Menu

Mattering Automations Intercom integration

Connect Intercom to Mattering Automations: conversations, contacts, companies, tags, segments, data attributes, events, and help center articles as workflow steps, authenticated with a single Intercom access token.

The Mattering Automations Intercom integration adds Intercom to your automation canvas: list, search and read inbox conversations with their full message history, reply to a customer or add a teammate-only note, assign, close, snooze, retitle and tag conversations, create, search, update, tag and archive contacts, upsert companies and attach contacts to them, write contact notes and behavioural events, manage tags, read segments and data attributes, and search, read, create and update help center articles and collections.

Setup takes a few minutes: create an access token in the Intercom Developer Hub, attach it as a credential in Mattering, and test the connection. Workspaces hosted in Europe or Australia have one extra thing to type, covered in the credential section below. This guide walks through each step and ends with the full node reference.

The messaging model is note-first by construction. 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. Verify the integration with read nodes and notes only, and keep the reply node behind a condition, an approval step, or a manual run.

Before you start

  • An Intercom workspace you administer. Intercom also offers a free developer workspace through the Developer Hub, which is the intended way to build and test an integration without a paid subscription.
  • Access to the Intercom Developer Hub (developers.intercom.com) to create an app in that workspace and copy its access token.
  • Knowing which region hosts the workspace: the United States, Europe, or Australia. It changes the credential value by three characters.
  • A Mattering workspace with access to the Automations app.

Create an Intercom access token

Mattering authenticates to Intercom with an access token, sent as a bearer credential on every request. The token belongs to an app inside your own workspace and is scoped to that workspace, which is Intercom's documented private-app flow: no OAuth round trip, no request signing, and no refresh step to model.

Sign in to the Intercom Developer Hub (developers.intercom.com) and open or create an app inside the workspace you want to automate.
Go to Configure > Authentication and copy the access token.
Check which region hosts the workspace: the United States, Europe, or Australia.
Region belongs in the credential, and getting it wrong is the most likely way this integration fails. 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. So prefix the token value with the region: eu:YOUR_TOKEN for Europe, au:YOUR_TOKEN for Australia, and either us:YOUR_TOKEN or no prefix at all for the United States. 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 first thing to check when calls behave strangely.
Treat the access token like a password. Intercom's terms of service specifically prohibit asking your own users for their access tokens instead of implementing OAuth, so use this credential only for a token issued by a workspace you administer, entered into your own connector. Do not build a flow that collects tokens from other people.

Connect Intercom to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Intercom from the list.
Click Create new credential, paste your access token (with the eu: or au: prefix if the workspace is hosted outside the United States), and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection. Mattering calls Intercom's admin identify endpoint and confirms the token authenticates, reporting the teammate and the workspace it belongs to.
Click Connect. All 49 Intercom nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: an Intercom section should list the query and action nodes. Drop Intercom: Identify Admin (Auth Check) onto the canvas and run a test step. It takes no configuration at all and is a read-only call that returns the teammate the token belongs to and the workspace it is attached to. What that response does not contain is worth knowing: no token, key, secret or session field of any kind. The only identifier in it is the public workspace code that already appears in the Intercom Messenger snippet on your own website, visible in any browser's view-source. Unlike some support APIs, this endpoint has no anonymous mode, so a bad token comes back as a clean 401 rather than a misleading success.

To confirm the rest of the surface, run Intercom: List Admins for the teammate ids that the reply, note, assign, close and snooze nodes need, Intercom: List Tags for the tag ids that the add-tag and remove-tag nodes require, and Intercom: Search Conversations for the inbox itself. Everything in the verify path is read-only; nothing here reaches Intercom: Reply to Conversation (Sends to Customer), which is the only node a customer ever sees.

Node reference

49 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 23

Intercom: Find Companies

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

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

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

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

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

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)

intercom_identify_admin

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

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

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

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

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

intercom_list_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

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

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

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

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

intercom_list_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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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)

intercom_create_conversation

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

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

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

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)

intercom_delete_tag

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

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

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)

intercom_reply_to_conversation

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

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

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

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

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

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

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

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

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.

Using the integration

On the automation canvas

Intercom nodes chain with every other node, which is the point of running them here rather than one vendor at a time. A scheduled Intercom: Search Conversations sweep can open a task in Mattering Productivity for anything unanswered past your target, a billing signal from another connector can land as a custom attribute through Intercom: Update Contact and as a behavioural event through Intercom: Submit Event, and Intercom: Create or Update Company can keep account records in step with a CRM. For per-person context, Intercom: List Contact Events returns what someone just did, with the documented caveat that only the last 90 days can be listed individually.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can read threads, look up the account behind them, search your help center, and write a suggested answer back as a teammate-only note through the same nodes your workflows use. Set display_as to plaintext on Intercom: Get Conversation to strip the HTML out of every message body before an AI step reads it, which is also the smaller payload; Intercom caps that response at the 500 most recent conversation parts. The reads, plus Intercom: Add Note to Conversation, are the safest Intercom surface to hand an agent.

Notes, replies, and the body field that is public

One Intercom endpoint does two very different jobs, so this integration ships it as two nodes. Intercom: Reply to Conversation (Sends to Customer) posts a public reply that is delivered in the Messenger and, depending on the channel, emailed to the contact, and it cannot be unsent. Intercom: Add Note to Conversation hits the same endpoint with the message type pinned to note in fixed configuration, so it is visible only to teammates in the inbox and no configuration change can flip it outbound. Build and rehearse with the note node, then go live against a conversation you started from your own test contact. The sneaky one is elsewhere: the optional body field on Intercom: Assign Conversation and Intercom: Close Conversation is also a public reply, not an internal comment, so closing a thread with a body expecting a private wrap-up will message the customer. Leave it blank for silent routing.

Three regional hosts, one credential

Intercom serves the United States, Europe and Australia from three separate API hosts, and its documentation describes the US host as attempting to route a request to the correct region rather than guaranteeing it. Rather than hard-code one host or add a region field to all 49 nodes (which is how one node in a ten node flow ends up wrong), the region rides on the credential: eu: or au: in front of the token value, or nothing for the United States. Change region by editing the one credential; every node follows.

A pinned API version, by release number

Intercom versions its API with a decimal release number in an Intercom-Version header, not a date string: values run from 1.0 through 2.16, incrementing by 0.1 per release, with 2.16 released on 2026-07-15. Many APIs use dates and people assume Intercom does too, so it is worth saying plainly. Every node sends the header pinned to 2.16, deliberately. Without it each workspace gets whatever version its own app is pinned to, which means the same node would return different response shapes for different customers and the sample output shown in the canvas would drift.

Intercom ids, your ids, and merged contacts

Contact and company nodes take the Intercom id, which is not the identifier from your own database. Intercom: Get Contact by External ID is the bridge for people (users only, never leads), and Intercom: Find Companies resolves your own company_id to the Intercom company id the other company nodes want. Two documented behaviours to plan around: a contact that was merged into another one returns HTTP 410 with an error code of contact_merged and a Link header naming the survivor, and a company's company_id can be set once and never changed, with the company staying invisible in the Intercom UI until at least one contact is attached to it.

Troubleshooting

Test Connection fails with a 401
The token is invalid, was revoked, picked up stray whitespace when pasted, or belongs to a different workspace. Confirm it against Configure > Authentication for the app in the workspace you meant to automate. If the token is definitely correct, the next suspect is the region prefix below, because a token sent to the wrong regional host also comes back as a 401.
The workspace is hosted in Europe or Australia and calls fail or return nothing
The token was almost certainly pasted bare. Intercom runs three separate API hosts and only the US host attempts to route requests elsewhere, which the documentation does not promise. Edit the credential and prefix the value with eu: for a European workspace or au: for an Australian one, then run Intercom: Identify Admin (Auth Check) again. This is the single most common support question this integration produces, and it is a one-line fix rather than anything structural.
A customer received a message the automation was not supposed to send
There are two ways this happens. Either Intercom: Reply to Conversation (Sends to Customer) ran without a gate, in which case put a condition, an approval task, or a manual run in front of it and rehearse with Intercom: Add Note to Conversation instead, or the optional body field on Intercom: Assign Conversation or Intercom: Close Conversation was filled in. That field is a public reply, not an internal comment: clear it, and put the text into Intercom: Add Note to Conversation, which teammates see and the customer never does. Neither kind of message can be unsent, so fix the flow before the next run.
Writing custom_attributes fails or the value is ignored
The attribute has to exist on the workspace first and has to be writable through the API. Run Intercom: List Data Attributes and check the attribute is listed for the right model (contact or company) with api_writable set. If it is missing, create it once at setup with Intercom: Create Data Attribute rather than on every run. An attribute's data type cannot be changed afterwards through the API, so pick it carefully; an unwanted attribute is archived with Intercom: Update Data Attribute rather than deleted.
A contact lookup returns HTTP 410 Gone
That contact was merged into another one. Intercom answers 410 rather than 404, with an error code of contact_merged and a Link header naming the surviving contact, and both Intercom: Get Contact and Intercom: Get Contact by External ID surface it. Follow the link to the survivor and update whatever id your workflow stored. Note also that lookup by external id covers users only, never leads.
An article was created but does not appear on the help center
That is the design working. Intercom: Create Article defaults its state to draft on purpose, so an automation cannot silently publish to a public help center. When the draft has been reviewed, set the state to published with Intercom: Update Article, which makes it publicly visible immediately and can take it back down again. The author must be a teammate with help-center access, and article tags are read-only through this API.
A tag vanished from hundreds of contacts and conversations at once
Intercom: Delete Tag (Destructive) was run. Deleting a tag removes it from the workspace and therefore from every object it was applied to, and Intercom has no restore endpoint, so recreating the tag gives you a new empty tag rather than the old assignments. It is the only destructive node in this integration; everything else is reversible or additive. To take a tag off a single record, use Intercom: Remove Tag from Contact or Intercom: Remove Tag from Conversation, which unlink one object and are exactly reversible.
Nodes start returning HTTP 429
Intercom rate limits per app and per workspace, and the budget refills every 10 seconds rather than once a minute, so a burst inside a single 10-second window can be throttled while the per-minute total still looks fine. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (a Unix timestamp in seconds). The nodes do not retry on your behalf, deliberately, so add a wait or a smaller batch size in the automation and spread scheduled sweeps out rather than firing them all on the hour.

Intercom is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products