Documentation Index
Fetch the complete documentation index at: https://docs.iru.com/llms.txt
Use this file to discover all available pages before exploring further.
About Intercom
Iru reads contacts, conversation metadata, teams, tags, and workspace settings through the Intercom REST API. You must pick the regional base URL (US, EU, or Australia) that matches data residency, then supply a Bearer token from the Developer Hub (app access token or equivalent).How it works
| Detail | Value |
|---|---|
| Category | Customer support / CRM |
| Authentication | Bearer token |
| Region | Base URL |
|---|---|
| US (default) | https://api.intercom.io |
| EU | https://api.eu.intercom.io |
| Australia | https://api.au.intercom.io |
Prerequisites
- Admin or sufficient rights to create or view app tokens in the Developer Hub.
Connect Intercom to Iru
Intercom
Iru Compliance
Turn on Intercom
Find Intercom (use Category or Search by name or description). On that card, turn on the toggle. A browser tab or window may open for the connector wizard.
Select the API host
Select the server endpoint for your region (US, EU, or Australia). Confirm before entering credentials.
Troubleshooting
Nothing opens when you turn the source on
Nothing opens when you turn the source on
Check pop-up blocker settings for the Iru site and try again.
401 Unauthorized
401 Unauthorized
Wrong region
Wrong region
EU/AU workspaces must use the matching host - not the generic US route.
Missing datasets
Missing datasets
Extended scopes may require Intercom approval. Check app permissions in Developer Hub.
Considerations
Deep conversation scopes sometimes need Intercom…
Deep conversation scopes sometimes need Intercom review (can take several business days).
See also
- See Sources Management for the full connector list.
