n8n + Intercom Integration: Automate Customer Messaging Workflows

The n8n Intercom integration turns your customer messaging platform into the trigger point for dozens of automated workflows. Instead of manually triaging conversations, tagging contacts, or copying data between tools, you can wire Intercom events directly into your support, sales, and product operations — and have n8n handle the busywork.

Intercom handles over 500 million conversations per month across its customer base, and most support teams still manually route, tag, and escalate a significant portion of those. If your team spends time on repetitive Intercom tasks, automation is the obvious next step.

Why Connect n8n and Intercom

Intercom is a powerful customer messaging platform, but its built-in automation (Custom Bots, Series) has limits. You can trigger messages and simple routing inside Intercom, but the moment you need to involve an external tool — your CRM, a project tracker, a database, a notification channel — you're stuck copying data manually or paying for another SaaS integration tool.

n8n bridges that gap. With the Intercom node, you can listen for events like new conversations, user creation, or tag changes, then route that data anywhere across n8n's 400+ integrations. Some practical use cases:

• Route leads from Intercom to HubSpot, Salesforce, or Pipedrive based on company size or plan
• Escalate urgent tickets to Slack or Microsoft Teams with full conversation context
• Sync contact data between Intercom and your database or CRM on every update
• Trigger onboarding sequences when a user signs up or hits a product milestone
• Automate NPS follow-ups based on score ranges and customer segments

Because n8n is open-source and self-hostable, you keep full control over your data — a real advantage for teams handling sensitive customer information.

Setting Up the Intercom Node in n8n

Before building workflows, you need to connect your Intercom account to n8n. Here's how:

1. Open your n8n instance and go to Credentials → Add Credential → search for Intercom
2. Select the OAuth2 authentication method (recommended) or use an Access Token from Intercom's developer settings
3. For OAuth2: click Connect, sign in to your Intercom workspace, and authorize the connection
4. For Access Token: go to Intercom → Settings → Integrations → Developer Hub → create a new app, copy the Access Token, and paste it into n8n
5. Click Save and test the connection

The Intercom node in n8n supports several resources: Company, Contact (formerly Lead/User), Conversation, and Tag. Each resource has operations like create, get, update, delete, and list. For trigger-based workflows, you'll use the Intercom Trigger node, which listens for webhook events from Intercom.

Auto-Tag and Route Intercom Conversations by Topic

Manually tagging every incoming conversation is tedious and inconsistent. This workflow reads new Intercom conversations, classifies them, and applies the right tag automatically.

Workflow nodes:

1. Intercom Trigger — set the event to conversation.created
2. IF node — check the conversation body for keywords. For example, branch on whether {{ $json.data.item.conversation_message.body }} contains "billing", "bug", "feature request", or "cancel"
3. Intercom node (Tag → Add) — for each branch, add the corresponding tag (e.g., "billing-issue", "bug-report", "feature-request", "churn-risk")
4. Intercom node (Conversation → Assign) — optionally assign the conversation to the right team based on the tag

For more advanced classification, replace the IF node with an OpenAI node or AI Agent that reads the message and returns a category. This handles edge cases that simple keyword matching misses — like a customer saying "I want my money back" getting tagged as both "billing-issue" and "churn-risk".

Lead Qualification: Intercom to CRM Pipeline

When a new lead starts a conversation in Intercom, you want them in your CRM pipeline fast — especially if they match your ideal customer profile. This workflow qualifies leads and pushes them to your sales tool automatically.

Workflow nodes:

1. Intercom Trigger — event: contact.created or conversation.created
2. Intercom node (Contact → Get) — fetch full contact details including company, plan, and custom attributes
3. IF node — qualify the lead based on your criteria. Example: company size > 50 employees AND plan equals "business" AND location in target regions
4. HubSpot node (Contact → Create) — for qualified leads, create or update a contact in your CRM with all Intercom data mapped
5. HubSpot node (Deal → Create) — create a deal in your sales pipeline, set the stage to "New Lead", and assign to the right sales rep
6. Slack node — notify your sales channel: "New qualified lead from Intercom: [Company Name] — [Deal Link]"

The alternative branch (non-qualified leads) can still add the contact to a nurture list in Mailchimp or your email tool for later follow-up.

Escalate High-Priority Tickets to Slack

Not every conversation needs immediate attention, but VIP customers and urgent issues should never sit in a queue. This workflow watches for priority signals and pushes them to Slack (or Microsoft Teams) in real time.

Workflow nodes:

1. Intercom Trigger — event: conversation.created
2. HTTP Request node — call the Intercom API to fetch the contact's company data and check their plan tier or MRR custom attribute
3. Switch node — route based on priority level:
   • Critical: enterprise plan OR MRR > $5,000 OR message contains "down", "outage", "urgent"
   • High: business plan OR MRR > $1,000
   • Normal: everything else
4. Slack node — for critical and high priority, post to #support-escalations with a rich message block that includes the customer name, company, MRR, conversation snippet, and a direct link to the Intercom conversation
5. Intercom node (Conversation → Add Tag) — tag the conversation as "escalated" so agents see the priority immediately

This workflow ensures your highest-value customers get a human response within minutes, not hours. You can add a PagerDuty or Twilio SMS node for truly critical escalations outside business hours.

Sync Intercom User Data Across Your Stack

Customer data lives in too many places — Intercom, your CRM, your database, your billing system. When someone updates their info in one tool, the others go stale. This workflow keeps everything in sync.

Workflow nodes:

1. Intercom Trigger — event: contact.updated (fires when any contact attribute changes)
2. Set node — extract and normalize the fields you care about: email, name, company, phone, plan, custom attributes
3. Parallel branches (use n8n's split/merge pattern):
   • PostgreSQL node — upsert the contact record in your database using email as the key
   • HubSpot node — update the matching CRM contact
   • Google Sheets node — append or update a row in your master customer sheet (useful for ops teams who live in spreadsheets)
4. Merge node — rejoin the branches and log the sync result

Run this on a dedicated n8nautomation.cloud instance so syncs happen 24/7 without worrying about uptime. The managed infrastructure handles automatic backups and keeps your workflows running even during high-volume periods.

Automated NPS Follow-Up Workflow

Collecting NPS scores is only useful if you act on them. This workflow triggers personalized follow-ups based on the score a customer submits through Intercom's surveys.

Workflow nodes:

1. Webhook node — receive NPS survey responses from Intercom (configure this in Intercom under Surveys → Webhook delivery, pointing to your n8n webhook URL)
2. Switch node — route by NPS score:
   • Promoters (9-10): these are your advocates
   • Passives (7-8): satisfied but not enthusiastic
   • Detractors (0-6): unhappy customers who need attention
3. Promoter branch:
   • Intercom node (Message → Create) — send a thank-you message with a link to leave a G2 or Capterra review
   • Intercom node (Tag → Add) — tag them as "nps-promoter" for future reference campaigns
4. Detractor branch:
   • Intercom node (Conversation → Create) — open a new conversation: "We noticed you had a less-than-ideal experience. Our team lead would love to chat — what's the best time?"
   • Slack node — alert the CS team with the customer's score, account details, and recent conversation history
   • Google Sheets node — log detractors in a tracking sheet for weekly review
5. Passive branch:
   • Intercom node (Tag → Add) — tag as "nps-passive"
   • Mailchimp node — add to a nurture sequence highlighting features they might not be using

This turns a vanity metric into a retention engine. Detractors get personal attention before they churn, and promoters get channeled toward activities that grow your brand.

Each of these workflows takes 15-30 minutes to build in n8n's visual editor. Start with the one that addresses your biggest pain point — usually conversation routing or ticket escalation — and layer on more automations as your team gets comfortable. With a managed instance on n8nautomation.cloud, you skip the server setup entirely and go straight to building workflows that save your support team hours every week.