https://api.intercom.io, or the EU or Australian host for those regions), using an access token from an app that someone with Developer Hub access creates in Intercom. Configview sends only GET requests. It never creates, changes or deletes anything in Intercom.
You will end up with 1 required secret (INTERCOM_ACCESS_TOKEN) and 1 optional secret (INTERCOM_REGION) in Configview when setup is complete.
Scope of this integration today. Configview reads who works in the workspace (teammates, with paid Inbox seat and away mode), your teams and who is in them, the admin activity log for the last 30 days (sign-ins, role, permission and seat changes, token and webhook events, exports), the workspace itself, Help Center settings, and the definitions of your data attributes. It never reads conversations, messages, contacts, leads, companies, tickets, notes, articles, call recordings or transcripts, and it never calls those endpoints.
What the Intercom API does not tell Configview
The teammate list has no role, permission set, last-active date, 2FA or SSO status. There is no endpoint for pending invites, API tokens or webhooks: token, webhook and role changes show up only as events in the activity log. Removed teammates are not listed. Configview cannot answer who is an admin or who has gone quiet.What you need
- An Intercom workspace with access to Settings > Integrations > Developer Hub
- The data region of the workspace (US, EU or Australia)
Step 1: Open the Intercom page in Configview
https://{companyname}.configview.com/admin/integrations/intercom
Step 2: Create the token (least privilege)
- In Intercom open Settings > Integrations > Developer Hub and create a new app (an internal integration)
- Under Authentication > Permissions tick Read admins only. This covers teammates, teams and the activity log. If the first run reports a 403 for Help Centers or data attributes, tick the matching read-only permission for that area and nothing else
- Do not tick any conversation, contact, company, ticket, message or write permission
- Copy the access token. It belongs to the workspace, not to a person, so it keeps working when someone leaves
- In Configview paste it into
INTERCOM_ACCESS_TOKENunder Credentials and click the save icon - If your workspace is hosted in the EU or Australia, set
INTERCOM_REGIONtoeuorau. Leave it empty for the US
Step 3: Connect and verify
- Click Connect. Configview creates its tables and schedules every collector at your default run time:
- Click Verify now. The health check reads the secret, calls
GET /me, then reads the teammate list.
Data Tables
Each table has arun_at column and keeps only the newest run.
Rate limits
Intercom allows 10,000 calls per minute per workspace for private apps (25,000 across all apps), counted in 10-second windows. Configview paces at 120 per minute, reads activity logs 150 rows at a time, and retries a 429 after the reset header (60 seconds if none is sent). Each collector makes only a handful of requests.Known gaps and things to check on the first run
These come from the published OpenAPI description (version 2.14); no live tenant has been tested yet.- Permissions. Only
read_adminsis documented for teammates and the activity log. Teams, Help Centers and data attributes may each need their own read permission on the app; a 403 is skipped and the table stays empty. - Activity log paging. Configview sends
created_at_after(30 days back) and followspages.next.starting_after. If the table holds fewer than 150 rows on a busy workspace, check that field. - Region. A token used against the wrong regional host returns 401. Set
INTERCOM_REGIONto match the workspace. - Team ids.
team_idson a teammate are numbers andadmin_idson a team are numbers, whileidfields are strings; Configview stores all of them as text and assumes they match. - Fin and bot admins. The teammate list may include non-human admins; they show as accounts without a job title.