Prerequisites
- Administrator permission on the Oleria workspace
- Access to your Intercom workspace’s Developer Hub
Create a Private App Access Token in Intercom
1
Open the Developer Hub
Sign in to Intercom and go to the Developer Hub, then open (or create) an app for this integration.
2
Grant scopes
Under Configure → Authentication, grant the app the following scopes:
read_adminsread_admin_activity_logs
3
Create the Access Token
From the same Authentication page, create an Access Token. Copy it now - Intercom shows it only once.
Connect Intercom to Oleria
1
Open the integration
Log in to your Oleria workspace, navigate to Integrations, and select Intercom.
2
Complete the connection form
Paste the Access Token you created in the Developer Hub.
3
Authenticate
Select Authenticate to complete the connection.
4
Verify the connection
Verify the Intercom integration status from the connected integrations page.
What Oleria syncs
- Users - Intercom admins (teammates), from the admin list
- Roles - the role catalog, derived from each admin’s assigned role
- Teams - Intercom teams, mapped as groups, and each admin’s team memberships
- Activity - admin activity-log events (audit trail of admin actions in the workspace)
Known limitations
- US region only - Oleria’s Intercom integration supports workspaces on Intercom’s US data region. EU and Australia region workspaces aren’t supported; connecting one fails at authentication.
- Intercom exposes no dedicated roles endpoint, so the role catalog is derived from the roles observed on admin accounts rather than fetched directly.
- No governance actions. Intercom’s API has no admin create, disable, suspend, or role/team-change operation. Oleria doesn’t perform any account or access changes for this integration - teammate lifecycle, roles, and team membership are all managed in Intercom’s own admin console.
- Contacts and Companies in Intercom aren’t synced as resources - this integration covers workspace access (admins, roles, teams) and admin activity only.

