Intercom integration

Intercom customer messaging automation

Intercom is the customer messaging and support platform teams use for live chat, help center articles, tickets, and a shared record of every contact and company. The NoClick Intercom node works against the Intercom API, so one workflow can create or update contacts and companies, attach a contact to its company, add internal notes, open conversations and tickets, and manage help center articles and tags. Contacts can be archived or deleted and records fetched by lookup, which keeps routine support upkeep running on its own instead of by hand. Drop it on the canvas to keep your Intercom data current from whatever system your customers actually live in.

What you can automate with Intercom

Intercom operations

Triggers4

Contacts16

Conversations8

Tickets6

Companies5

Messaging2

Workspace7

Help Center5

Templates using Intercom

Intercom Support Agent

Answers the questions your playbook covers in Intercom within seconds, and leaves an internal note plus a Slack ping the moment a conversation needs a person. Half of live chat is the same handful of questions, and the other half is the reason people still need to be reachable. This agent takes the first half instantly, in a sentence or two, using only the playbook you wrote, and refuses to guess at the rest. Anything about money, access, or a customer losing patience gets an acknowledgement, an internal note with the context, and a Slack ping, so a human picks it up already knowing what happened. ## What people use it for - **Instant answers to repeat questions** - A small set of questions makes up most of a chat inbox, and each one still costs an agent a context switch. Those get answered in seconds without anyone opening Intercom. - **Cover the hours you are asleep** - Customers in other timezones get a real answer instead of a form and a wait. Anything the playbook does not cover is handed over with a note, ready for the morning. - **Handovers that carry context** - When it escalates, the note already says what the customer wants, what was checked, and what is blocking. That is the difference between picking up a conversation and restarting it. - **One playbook, one answer** - Chat is where improvised answers become promises. Grounding every reply in a written playbook keeps limits and pricing consistent, and keeps unwritten promises out of the thread. ## Before you fork **What do I need to connect before it runs?** An Intercom connection that can read conversations and contacts and write replies and notes, plus the Slack channel where handovers should land. You then write two things: the playbook of answers you are happy for it to give, and the rules for what a person must own. Start the playbook narrow, since it only replies to what the playbook covers, and widen it once you have read a week of transcripts. **How do I stop it answering things it should not?** Anything outside the playbook is a handover by design, so the playbook is the whole control surface. Money, refunds, account access, cancellations, and angry customers escalate regardless of what the playbook says, and it is barred from promising a refund, a discount, a callback time, or a fix date. **What does it cost to run?** One agent run per conversation event it receives, so cost follows chat volume. Escalations are cheaper than answers because it stops after a note and a Slack line rather than composing a reply. If your Intercom fires on more event types than you want triaged, narrow the trigger before going live.

91904 nodes

Questions

Yes. The Intercom node creates or updates contacts, attaches them to companies, adds internal notes, applies tags, and can archive or delete a contact when it is no longer active. Wire any of these to a trigger, so a form submission, a schedule, or an inbound event can keep your Intercom records current on its own.

Yes. The node exposes trigger operations for contact events, conversation events, company and workspace events, and ticket events. When one fires, your workflow starts automatically and can look up the related record, tag it, add a note, or open a ticket in response.

You authenticate the node with your Intercom access token, after which every operation runs against your workspace. Once connected, the same credential covers contacts, companies, conversations, tickets, tags, and help center articles, so you only set it up once.

Yes. The node can create, fetch, and delete Intercom help center articles. That lets a workflow publish approved content, pull an existing article for review, or remove outdated pieces on a schedule.

Yes. Alongside contact and company operations, the node can create conversations and create tickets. Pair that with the conversation and ticket triggers and a workflow can both react to incoming support activity and open new records for the team to handle.