Resources · n8n integration

Intercom n8n integrationAutomate Intercom with n8n.

Support opens a conversation, and the contact record behind it is already three weeks old. The Intercom n8n integration closes that gap from a workflow: 15 operations spread over 3 objects, companies, leads and users, kept in sync without anyone retyping a field.

Try the Intercom integration on n8nSee the 15 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Intercom n8n integration actually do?

The Intercom node lets an n8n workflow read and write the contact data behind your Intercom inbox. It handles 3 objects, companies, leads and users, with 15 operations in total: create, read one, read many, update, plus delete on leads and users and a list of the users attached to a company.

Everything runs on one credential, so the same connection serves every workflow you build afterwards.

Take a trial signup. Your product database fires a workflow, user.create writes the person into Intercom with the identifier you already use, and company.create attaches the account they belong to. Support opens the conversation two days later and the plan, the size and the industry are already on the record.

Second pattern, the periodic export. A Schedule Trigger runs user.getAll with Return All switched on and a Segment ID filter, then drops the result into Google Sheets for the weekly review. The same list can be counted and posted into Slack so the team sees the number before the meeting.

Third pattern, inbound. A form submission creates a lead with lead.create, carrying the campaign it came from in the UTM Campaign and UTM Medium fields, and a follow up goes out through Gmail. When the person signs up, lead.update corrects the record instead of creating a duplicate.

Anything outside these 15 catalogue operations goes through the HTTP Request node, which calls any endpoint of the Intercom API while reusing the very same credential through predefined authentication. You keep one connection, you just point it somewhere else.

One habit to build early: on the list operations, Return All is what makes n8n walk through the API pages until everything is back. Leave it off and Limit caps how many items come out, which is fine for a test and misleading for an export. If you are still deciding whether the platform fits, the n8n review goes through the trade offs, and the n8n training covers expressions and credentials in practice.

Connect

How do you connect Intercom to n8n?

  1. 01

    Create an app in your Intercom developer hub

    Start on the Intercom side, not in n8n. You need an Intercom developer account, then an app created in your developer hub, because that app is what the node's authentication depends on afterwards. Create both before you touch n8n: nothing in the workflow connects until the app exists and its token is ready to copy.

  2. 02

    Copy the Access Token Intercom generated

    Intercom automatically generates an Access Token when you create the app. Copy it from the app page in the developer hub. This token is the only secret you need for the node, and Intercom's own documentation on how to get your Access Token walks through where it sits if you cannot find it.

  3. 03

    Save the credential once in n8n

    In n8n, open the Credentials menu and create an Intercom credential. Paste the Access Token into the API Key field, save, and pick that credential from the dropdown in the node. A credential is created once and reused across every workflow, so you do this on the first build and never again.

Actions

What can the Intercom node do?

The Intercom node exposes 15 operations across 3 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateDeleteUsers
Company✓✓✓✓✓
Lead✓✓✓✓✓
User✓✓✓✓✓

Company

5 operations
01

Create a company

company.create

What you see in n8n

Notes & use cases

Writes a new company record into Intercom and returns the created object to the next node.

Key parameters

  • Company ID: the company ID you have defined for the company on your side, which is what you will query on later.
  • Industry, Size, Plan: Additional Fields describing the industry the company operates in, the number of employees in it, and the name of the plan you have associated with the company.
  • Website: the URL for this company's website. The value is not validated and any string is accepted, so clean it before sending.
Use cases
a new B2B account is signed in your billing tool and the workflow creates the matching Intercom company before the first ticket arrives.
02

Get a company

company.get

What you see in n8n

Notes & use cases

Pulls one company back and hands the record to the rest of the workflow.

Key parameters

  • Select By: what property to use to query the company, either companyId, id or name. Pick the one you actually store elsewhere.
  • Value: required, the value to look up, and it has to match whatever Select By expects. Coming from an earlier node it is an expression such as {{ $json.field }}.
Use cases
before pushing a plan change, read the account to confirm it is already in Intercom and route the branch accordingly.
03

Get many companies

company.getAll

What you see in n8n

Notes & use cases

Returns companies as a list, one n8n item per company.

Key parameters

  • Return All: on, n8n chains the API pages until every company has come back. Off, it stops at Limit, the maximum number of results returned.
  • Segment ID and Tag ID: the two Filters, to keep only the companies in one segment or carrying one tag.
Use cases
a monthly account review that exports every company with its plan into a spreadsheet, or a narrower pull of one segment for a renewal campaign.
04

Update a company

company.update

What you see in n8n

Notes & use cases

Changes an existing company record rather than adding a second one.

Key parameters

  • Company ID: the company ID you have defined for the company, used to find the record to edit.
  • Custom Attributes: a hash of key and value pairs for custom data you want to attribute, built one entry at a time with Add Attribute.
  • Plan and Size: Additional Fields for the plan name associated with the company and its employee count.
Use cases
an upgrade in billing rewrites the plan on the Intercom company, so support sees the new tier at the top of the conversation.
05

List users of a company

company.users

What you see in n8n

Notes & use cases

Lists the users attached to one company, which is the only operation that crosses two objects.

Key parameters

  • List By: id for the Intercom defined ID representing the company, or companyId for the one you gave it.
  • Value: required, the identifier matching your List By choice.
  • Return All: on for every user on the account, off to stop at Limit.
Use cases
a renewal is coming up and the workflow collects every contact on the account before deciding who gets the message.

Lead

5 operations
06

Create a lead

lead.create

What you see in n8n

Notes & use cases

Adds a lead, the record Intercom keeps for someone who has not become a user yet.

Key parameters

  • Email: required, the email of the user, in the name@email.com form.
  • Name and Phone: Additional Fields for the name and the phone number of the user.
  • UTM Campaign, UTM Medium, UTM Term: the campaign that brought them in, the type of link used, and the search terms.
Use cases
a demo request on the site lands as a lead with its campaign attached, so the first reply already knows where the person came from.
07

Delete a lead

lead.delete

What you see in n8n

Notes & use cases

Removes a lead record from Intercom. There is no undo step in the workflow, so branch carefully before it.

Key parameters

  • Delete By: id for the Intercom defined ID representing the lead, or userId for the automatically generated identifier.
  • Value: required, the identifier to delete by, matching the property you chose above.
Use cases
a deletion request arrives in the inbox, an approval step gates the workflow, and the lead is removed once someone has confirmed it.
08

Get a lead

lead.get

What you see in n8n

Notes & use cases

Reads a single lead so the workflow can decide what to do with the person.

Key parameters

  • Select By: the property to select the lead by, among email, id, userId and phone. Four ways in, which matters when your other tools store different keys.
  • Value: required, the lookup value for the property you picked.
Use cases
an inbound message arrives with only a phone number, and the workflow finds the lead by phone before routing the conversation to the right owner.
09

Get many leads

lead.getAll

What you see in n8n

Notes & use cases

Brings back a list of leads, one item each.

Key parameters

  • Return All: on to page through the whole set, off to cap it with Limit.
  • Email and Phone: the two Filters, the email address of the lead and the phone number of the lead, to narrow the pull instead of sorting afterwards.
Use cases
a nightly run collects the current leads and compares them against your CRM, so the duplicates get spotted before a human writes to both.
10

Update a lead

lead.update

What you see in n8n

Notes & use cases

Edits a lead already in Intercom, which is what keeps a record clean instead of doubled.

Key parameters

  • Update By: the property to query the lead by, userId or id.
  • Value: required, the value of that property for the lead to update.
  • Unsubscribed From Emails and Company Names or IDs: Additional Fields for the email opt out state and the companies this user belongs to.
Use cases
someone unsubscribes in your emailing tool and the same flag is written back onto the Intercom lead within the minute.

User

5 operations
11

Create a user

user.create

What you see in n8n

Notes & use cases

Creates the record Intercom keeps for an identified customer.

Key parameters

  • Identifier Type: userId, a unique string identifier required on creation if an email is not supplied, or email, required on creation if a user_id is not supplied.
  • Value: required, the unique string identifier value itself.
  • Name, Phone, Session Count, Company Names or IDs: part of the 14 Additional Fields, including how many sessions the user has recorded.
Use cases
a trial signup creates the user with the same identifier your product uses, so later updates always find the right record.
12

Delete a user

user.delete

What you see in n8n

Notes & use cases

Deletes a user record. It is the shortest operation in the node and the one to wire last.

Key parameters

  • ID: required, the Intercom defined ID representing the record. It is the only field, so the workflow has to have that identifier in hand, typically read by an earlier lookup and passed as {{ $json.field }}.
Use cases
an account closure goes through a manual approval, then the user is removed from Intercom in the same run that closes the billing side.
13

Get a user

user.get

What you see in n8n

Notes & use cases

Fetches one user and makes the record available to every node downstream.

Key parameters

  • Select By: the property to select the user by, id for the Intercom defined ID or userId for the automatically generated identifier.
  • Value: required, the value to view by. Note that it expects an identifier, not a name.
Use cases
a ticket arrives from your helpdesk with an internal user id, and the workflow reads the Intercom record to enrich the alert it posts to the team.
14

Get many users

user.getAll

What you see in n8n

Notes & use cases

Returns users as a list, and it carries the widest set of filters in the node.

Key parameters

  • Return All: on to chain the pages, off to stop at Limit.
  • Company ID, Email, Segment ID, Tag ID: the 4 Filters, respectively the company representing the user, the email address, the segment and the tag.
Use cases
a churn review pulls every user carrying one tag, counts them by company, and hands the list to the account team.
15

Update a user

user.update

What you see in n8n

Notes & use cases

Rewrites fields on an existing user, the operation most workflows end on.

Key parameters

  • Update By: the property to query the user by, id, email or userId.
  • Value: required, the value of that property for the user to update.
  • Update Last Request At: whether to instruct Intercom to update the user's last_request_at value to the current API service time in UTC.
Use cases
a nightly sync writes the current session count and plan onto each user, so the support view matches the product.
Need help

Need help automating Intercom with n8n?

A person reads every message.

FAQ

Intercom and n8n, the questions that come next

01Is the Intercom n8n integration free?
On the n8n side, yes. The Intercom node ships with n8n, so there is nothing to install and no extra cost to unlock it. That holds on n8n Cloud, the hosted offering run by n8n, and on an instance you host yourself with Docker or npm under the Community Edition and its Sustainable Use licence. A workflow behaves the same either way, which means you can build on Cloud and move later without rewriting nodes. What Intercom itself costs is a separate question and depends on your plan with them, so check that on their side before you count the savings.
02What credentials do you need to connect Intercom to n8n?
One credential, built on an API key. The supported authentication method for this node is an API key, and the value you use is the Access Token that Intercom automatically generates when you create an app in your developer hub. So the prerequisites are an Intercom developer account and an app, both created before you open n8n. In n8n you create the Intercom credential once from the Credentials menu, paste the Access Token into the API Key field, and every workflow afterwards picks it from the node dropdown. The node itself has no authentication selector, so there is nothing else to choose.
03What are the limits of the Intercom node in n8n?
The node exposes 15 operations over 3 objects: companies, leads and users. Anything beyond those operations goes through the HTTP Request node, which reaches any endpoint of the Intercom API and reuses the same credential through predefined authentication, so you are not blocked, you just build that step yourself. The other thing to watch is pagination. On the list operations, Return All chains the API pages until everything has come back, and with it switched off Limit caps the number of items returned. A test run that looks complete can be a truncated list, so check that box before you trust an export.
04How do you trigger an n8n workflow from Intercom?
There is no Intercom trigger node in n8n, so the workflow starts somewhere else. The two common starts are a Schedule Trigger, which runs the workflow at a fixed interval and then reads with Get many users or Get many companies, and the n8n Webhook node, which gives you a URL that a third party service calls to start the run. The trigger of another tool works too: a form, a payment, a new row, whatever already signals the event you care about. From there the Intercom node does the reading or writing, and the choice between polling on a schedule and being called by a webhook is yours to make per use case.
05n8n or Make for Intercom?
It depends on what you weigh most. Make is a hosted automation platform with no self-hosting option and billing per operation, so cost tracks volume and the data passes through their infrastructure. n8n runs on Cloud or on your own server, which matters when customer conversations and contact records are involved and you would rather keep them in house. The other split is the cost model: per operation on one side, per instance or plan on the other, which changes the maths once a workflow loops over every user on an account. Both build visually. Try the Intercom node on one real workflow and judge from there.
Same platform

Other docs you might need on this stack.

Browse all integrations