How to connect Intercom to Slack

Support conversations live in Intercom. Team decisions happen in Slack. When those two systems stay disconnected, response times drift and context gets lost between tabs. Learning how to connect Intercom to Slack closes that gap — alerts reach the right channel, conversations get resolved faster, and nobody has to check two dashboards.

The good news: Intercom offers a native Slack integration that handles basic notification routing. But most teams outgrow it within a month. According to Intercom's 2025 customer service trends report, 73% of support teams now use three or more communication channels simultaneously. Slack's Workforce Index (2025) found that context-switching between tools costs the average knowledge worker 32 minutes per day.

Unlike generic AI automation posts, this guide shows real CodeWords workflows — not just theory. You will see the native integration, its limits, and how to build something better.

Browse more: CodeWords integrations, templates, pricing.

TL;DR

• Intercom has a native Slack app that posts conversation notifications to channels — quick to set up, limited in customization.
• For filtered alerts, AI-powered routing, or bidirectional replies, you need a workflow beyond the native integration.
• CodeWords lets you build serverless Intercom-to-Slack pipelines with LLM-based triage, custom formatting, and reply-from-Slack functionality.

How does the native Intercom-Slack integration work?

Intercom's built-in Slack app connects in a few clicks:

1. In Intercom, go to Settings → Integrations → Slack.
2. Authorize your Slack workspace.
3. Choose which conversation events trigger Slack notifications (new conversations, replies, assignments, notes).
4. Map Intercom inboxes or teams to specific Slack channels.

Once connected, new Intercom conversations appear as Slack messages with a link back to the Intercom thread. Team members can see the customer name, message preview, and assigned teammate.

The native integration works well for small teams with a single inbox. It falls apart when you need to filter by priority, route by topic, enrich messages with customer data, or reply directly from Slack without opening Intercom.

What are the limitations of the native integration?

Four friction points push teams toward custom solutions:

No intelligent routing. The native app maps inboxes to channels. It cannot route a billing question to #support-billing and a bug report to #engineering-bugs based on message content. Every conversation lands in the same channel unless you manually move it.

No enrichment. The Slack notification shows the message text and customer name. It does not pull in account value, plan tier, previous tickets, or NPS score. Your team clicks through to Intercom every time for context.

No reply from Slack. You can see the alert in Slack but cannot respond without switching to Intercom. For teams that live in Slack, this is a workflow killer.

No filtering. High-volume inboxes generate dozens of notifications per hour. Without filters, the Slack channel becomes noise. Important conversations drown in routine messages.

How do you build a smarter Intercom-to-Slack workflow?

A CodeWords workflow solves each limitation with a serverless pipeline:

Step 1: Listen for Intercom events. Register a webhook in Intercom's developer hub. Point it at a CodeWords endpoint. Each new conversation or reply sends a JSON payload to your workflow.

Step 2: Enrich the data. Use the Intercom API to pull the customer's company, plan, total spend, and conversation history. Attach this context to the Slack message.

Step 3: Classify with AI. Pass the message through an LLM (OpenAI, Anthropic, or Gemini — all available natively in CodeWords) to classify the topic: billing, bug, feature request, onboarding, or general. Assign a priority: urgent, high, normal, low.

Step 4: Route to the right channel. Based on the classification, post to the appropriate Slack channel. Format the message with blocks: customer info, message preview, priority badge, and action buttons.

Step 5: Enable reply from Slack. Use Slack's interactivity API to capture replies and post them back to Intercom via the Intercom API. The support agent never leaves Slack.

This pipeline replaces a rigid integration with a system that adapts. Add a new category? Update the LLM prompt. Change routing rules? Edit a dictionary. No rebuilding connectors.

Related reading: Slack API events, workflow automation examples, AI workflow automation, no-code automation.

How do you filter alerts to reduce noise in Slack?

Volume control matters. A support team processing 500 conversations per day cannot dump all 500 into a single Slack channel.

In a CodeWords workflow, add filtering logic after the enrichment step:

• By priority: Only post urgent and high-priority conversations to #support-escalations. Batch normal-priority summaries into a daily digest.
• By customer tier: Enterprise customers alert #support-enterprise. Free-tier users route to #support-community or a separate queue.
• By keyword: Conversations mentioning "cancel," "downgrade," or "billing error" trigger an immediate alert to #retention.
• By time: Outside business hours, route to an on-call channel instead of the full team channel.

Zapier and Make can handle simple keyword filters, but they cannot run LLM classification or combine multiple filter dimensions in a single step. CodeWords handles all of this in one workflow.

Can you summarize conversation threads before posting to Slack?

Yes — and this is one of the highest-value patterns for busy teams.

Instead of posting every message in a long Intercom thread, the workflow waits for a configurable window (e.g., 5 minutes of inactivity), pulls the full thread, summarizes it with an LLM, and posts a single Slack message with the summary, key customer quotes, and recommended action.

This turns a 15-message thread into a three-sentence brief. The engineer or PM reading the Slack channel gets the signal without the noise.

You can chain this with Perplexity or SearchAPI.io lookups to add external context — for example, checking whether the reported bug matches a known issue in your public status page.

See also: AI automation examples, automated lead management, workflow automation platform.

FAQs

Can I connect multiple Intercom workspaces to one Slack workspace?

Yes. Each Intercom workspace registers its own webhook. Your CodeWords workflow receives payloads from all of them and routes based on a workspace identifier in the payload.

Does the native Intercom-Slack integration support threads?

Partially. Follow-up messages can appear as thread replies in Slack, but you cannot reply from the Slack thread back to Intercom without a custom integration.

How fast are Intercom webhook deliveries?

Typically under 5 seconds. Intercom retries failed webhook deliveries with exponential backoff for up to 24 hours, so your workflow receives events reliably.

Can I trigger Intercom actions from Slack?

With a custom workflow, yes. Slack buttons or slash commands can call the Intercom API to assign conversations, add tags, snooze threads, or close tickets — all without leaving Slack.

Connect Intercom and Slack the right way

The native integration is a starting point. For intelligent routing, AI classification, enrichment, and reply-from-Slack, a CodeWords serverless workflow gives you the control and flexibility that a pre-built connector cannot.

Build your Intercom-Slack workflow on CodeWords — ship it today.