An Intercom MCP where the automation writes the note and a person sends the reply
Connect one access token and the Intercom inbox, contacts, companies, tags, segments, events, and help center become workflow steps for visual automations and AI agents. Replies and notes are two separate nodes with the message type pinned in fixed configuration, so the one node a customer can see is always a deliberate step.
What the Intercom MCP connector does
The Intercom connector for Mattering Automations is 49 nodes across the REST API: the workspace with its teammates and teams, contacts (list, search, create, update, tag, archive and restore), companies (upsert, read, and the contacts attached to them), conversations (list, search, read the full thread, reply, note, assign, close, snooze, retitle and tag), contact notes, tags, segments, data attributes, behavioural events, and help center articles and collections. Those 49 come out of Intercom's 164 documented paths on one curation rule: ship the objects a support or lifecycle automation touches, plus the reads that resolve an id before a write, and nothing only an Intercom admin would change.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can read a thread as plain text, pull the customer's recent events and account record, search the help center for the answer, and write a suggested reply into the conversation as a teammate-only note, without anyone opening the Intercom inbox.
Because Mattering is a work platform rather than middleware, support work lands somewhere useful by default and Intercom sits in the same workflow as everything else you run. A conversation that stays unanswered too long can open a task in Mattering Productivity, a churn signal from a billing tool can be written back onto the contact as a custom attribute and a behavioural event, and a help center article can be drafted from a task, all on one canvas next to the rest of the work.
The messaging boundary is structural, not advisory. Intercom: Add Note to Conversation and Intercom: Reply to Conversation (Sends to Customer) are the same Intercom endpoint split into two nodes with the message type pinned in fixed configuration, so no configuration change can turn a note into an outbound message. The note node is the safe default for automation; the reply node reaches a real person and cannot be unsent, so gate it behind an approval step. One more trap is worth knowing before you build: the optional body field on Intercom: Assign Conversation and Intercom: Close Conversation is posted as a PUBLIC reply, not an internal comment, so leave it blank unless you mean to write to the customer.
One connection, three surfaces
- Visual automations. Drag Intercom nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Intercom node, ready to drop on the canvas
49 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 23
Intercom: Find Companies
Look companies up by name or by YOUR own company_id, or filter every company by tag id or segment id. This is the lookup counterpart to List Companies: pass company_id to resolve your internal account id to the Intercom company id that the other company nodes need.
Intercom: Get Article
Fetch one help-center article by id, including its HTML body and its view, conversation and reaction statistics. The body is the piece worth feeding to an AI step that answers from your documentation.
Intercom: Get Company
Fetch one company by its Intercom id, with plan, seat count, monthly spend, session count, tags, segments and custom attributes.
Intercom: Get Contact
Fetch one contact by its Intercom id, including custom attributes and the counts and links for its tags, notes and companies. Note the documented merge behaviour: if the contact was merged into another one, this returns HTTP 410 with a Link header naming the surviving contact and an error body whose code is contact_merged.
Intercom: Get Contact by External ID
Look a contact up by YOUR identifier (the external_id you set on it), which is the usual way to bridge Intercom to your own database or to another app in the automation. Documented limitation: users only, never leads. A merged contact returns HTTP 410 pointing at the survivor.
Intercom: Get Conversation
Fetch one conversation with its full message history in conversation_parts, plus assignee, state, tags, rating and custom attributes. Documented hard limit: at most 500 conversation parts come back, the 500 most recent if the thread is longer. Set display_as to plaintext to strip the HTML out of every body, which is what you usually want before feeding a thread to an AI step.
Intercom: Identify Admin (Auth Check)
Return the teammate (admin) that the access token belongs to, with the workspace it is attached to. Needs no configuration, which makes it the connector's credential health check: a valid token returns 200 with data.id and data.email, an invalid one returns 401 with errors[0].code "unauthorized". The response carries no token, key or secret of any kind (data.app.id_code is the public workspace identifier already present in the Messenger snippet on your own website, not a credential). Handy for reading your own admin id, which several write nodes need.
Intercom: List Admins
List every teammate in the workspace, with id, name, email, away status, inbox seat and team memberships. This is where the admin_id values used by the reply, note, assign, close and snooze nodes come from.
Intercom: List Articles
List every help-center article in the workspace, most recently updated first, with title, state, author, parent collection and public URL. Use Search Articles when you know roughly what you are looking for.
Intercom: List Companies
List the workspace's companies, most recently active first. A POST that reads only, so it changes nothing. Documented limits: companies with no associated users are not returned, and paging tops out at 10,000 companies.
Intercom: List Company Contacts
List every contact attached to a company. The usual account-level fan-out: find the company, then act on all of its people.
Intercom: List Contact Events
List the behavioural events recorded for ONE contact, newest first, which is the fastest way to give a support agent or an AI step the context of what the customer just did. Identify the person with exactly one of user_id, intercom_user_id or email. Documented limit: only events from the last 90 days can be listed individually, though older ones still count in summaries.
Intercom: List Contact Notes
List the internal notes teammates have written on a contact, newest first, with each note's author and body. Notes are never visible to the customer.
Intercom: List Contacts
List all contacts (users and leads) in the workspace, cursor paginated. Page through with the starting_after cursor from pages.next. For anything filtered, prefer Search Contacts: this endpoint has no filters. Contacts that were merged away do not appear here.
Intercom: List Conversations
List all conversations in the inbox, cursor paginated. Returns conversation summaries without their message parts; use Get Conversation for the full thread. For anything filtered (open only, one team, unanswered) use Search Conversations.
Intercom: List Data Attributes
List the contact or company attributes defined on the workspace, standard and custom, with each one's data type and whether the API is allowed to write it (api_writable). Run this before writing custom_attributes anywhere: an attribute that does not exist, or is not api_writable, makes the write fail. Documented change: conversation attributes are no longer returned here.
Intercom: List Help Center Collections
List the help center's collections and sections, most recently updated first. A row with a parent_id is a section inside a collection. This is where the parent_id used by Create Article comes from.
Intercom: List Segments
List the workspace's saved segments of contacts, with each segment's id, name and person type. Segment ids feed the segment_id filter on Find Companies and the segment filters in Search Contacts.
Intercom: List Tags
List every tag in the workspace with its id and name. Run this first to resolve a tag name to the tag id that the add-tag and remove-tag nodes require.
Intercom: List Teams
List the workspace's teams (inbox groups) with their ids, member admin ids and assignment settings. Use a team id as the assignee_id on Assign Conversation with assignee_type set to team.
Intercom: Search Articles
Search help-center articles by phrase, optionally limited to one help center or to drafts. The natural first step in a deflection flow: search the docs for the customer's question, then reply or note the best article back into the conversation.
Intercom: Search Contacts
Search contacts by the value of their attributes with Intercom's query DSL: filter on email, role, created_at, last_seen_at, tag ids, company ids, custom attributes and more, combined with AND and OR. A POST that reads only, so it changes nothing. This is the filtered alternative to List Contacts.
Intercom: Search Conversations
Search conversations with Intercom's query DSL: filter on state (open, closed, snoozed), open, read, priority, created_at, updated_at, waiting_since, admin or team assignee, contact ids, tag ids, channel and custom attributes, combined with AND and OR. A POST that reads only. This is the node that finds work to act on: unanswered conversations, everything waiting on one team, anything older than an hour.
Action nodes 26
Intercom: Add Note to Conversation
Add an internal note to a conversation, visible to your teammates in the inbox and NEVER to the customer. This is the safe way to push context into a thread from an automation: order status, account health, an AI summary or a suggested reply for a human to approve. Notes accept some HTML formatting. Same endpoint as Reply to Conversation, with message_type fixed to note so it cannot leak outbound.
Intercom: Add Tag to Contact
Apply an existing tag to a contact and get the tag back. Additive: it does not disturb the contact's other tags. Reverse it with Remove Tag from Contact. The tag must already exist; create it first with Create or Update Tag.
Intercom: Add Tag to Conversation
Apply an existing tag to a conversation, which is how automated triage shows up for the humans working the inbox and how reporting groups threads later. Additive and reversible via Remove Tag from Conversation. Posts nothing to the customer.
Intercom: Archive Contact
Archive a contact so they drop out of your lists, segments and messaging without being erased. This is the reversible alternative to deletion: the Unarchive Contact node brings them straight back. Permanent contact deletion is deliberately not part of this connector.
Intercom: Assign Conversation
Route a conversation to a teammate or to a team. Reversible: assign it somewhere else and the previous assignment is simply replaced. Careful with the optional body field: anything you put there is posted as a PUBLIC reply the customer sees, so leave it blank for silent routing.
Intercom: Attach Contact to Company
Link a contact to a company, which is also what makes the company visible in the Intercom UI. Additive: a contact can belong to several companies. Detaching again is available on the Intercom API but is not shipped as a node; do it in the Intercom UI or with the generic HTTP node.
Intercom: Close Conversation
Close a conversation. Fully reversible: a closed conversation reopens when the customer replies, and a teammate can reopen it from the inbox at any time. Careful with the optional body field: anything you put there is posted as a PUBLIC reply the customer sees, so leave it blank to close silently.
Intercom: Create Article
Create a help-center article. This node defaults state to draft on purpose, so an automation cannot silently publish to your public help center: set state to published only when you mean it. author_id must be a teammate with help-center access. Reversible: an unwanted draft can be deleted from the Intercom UI, and article tags are read-only through this API.
Intercom: Create Contact
Create a contact: a user (someone you have identified) or a lead (an anonymous visitor). Set external_id to your own identifier so later automations can find this person with Get Contact by External ID. Reversible: a contact created by mistake can be archived with the Archive Contact node and brought back with Unarchive Contact. Creating a contact sends nothing to the person.
Intercom: Create Contact Note
Write an internal note onto a contact's profile: enrichment data, a churn-risk flag, an account summary. Teammate-only, never shown to the customer and it notifies nobody. Honest caveat: the Intercom API has no delete-note endpoint, so a note posted by mistake has to be removed by a human in the Intercom UI.
Intercom: Create Conversation (From Contact)
Open a new conversation AS a contact, exactly as if the person had written in through the Messenger, so it lands in your inbox for a teammate to answer. Read the direction carefully: this does not message the customer, it creates their side of a thread. To send something outbound, reply to an existing conversation with the Reply to Conversation node. Documented behaviour: in-app messages only, and a visitor passed here is converted to a lead.
Intercom: Create Data Attribute
Define a new custom attribute on contacts or companies, so later nodes can write it through custom_attributes. Do this once at setup rather than on every run. Reversible in practice: an unwanted attribute is archived with Update Data Attribute (archived true) rather than deleted. Documented limitation you should plan around: the data type cannot be changed afterwards through the API.
Intercom: Create or Update Company
Upsert a company keyed on your own company_id: Intercom looks the company up by that value and updates it if found, or creates it if not. The natural sync node for pushing account data in from a CRM or billing system. Two documented traps: company_id can be set once and never changed afterwards, and a company stays invisible in the Intercom UI until at least one contact is attached to it.
Intercom: Create or Update Tag
Create a tag by name, or rename an existing one by passing its id as well. Returns the tag with its id, which is what the add-tag nodes need. This node deliberately exposes only the create-or-rename half of Intercom's multi-purpose tags endpoint; to apply a tag to a contact or a conversation use the dedicated add-tag nodes, which are clearer and individually reversible.
Intercom: Delete Tag (Destructive)
WARNING: destructive and not undoable through the API. Deleting a tag removes it from the workspace and therefore from every contact, company and conversation it was applied to, and there is no restore endpoint: recreating the tag afterwards gives you a new empty tag, not the old assignments. To take a tag off ONE record, use Remove Tag from Contact or Remove Tag from Conversation instead. Returns 200 with no body on success.
Intercom: Remove Tag from Contact
Remove one tag from one contact and get the removed tag back. This unlinks the tag from this contact only; the tag itself and its other assignments are untouched (that is the Delete Tag node, which is destructive). Reverse it with Add Tag to Contact.
Intercom: Remove Tag from Conversation
Remove one tag from one conversation and get the removed tag back. Unlinks the tag from this conversation only; the tag itself survives (deleting it outright is the Delete Tag node, which is destructive).
Intercom: Reply to Conversation (Sends to Customer)
WARNING: this sends a real message to a real customer. The reply is delivered in the Messenger and, depending on the conversation's channel, emailed to the contact, and it cannot be unsent. Do not point this node at live conversations while building or testing a flow. The safe rehearsal path is the Add Note to Conversation node, which writes into the same thread but is visible only to your teammates. When you are ready to go live, test against a conversation you started yourself from your own test contact. Posts a public reply from a teammate and returns the updated conversation.
Intercom: Snooze Conversation
Snooze a conversation until a chosen time, taking it out of the open queue without closing it. It comes back automatically at snoozed_until, and earlier if the customer replies. Fully reversible. Posts nothing to the customer.
Intercom: Submit Event
Record a behavioural event against a contact, such as invoice-paid or trial-expired, which then drives Intercom segments and outbound messages. Identify the person with exactly one of user_id, id or email. Honest caveat: an event cannot be deleted once submitted, so use an obviously named test event when trying this out. Returns 202 Accepted with an empty body on success.
Intercom: Unarchive Contact
Restore a previously archived contact, putting them back into lists, segments and messaging. The exact inverse of Archive Contact.
Intercom: Update Article
Update a help-center article: retitle it, rewrite the body, move it to another collection, or change its state. Only the fields you fill are sent. Note that setting state to published makes the article publicly visible immediately, and setting it back to draft takes it down again.
Intercom: Update Company
Update a company addressed by its INTERCOM id. Only the fields you fill are sent. Use Create or Update Company instead when you are keying off your own company_id, which cannot be changed by this node either way.
Intercom: Update Contact
Update an existing contact. Only the fields you fill are sent, so blank fields are left untouched rather than cleared. The common automation use is writing custom attributes back onto the person from another system.
Intercom: Update Conversation
Update a conversation's metadata: mark it read, retitle it, write conversation custom attributes, or associate it with a company. Only the fields you fill are sent. Nothing here is posted to the customer. For replying, assigning, closing or snoozing, use the dedicated nodes.
Intercom: Update Data Attribute
Update a custom attribute's description, allowed options, Messenger writability, or archive it. Archiving is the reversible stand-in for deletion (set archived back to false to restore it). The data type cannot be changed here: Intercom's docs call that out as a UI-only operation.
Connecting Intercom takes one credential
Intercom issues access tokens from the Developer Hub at developers.intercom.com: create or open an app inside the workspace you want to automate, then take the token from Configure > Authentication. The token is scoped to that one workspace, needs no OAuth flow, and is sent as a bearer credential on every request. Two things to know before you paste it. Intercom hosts workspaces on three separate API hosts (United States, Europe, Australia), so a workspace outside the US prefixes its token value with eu: or au: and the connector calls the right host. And Intercom's terms of service prohibit asking your own users for their access tokens instead of implementing OAuth, so this credential is for a token from a workspace you administer, entered into your own connector.
In the Intercom Developer Hub (developers.intercom.com), open or create an app inside your workspace and copy its access token from Configure > Authentication.
In Mattering Automations, open Connectors, click Add Connector, choose Intercom, and create a credential with that token. If the workspace is hosted in Europe or Australia, prefix the value with eu: or au:
Click Test Connection. Mattering calls Intercom's admin identify endpoint and reports the teammate and workspace the token belongs to.
All 49 Intercom nodes appear in the canvas palette. Run Intercom: List Admins and Intercom: List Tags first, because the teammate ids and tag ids they return are what the write nodes ask for.
Common uses for the Intercom MCP
Triage the inbox without messaging anyone
Intercom: Search Conversations is the node that finds work to act on: everything open and unanswered, everything waiting on one team, anything older than an hour. From there Intercom: Add Tag to Conversation records what the automation decided, Intercom: Assign Conversation routes the thread to a teammate or a team, and Intercom: Snooze Conversation takes it out of the open queue until a chosen time. Leave the body field blank on assign and close and none of this is visible to the customer.
Give a thread its context before a human opens it
Intercom: Get Conversation returns the full message history, with display_as set to plaintext so the HTML is stripped before an AI step reads it. Intercom: List Contact Events adds what the customer just did, Intercom: Get Company adds plan, seat count and monthly spend, and Intercom: Add Note to Conversation writes the summary into the thread where only teammates can see it.
Help center answers, drafted rather than sent
Intercom: Search Articles finds the documentation that matches the customer's question and Intercom: Get Article returns the body worth feeding to an AI step. The safe ending is Intercom: Add Note to Conversation carrying the suggested answer and the article link, so a teammate approves before anything goes out. Intercom: Reply to Conversation (Sends to Customer) is the deliberate second step, and it is the only node in this flow a customer ever sees.
Keep people and accounts in sync with your own systems
Intercom: Get Contact by External ID bridges your own identifier to the Intercom one, Intercom: Update Contact writes attributes back onto the person, and Intercom: Create or Update Company upserts an account keyed on your own company_id, with Intercom: Attach Contact to Company linking the people to it. Run Intercom: List Data Attributes first, because an attribute that does not exist, or is not marked api_writable, makes the write fail.
Lifecycle events that drive segments
Intercom: Submit Event records what happened in your product, such as an invoice paid or a trial expiring, and Intercom's own segments and outbound messages pick it up from there. Pair it with Intercom: Add Tag to Contact for the flags your team filters on, and Intercom: List Segments to read the saved segments those events feed. An event cannot be deleted once submitted, so use an obviously named test event while you are building.
Help center content that cannot publish itself
Intercom: Create Article defaults its state to draft on purpose, so an automation cannot silently publish to a public help center. Publishing is an explicit choice made on Intercom: Update Article, which also takes an article back down. Intercom: List Help Center Collections supplies the parent collection id, and Intercom: List Articles and Intercom: Search Articles read what is already there.
Example: Unanswered conversations get context, a summary, and a route, with a person before any reply
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a schedule runs every fifteen minutes.
Intercom: Search Conversations returns every open conversation waiting longer than your target, filtering on state and waiting_since with the query DSL.
Intercom: Get Conversation pulls each full thread with display_as set to plaintext, and Intercom: List Contact Events adds what the customer did just before writing in.
Intercom: Search Articles looks for help center content matching the question, and an AI step drafts a suggested answer from the article body.
Intercom: Add Note to Conversation writes the summary, the suggested answer and the article link into the thread. Teammates see it in the inbox; the customer never does.
Intercom: Assign Conversation routes the thread with its body field left blank, so the routing is silent, and Intercom: Add Tag to Conversation records the decision. Only a separately gated Intercom: Reply to Conversation (Sends to Customer), behind an approval task in Mattering Productivity, ever sends anything to the customer.
Intercom MCP questions, answered
What Intercom operations are supported?
49 nodes on the REST API, pinned to version 2.16: the workspace with its teammates and teams; contacts (list, search, get by Intercom id or by your own external id, create, update, tag, archive, unarchive); companies (list, find, get, upsert, update, list attached contacts, attach); conversations (list, search, read the full thread, reply, note, assign, close, snooze, update, tag); contact notes; tags; segments; data attributes; behavioural events; and help center articles, article search and collections. Deliberately not shipped: outbound messages that start a brand new email or in-app message with no existing thread, the separate Tickets product surface, contact and conversation deletion, redaction and merges, calls, recordings and transcripts, the asynchronous export and download endpoints, the Fin AI surfaces, and workspace administration such as away mode, office hours and IP allowlists.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. Intercom publishes its own MCP server too; what is different here is that these nodes live inside automations next to every other connector, so one workflow can read an Intercom thread, check an order in another system, open a task, and write the answer back as a note, rather than handing an assistant one vendor at a time.
Can this connector message a customer by accident?
It is built so that it cannot do so silently, and there are exactly three places a message can leave the workspace. Intercom: Reply to Conversation (Sends to Customer) says so in its own label: the reply is delivered in the Messenger and, depending on the conversation's channel, emailed to the contact, and it cannot be unsent. Intercom: Add Note to Conversation calls the same Intercom endpoint with the message type pinned to note in fixed configuration, so no configuration change can turn a note into an outbound message; that makes it the safe rehearsal path and the right default for automation. The third place is the one people miss: the optional body field on Intercom: Assign Conversation and Intercom: Close Conversation is posted as a public reply the customer receives, not an internal comment, so someone closing a thread with a body expecting a private wrap-up note has just messaged the customer. Leave it blank for silent routing. One direction worth reading twice: Intercom: Create Conversation (From Contact) creates the customer's side of a thread in your inbox and sends nothing to anybody.
My Intercom workspace is hosted in Europe or Australia. What changes?
One prefix on the token value when you create the credential: eu: for Europe, au: for Australia, and nothing at all (or us:) for the United States. Intercom runs three separate API hosts, one per region, and its own documentation says the US host will attempt to route a request to the correct region, which is not a guarantee. Putting the region in the credential settles it once for all 49 nodes rather than asking every node to carry a workspace level constant that one node in a ten node flow will eventually get wrong. The prefix is unambiguous because Intercom access tokens are base64 style strings and that alphabet contains no colon, so a leading eu: can never be part of a real token. A European or Australian workspace whose token was pasted bare is the most likely reason this connector misbehaves.
Which Intercom API version do the nodes use?
2.16, sent in the Intercom-Version header on every request. Intercom versions by decimal release number rather than by date: values run from 1.0 through 2.16, incrementing by 0.1 per release, and 2.16 shipped on 2026-07-15. Plenty of other APIs use a date string and people reasonably assume Intercom does the same. Pinning matters because a request with no version header gets whatever version the workspace's own app is pinned to, so the identical node would return different response shapes for different customers, and any sample output shown in the canvas would drift for anyone on an older pin.
What can this connector destroy?
One node, and it says so in its name. Intercom: Delete Tag (Destructive) removes a tag from the workspace and therefore from every contact, company and conversation it was applied to, and there is no restore endpoint: recreating the tag afterwards gives you a new empty tag, not the old assignments. To take a tag off one record, use Intercom: Remove Tag from Contact or Intercom: Remove Tag from Conversation, which unlink a single object and are exactly reversible. Everything else in the connector is reversible or additive, which is the plain version worth stating: permanent contact deletion, conversation deletion, redaction and merges are not built at all, and Intercom: Archive Contact ships with Intercom: Unarchive Contact as its exact inverse. Two append-only exceptions to be honest about: a note from Intercom: Create Contact Note has no API delete and must be removed by a person in the Intercom UI, and an event from Intercom: Submit Event cannot be unsent.
Can an Intercom conversation trigger a workflow?
Not as a trigger node in this connector. Intercom's webhook subscriptions are deferred until Automations has an inbound trigger story, so the honest pattern today is polling: run Intercom: Search Conversations on a schedule, filter on state, waiting_since or a tag, and act on what changed. One honest caveat while paging through results: a few pagination parameters are described in Intercom's prose documentation but not declared in their OpenAPI file for those paths. The nodes send them anyway, and they are harmless no-ops if an endpoint ignores them.
What about attachments and files?
Nothing binary goes in or comes out. Intercom's reply endpoints accept an array of base64 encoded file blobs, and that field is deliberately not exposed on any node, so a workflow cannot balloon its payload with file bytes; hosted attachment URLs ship instead, which covers pointing at an image the automation already has a link to. On the way out, calls, recordings, transcripts and every export download endpoint are omitted, so no node in this connector returns raw binary. The one genuinely large JSON response is a long thread from Intercom: Get Conversation, and Intercom itself caps that at the 500 most recent conversation parts.
Put Intercom to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Intercom is a product of its respective owner; Mattering is an independent platform.