List conversations in the workspace (most recent via paging/search). (docs)
GET /conversations
🟢 low
— no
List contacts (users or leads) in the workspace. (docs)
GET /contacts
🟢 low
— no
What the agent can do
Capability
API call
Risk
Needs approval
Reply to a conversation with a customer-visible message from an admin. (docs)
POST /conversations/{conversation_id}/reply
🔴 high
✅ yes
Create a new contact (user or lead) in the workspace. (docs)
POST /contacts
🟡 medium
✅ yes
Connecting it
You provide: Intercom workspace (OAuth) or Access Token
Where to get it: Intercom Developer Hub → create an app. Own workspace: copy the Access Token from Configure → Authentication. Multi-workspace: enable OAuth, set redirect URIs + permissions, run the authorization-code flow per workspace. Intercom uses a permissions model selected in the Developer Hub, not granular OAuth scopes.
Permissions/scopes:none / not scope-based
Account setup
Account needed: An active Intercom workspace; the connecting user must be an admin with permission to install apps and access conversations & contacts.
App registration: Developer Hub → create app. Own workspace: take the Access Token (full workspace access). Multi-workspace: build a public OAuth app with redirect URIs + selected permissions.
Verification required: Public/App-Store apps go through Intercom's review (Test & Publish). Private own-workspace apps need no review.
Testing: Use a development workspace + the Developer Hub Test & Publish flow to install/test before publishing.
Limits
Default 10,000 calls/min per app and 25,000 calls/min per workspace. Monitor rate-limit response headers.