Intercom
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.
How to connect
Connect your Intercom workspace via OAuth. Click "Connect" and authorize access in Intercom.
Ready to connect?
Go directly to the integrations page in your dashboard.
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
"redirect_uri_mismatch" error during OAuth
Your OAuth app's authorized redirect URIs don't include the On Belay callback URL. Add https://app.onbelay.ai/api/oauth-callback/intercom to the allowed redirect URIs in your OAuth app settings.
"invalid_scope" error
The API or scope isn't enabled in your cloud project. For Google integrations, make sure the relevant API (e.g., Google Ads API, Search Console API) is enabled in Google Cloud Console for your project.
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.
Still stuck? We're happy to help.
Contact support →