Automate Slack & Intercom

Stop paying for mismatched spreadsheets. Sync data between Slack and Intercom in real-time, so you can manage your operations without the busywork.

Get This Workflow Built

Custom API Integration

Secure Data Transfer

Done-For-You Setup

How the Data Flows

graph LR
    subgraph Source ["Slack"]
        T1(["Fetch Custom Actions"])
    end
    
    subgraph Middleware ["Enterprise Integration Core"]
        W[Webhook
Listener] --> V{Validation
& Auth}
        V -->|Fail| DLQ[Dead Letter
Queue]
        V -->|Pass| Map[Data Mapping
& Transformation]
        Map --> Retry[Rate Limiting
& Retries]
    end
    
    subgraph Target ["Intercom"]
        A1(["Add Event Legacy"])
    end

    T1 -->|JSON Payload| W
    Retry -->|Authenticated API POST| A1

    style Source fill:transparent,stroke:#cbd5e1,stroke-dasharray: 5 5
    style Target fill:transparent,stroke:#cbd5e1,stroke-dasharray: 5 5
    style Middleware fill:#f8fafc,stroke:#94a3b8,stroke-width:2px
    style T1 fill:#3b82f6,stroke:#fff,stroke-width:2px,color:#fff
    style W fill:#1f2937,stroke:#fff,stroke-width:1px,color:#fff
    style V fill:#1f2937,stroke:#fff,stroke-width:1px,color:#fff
    style Map fill:#1f2937,stroke:#fff,stroke-width:1px,color:#fff
    style Retry fill:#1f2937,stroke:#fff,stroke-width:1px,color:#fff
    style DLQ fill:#ef4444,stroke:#fff,stroke-width:1px,color:#fff
    style A1 fill:#e11d48,stroke:#fff,stroke-width:2px,color:#fff

When Slack and Intercom operate independently, support teams often face delays in responding to customer inquiries. For example, if a customer sends a message in Slack regarding an issue, a support agent may manually transcribe that information into Intercom, leading to potential data loss or miscommunication. This manual entry not only consumes valuable time but also increases the risk of errors, such as incorrect customer details or incomplete issue descriptions, ultimately frustrating both the support team and the customer.

Top Ways to Automate Slack & Intercom

Automated Customer Notifications: Instantly notify your team in Slack whenever a new message or ticket is created in Intercom, ensuring no customer inquiry goes unnoticed.
Real-Time Status Updates: Automatically update Slack channels with the status of ongoing customer interactions in Intercom, keeping your team informed and aligned without manual updates.
Streamlined Feedback Loop: Capture customer feedback from Intercom and automatically post it to designated Slack channels, facilitating immediate team discussions and action on customer insights.

How to Build the Slack → Intercom Sync

In Slack, set up a Standard Webhook by navigating to Apps > Manage Apps > Custom Integrations > Incoming WebHooks. Create a new webhook and select the channel to which messages will be sent.
Configure the webhook to listen for specific messages or events, such as when a new support request is posted in the designated Slack channel.
In the webhook configuration, set the payload to include relevant data such as user_id, message_text, and timestamp.
Use the Intercom REST API to insert new conversations. The endpoint is https://api.intercom.io/conversations. Ensure you include the necessary headers: Authorization: Bearer YOUR_ACCESS_TOKEN and Content-Type: application/json.
Map the extracted data from the Slack webhook to the Intercom API payload. For example, set user_id to user_id, message_text to body, and timestamp to created_at.
Test the integration by sending a message in Slack and verifying that a new conversation is created in Intercom with the correct details.

Developer Warnings & API Gotchas

Ensure that the user_id from Slack matches the corresponding Intercom user. If the mapping is incorrect, the conversation may not associate with the right customer profile.
Be cautious about the payload size limitations of the Intercom API. If the message text exceeds the character limit, it may result in failed API calls.
When extracting data from Slack, ensure that the timestamp is formatted correctly as a UNIX timestamp in seconds, as Intercom expects this format for the created_at field.

Supported API Operations

We leverage official, stable endpoints to ensure secure data transfer. No deprecated legacy routes.

When this happens in Slack... Fetch Custom Actions

Do this in Intercom Add Event (Legacy)
When this happens in Slack... List Canvas Sections

Do this in Intercom Add Note
When this happens in Slack... List Canvases

Do this in Intercom Add Tag to Contact
When this happens in Slack... List Channels available for User

Do this in Intercom Add Tag to User (Legacy)
When this happens in Slack... List Private Channels available for User

Do this in Intercom Add/Remove Tag on Company

SyncMatrix Experts

Available for Hire

We are an AI-powered automation team. We build custom, reliable API workflows that eliminate manual data entry.

Speak with an Integration Architect

We build custom API workflows that don't hit rate limits.

I can see you're looking at mapping Slack to Intercom. Tell me about your current setup—what's the specific bottleneck you're trying to automate right now?