By Helpdesk

Intercom automation: Workflows, assignment, Fin and the API

By Roman Zakharenko · Facts checked October 19, 2026

Intercom automation is built mainly in Workflows: a visual builder where a trigger starts the flow, branches pick a path and actions do the work, such as tagging, assigning or letting Fin answer. Each team inbox's assignment method then decides which teammate gets the conversation, and webhooks plus the REST API cover anything that has to happen outside Intercom. Below is how each piece behaves and where to start.

At a glance

Workflows are built in a visual builder and can be customer-facing or run silently in the background for teammates.
With branches, a conversation follows only the first matching path; Apply rules runs every matched path.
Only one SLA can be applied to a conversation; later SLA actions from other workflows are ignored.
Balanced assignment gives a conversation to the eligible teammate with the fewest open conversations.
Webhook subscriptions are created in the Developer Hub, not through the API, and the endpoint must use HTTPS.

How Intercom Workflows are built

Workflows are Intercom's single place to automate customer conversations and teammate processes. You build them in a visual builder from reusable steps. A workflow can be customer-facing, like a bot that greets and triages, or run silently in the background for your team. Every workflow combines the same few kinds of steps.

The building blocks of an Intercom workflow
Building block	What it does	Examples
Trigger	Sets when the workflow starts and for whom	When a conversation starts, during a conversation, on a ticket event, or when another workflow calls it as a reusable workflow
Branches	Check conditions and send the conversation down the first path whose condition matches	Separate paths for different audiences, channels or topics
Apply rules	Checks every path and runs the actions of each one that matches	Several independent tags or attributes set in one step
Actions	Do the work	Tag, assign, snooze, set priority, apply an SLA, let Fin answer, notify Slack

The difference between branches and Apply rules matters when conditions overlap. With branches, a conversation that meets several conditions only follows the first matching path, read from top to bottom, so put the most specific conditions first. Apply rules runs the actions of every matched path, which suits steps that should stack rather than compete.

Inbox automation: assignment, priority and SLAs

Most inbox automation is a background workflow made of actions. Assign sends a conversation to a chosen teammate or team inbox. Tag adds a tag, and tags are created and managed in your workspace settings. Snooze temporarily removes the conversation from the teammate inbox; if the customer or a teammate replies during the snooze, the workflow ends. Set priority marks how urgent the conversation is.

SLAs are applied with an action too, but only one SLA can be added to a conversation. If a later workflow tries to apply another SLA, that action is ignored, so decide which workflow owns SLAs before you build several of them.

Once a conversation lands in a team inbox, that inbox's assignment method decides who gets it: manual, round robin or balanced. Balanced assignment gives each new conversation to the eligible teammate with the fewest open conversations, and breaks ties in favour of the teammate who has waited longest for one. To be eligible, a teammate must be active and under their assignment limit. Intercom recommends balanced assignment for support teams.

A simple starting pattern: one background workflow on new conversations tags them by topic, sets priority, applies a single SLA and assigns them to the right team inbox. The inbox's assignment method then picks the teammate.

Fin AI Agent in your workflows

Fin AI Agent is Intercom's AI agent for answering customer questions. It answers from the content you give it: public articles, documents, snippets and public URLs, which you manage under Knowledge > Sources. It respects audience targeting on Intercom articles, so it won't answer from private or restricted articles that the customer on Messenger isn't allowed to see.

Fin is supported on Intercom Messenger on web, iOS and Android, and on email, WhatsApp, SMS, Facebook and Instagram. Inside Workflows, a 'Let Fin answer' step lets Fin respond at any point in the flow and keep going until the issue is resolved or escalated to a teammate.

Plan the handoff as carefully as the answers. Decide which team inbox an escalated conversation should go to, and build that path in the workflow so it never sits unassigned.

Webhooks and the Intercom REST API

When something in Intercom needs to reach another system, use webhooks. You set them up in the Developer Hub: open your app, go to Configure, then Webhooks, and enter your endpoint URL. The endpoint must use HTTPS and must accept a HEAD request, which Intercom uses to validate the URL. Subscriptions can only be created in the Developer Hub, not through the API.

Next you pick topics. A topic is an event inside Intercom that triggers the webhook, and each topic is tied to one or more permissions your app must have. Intercom sends an HTTP POST to your endpoint for every topic you subscribe to, and each payload includes the topic and a delivery attempt count. The 'Send a test request' button in the webhooks section lets you check the endpoint.

To act on conversations from your own code, use the REST API. Requests go to api.intercom.io with an access token sent as a Bearer token in the Authorization header, plus an Intercom-Version header that defaults to the version set in your app. Replying, for example, is a POST to /conversations/{id}/reply with a JSON body that sets the message type, the author type and the message body.

Good first candidates for Intercom automation:

Tagging new conversations and assigning them to the right team inbox.
Applying one SLA per conversation and raising priority for key accounts.
Sending conversation events to a webhook so Make or n8n can update other systems.
Posting new or escalated conversations to a Slack channel.

Slack and Jira integrations

For Slack alerts, set a Slack channel's purpose to notification-only, then add a 'Notify Slack' step to a workflow. The Intercom app posts the notification, and later notifications for the same conversation appear as thread replies under the original message. Replies typed in that thread are not sent back to the Intercom conversation, so teammates still answer customers in Intercom.

For engineering escalations, Intercom's Jira for Tickets app can automatically create Jira issues from the ticket types you specify, mirror Jira issue statuses back to the Intercom tickets and sync notes. Its basic automation maps only the title and description; for more fields, use its custom automation built on Workflows templates. It doesn't create issues straight from conversations, so a conversation has to be converted into a ticket first.

Getting this built

TascaLab builds on top of the tools you already use, with no platform switch, using APIs, webhooks and Make or n8n. Intercom has both a REST API and webhooks, so it can almost certainly be connected; the specific setup is confirmed on a free 30-minute Health Check call. Ticket Routing & Categorization is a one-time project at $775, and Custom Automation for flows across several systems is from $1,200. Every project includes 30 days of post-launch support, basic documentation and no hidden fees, and most setups take 1–3 weeks.

Frequently asked questions

What is the difference between branches and Apply rules in Intercom Workflows?

Branches send the conversation down only the first path whose condition matches, checked from top to bottom. Apply rules checks every path and runs the actions of each one that matches.

Which assignment method does Intercom recommend for support teams?

Balanced assignment. It gives each conversation to the active teammate under their assignment limit who has the fewest open conversations, with ties going to whoever has waited longest.

What content does Fin AI Agent use to answer customers?

Public articles, documents, snippets and public URLs that you add under Knowledge > Sources. It respects article audience targeting, so it won't answer from articles the customer can't see.

Can I create Intercom webhook subscriptions through the API?

No. Webhook subscriptions are set up in the Developer Hub. The endpoint must use HTTPS and accept a HEAD request, which Intercom uses to validate it.

Can teammates reply to customers from Intercom's Slack notifications?

No. In a notification-only Slack channel, replies in a notification's thread are not sent back to the Intercom conversation.

Want this set up for your team?

Book a free Health Check: a 30-minute call and a written report with 2–3 concrete recommendations, a fixed price and estimated running costs. No pitch.

Reviews on Upwork