Intercom
API keyCommunication & SupportOrg connection
Org-level connection
Intercom is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
Getting your API key
In Intercom, go to Settings → Integrations → Developer Hub (or developers.intercom.com) and open or create an app for your workspace
In the app, copy the Access Token (Configure → Authentication → Access token)
Paste the access token in the field above and click Connect
Ready to connect?
Sign in to On Belay and open the Integrations page to add Intercom.
Permissions (scopes)
These are the data scopes On Belay can be granted for Intercom. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
contacts:read | Read and list users and companies | Read only |
contacts:write | Write users and companies | Read / Write |
users:read | Read and write users | Read only |
events:read | Read events | Read only |
events:write | Write events | Read / Write |
conversations:read | Read conversations | Read only |
conversations:write | Write conversations | Read / Write |
conversations:delete | Delete conversations and metrics | Read / Write |
tags:read | Read tags | Read only |
tags:write | Write tags | Read / Write |
data_attributes:write | Write data attributes | Read / Write |
counts:read | Read counts | Read only |
export_content:read | Export content data | Read only |
message_data:export | Export message data | Read only |
content_data:read | Read content data | Read only |
tickets:read | Read tickets | Read only |
tickets:write | Write tickets | Read / Write |
jobs:read | Read status of jobs | Read only |
reporting_datasets:read | Read reporting datasets | Read only |
reporting_data:export | Export reporting data | Read only |
custom_objects:read | Read and write custom object instances | Read only |
custom_objects:write | Write custom object instances | Read / Write |
admins:read | Read admins | Read only |
admins:write | Update admins | Read / Write |
admin_activity_logs:read | Read admin activity logs | Read only |
articles:read | Read and list articles | Read only |
articles:write | Read and write articles | Read / Write |
news_items:read | Read and list news items and newsfeeds | Read only |
news_items:write | Read and write news items and newsfeeds | Read / Write |
ai_content:read | Read and write AI content | Read only |
phone_call_redirects:write | Create phone call redirects | Read / Write |
brands:read | Read brands | Read only |
data_connectors:read | Read data connectors | Read only |
emails:read | Read emails | Read only |
api_activity:read | Read API activity | Read only |
content_snippets:read | Read and write content snippets | Read only |
content_snippets:write | Write content snippets | Read / Write |
app_data:gather | Read data when entered into the app | Read only |
ip_allowlist:manage | Manage IP allowlist | Read / Write |
Troubleshooting
"Invalid API key" or "Unauthorized" error
Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
The key expires or stops working
Some API keys have expiration policies. Generate a new key in Intercom and update it in On Belay → Integrations → Intercom → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.
Still stuck? We're happy to help.
Contact support →