Intercom MCP integration for AI agents.
Connect AI agents to Intercom through 24 structured actions, including get admin, create contact, close conversation, and reopen conversation. Review authent…
- ACTION CONTRACTS
- 24
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Intercom integration exposes
The Intercom Agent App exposes 24 provider-backed actions for communication and productivity work. Its current contract lets an authorized agent get a single intercom admin by identifier, create a new intercom contact, and close an intercom conversation. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Intercom account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Intercom capabilities.
Showing 12 of 24 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_adminREADGet a single Intercom admin by identifier.
INPUTS: adminId
create_contactWRITECreate a new Intercom contact.
INPUTS: role / externalId / email / phone / name
close_conversationHIGH IMPACTClose an Intercom conversation.
INPUTS: conversationId / adminId / body
reopen_conversationREVIEWReopen an Intercom conversation.
INPUTS: conversationId / adminId
get_articleREADGet a single Intercom help center article by identifier.
INPUTS: articleId
get_companyREADGet a single Intercom company by company ID or name.
INPUTS: companyId / name
get_contactREADGet a single Intercom contact by identifier.
INPUTS: contactId
get_contact_by_external_idREADGet a single Intercom contact by external ID.
INPUTS: externalId
get_conversationREADGet a single Intercom conversation with its conversation parts.
INPUTS: conversationId / displayAs
get_countsREADRead Intercom workspace, conversation, or grouped counts.
INPUTS: type / count
get_current_adminREADGet the currently authorized Intercom admin and workspace metadata.
get_job_statusREADGet the status of an Intercom asynchronous job.
INPUTS: jobId
INPUT CONTRACTS
Know what the action needs before it runs.
get_admin
adminIdOPTIONAL- Intercom admin identifier.
create_contact
roleOPTIONAL- Intercom contact role.
externalIdOPTIONAL- External identifier stored on the Intercom contact.
emailOPTIONAL- Primary email address for the Intercom contact.
phoneOPTIONALnameOPTIONAL
close_conversation
conversationIdREQUIRED- Intercom conversation identifier.
adminIdREQUIRED- Intercom admin identifier performing the close.
bodyOPTIONAL- Optional closing message to append to the conversation.
reopen_conversation
conversationIdOPTIONAL- Intercom conversation identifier.
adminIdOPTIONAL- Intercom admin identifier performing the reopen.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Admin
Get a single Intercom admin by identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_adminControl Create Contact
Create a new Intercom contact. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Get Article
Get a single Intercom help center article by identifier. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_articleSAFETY BOUNDARY
Operate Intercom with explicit limits
- Authorize Intercom with OAuth 2.0 and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `close_conversation` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `Write conversations`, `Read and write users`, `Read admins`, and `Read and List articles`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Intercom task completed successfully.
CONNECTION MODEL
OAuth 2.0
Intercom uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 19
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Intercom.