Intercom Make integrationAutomate Intercom with Make.

Routes a thread to the admin or the team who should answer it, so nobody has to drag it by hand in the inbox. Pair it with a tag set earlier in the scenario to decide who gets what.

Links a person to the account they belong to, or breaks that link when they move on. Your agents then see the right company next to each contact during a chat.

Puts a label on a whole account, or removes it, so segments and reports in Intercom can group companies without manual tagging. Useful whenever the signal comes from another tool.

Labels an individual person, or clears the label, which keeps outreach lists and inbox views honest without a teammate clicking through profiles. It works on users and leads alike.

Marks a thread with a topic label, or takes the label off, so inbox views and reports can sort by subject. It is the brick most triage scenarios start with after the trigger.

Shuts a thread once the work behind it is done elsewhere, keeping the open queue limited to what really needs an answer. Agents stop chasing tickets that are already settled.

Adds a new person to Intercom, either as a user or as a lead, from data collected in another app. Your team can then chat with them or target them without importing a file.

Opens a thread as if the user or lead had written in, so a message captured outside Intercom lands in the same inbox as every chat. Agents answer it with their usual tools.

Leaves an internal note on someone's profile, visible to your team and not to the customer. It brings context from other tools right where the agent looks during a chat.

Sends a message from one of your admins, in-app or by email, which starts a conversation from your side. Replies come back into the Intercom inbox like any other thread.

Writes an account record in Intercom, creating it the first time and updating it afterwards, so one module covers both cases. Company data stays aligned with your billing or CRM tool.

Defines a custom attribute for contacts or companies, or changes an existing one, so Intercom has a place to store the data your other tools send. It shapes the schema rather than a single record.

Makes sure a label exists in Intercom, creating it or renaming it as needed, before other modules attach it anywhere. Your tag list stays in step with categories defined elsewhere.

Removes a person from Intercom, handy when another system is the reference for who should stay. It keeps test entries and outdated leads from cluttering views.

Drops a label from the workspace once it no longer means anything, so agents stop picking dead tags. Cleanup follows the source of truth instead of someone remembering to do it.

Pulls one account's details from Intercom so later modules can use them, for example to enrich a message or update a spreadsheet. You get a single bundle back, not a list.

Fetches the full profile of one person so the rest of the scenario can read their attributes. It is the lookup to place right after a trigger that only carries an identifier.

Reads back one specific note left on a profile, so its text can travel to another tool. It works when you already know which note you want.

Loads one thread with its details so you can decide what to do next: tag it, assign it, copy its content. It turns a bare event into data the next modules can map.

Returns the profile of one teammate who works in your Intercom inbox, which helps when a message or a report needs their name. It saves maintaining a separate staff list.

Tells you which Intercom account the connection is using, a quick way to confirm you are pointed at the right workspace. It is more a setup check than a daily brick.

Retrieves one saved audience from Intercom, so its details can feed a report or a decision further down the scenario. It gives you the segment itself, not its members.

Opens the rest of the Intercom API to your scenario, reusing the connection you already set up. Anything the listed modules leave out can still be reached from here.

Clears the unread state on a thread, which keeps counters meaningful when a scenario already handled the message. Agents focus on threads that truly wait for them.

Folds an anonymous lead into the signed-up user it turned into, so the chat history and the account live on one profile. No more duplicate people in reports.

Brings a parked or finished thread back into the open queue, so an agent picks it up again. It is the counterpart of Close a Conversation and Snooze a Conversation.

Adds a message to an existing thread, on behalf of a contact or an admin, or posts an internal note only admins see. One module, three ways to speak inside a conversation.

Switches a teammate to away in the inbox, so Intercom stops treating them as available. Staffing changes made elsewhere show up without anyone flipping the toggle.

Parks a thread until a future date, when it comes back to the inbox by itself. Agents stop seeing tickets that are waiting on something outside their control.

Records something a person did in your product or another tool on their Intercom timeline. Agents and messages can then rely on actions Intercom never saw directly.

Changes attributes on an existing person, keeping their Intercom profile in line with the tool that owns the data. Agents stop working from stale details.

Fills or changes the custom attributes on a thread, the extra fields your workspace defined for conversations. Reports and views can then slice tickets by data coming from outside Intercom.

Adds another person to a thread, or removes one, so the right participants see the exchange. It helps when a question involves a colleague of the original sender.

Returns the trail of actions taken by all your admins, one bundle per entry, ready to archive or review in another tool. It gives you an audit view outside Intercom.

Brings back every teammate in your Intercom workspace, useful to build rotations or sync the team roster elsewhere. You get one bundle per admin.

Pulls your companies together with the users attached to them, which suits exports and cross-checks with a CRM. Each company arrives as its own bundle.

Retrieves all companies from a workspace with a big account base, as a variant made for volume. Pick it when the regular listing is not meant for the size you handle.

Gives you every person attached to one company, so a single account-level signal can reach each of its people. One bundle per contact comes out.

Shows which saved audiences a company falls into, a quick way to know how Intercom currently classifies that account. The answer can steer the next module.

Returns all your users and leads, one bundle each, the starting point for exports, clean-up passes or bulk updates. It covers the whole contact base, not a single person.

Hands you every company a given person is linked to in Intercom, each one as a separate bundle (one item passed to the next module). Handy when a single contact works with several accounts.

Hands you the events recorded for one contact in Intercom, such as those your product sends there, so your scenario reacts to what the person really did.

Pulls back all the internal notes your team left on one contact, one bundle per note. Useful for carrying that context into a CRM, a report or a handover message.

Tells you which Intercom segments a person currently falls into, so the rest of the scenario can branch on that audience instead of rebuilding the rule elsewhere.

Returns the tags stuck on one contact, which lets a scenario check a label before acting, for example skipping anyone marked as a partner or a churn risk.

Gives you your Intercom conversations as individual bundles, ready to copy into a spreadsheet, a dashboard or a support review without exporting anything by hand.

Shows you the attributes Intercom stores on contacts or on companies, both the standard ones and the custom ones your team added. It is the map you check before mapping data between tools.

Gives you the full catalog of segments defined in your Intercom workspace, so a scenario can look up an audience by name or copy the list into another tool.

Lists every tag that exists in your workspace, one bundle each, which is the quickest way to spot duplicates or find the exact tag name a later module expects.

Finds only the conversations that match your query, rather than dumping the whole inbox. A search module can return zero, one or many bundles, so plan for each case.