--- title: "Slack + OmniChannels.ai: see failures and replies where your team works" description: "Post OmniChannels.ai delivery failures and inbound SMS or WhatsApp replies to a Slack channel through an automation tool, and trigger sends from Slack." canonical: "https://omnichannels.ai/integrations/slack/" language: "en" updated: "2026-10-10" publisher: "BroadNet Technologies" brand: "OmniChannels.ai" --- # Slack + OmniChannels.ai: see failures and replies where your team works Canonical: https://omnichannels.ai/integrations/slack/ Language: en Publisher: OmniChannels.ai by BroadNet Technologies **In short:** Slack connects to OmniChannels.ai through an automation tool or a small function of yours. Our account webhook sends delivery statuses and inbound messages; the automation filters them and posts failures or customer replies to a Slack channel through Slack's incoming webhooks or its own Slack step. In the other direction, a Slack message or workflow can start an automation that sends through our API. Connect via API & webhooks ## What you can do ### Failed message alerts When a status is FAILED or REJECTED, post the number, channel and reason to an operations channel so someone can follow up. ### Customer replies in a channel Inbound SMS or WhatsApp replies are posted to a shared channel so the team sees them quickly and can pick them up in the inbox. ### Campaign progress notes An automation counts statuses for a batch and posts a short summary to the marketing channel. ### Send from a Slack workflow A Slack workflow or a message in a set channel starts an n8n, Make or Zapier flow that sends an SMS or WhatsApp template through our API. ## How it connects Our platform posts delivery statuses and inbound messages to the one webhook URL configured on your account, and the payload is not in Slack's message format. So something in between receives it and translates it: an automation tool such as n8n, Make or Zapier, or a small function of yours. It filters the events you care about, such as failures and replies, and posts a readable message to Slack through an incoming webhook, a Slack step in the automation tool, or a Workflow Builder workflow that starts from a webhook where your Slack plan supports it. Sending from Slack works the other way round. The automation tool's Slack trigger, or a workflow that calls the tool's webhook, starts a flow that makes an HTTP request to our REST API with your Bearer token. Keep a person in the loop for sends started from chat. - Our webhook is not Slack format; an automation or function translates it - Post with Slack incoming webhooks, an automation tool's Slack step or Workflow Builder - Filter to failures and replies so the channel stays useful - Sends from Slack go through an automation tool to our API ## Set it up 1. **Request API access:** Request test access and receive an API token. Test sends go only to your own verified numbers. (Guide: https://omnichannels.ai/developers/authentication/) 2. **Create the Slack destination:** Create an incoming webhook for the target channel, or connect your Slack workspace in your automation tool. 3. **Receive our events:** Create a webhook trigger in n8n, Make or Zapier and ask our team to set it as your account webhook URL. (Guide: https://omnichannels.ai/developers/zapier-make-webhooks/) 4. **Filter and format:** Keep only the statuses and inbound messages you want, map the fields from a real event, and post a short message to Slack. (Guide: https://omnichannels.ai/developers/webhooks/) 5. **Optionally send from Slack:** Add a flow that a Slack message or workflow starts and that sends through our API, with a confirmation step. (Guide: https://omnichannels.ai/developers/sms/) ## Example workflow OmniChannels.ai webhook (Delivery statuses and inbound messages) → n8n, Make or Zapier (Filters events and formats a Slack message) → Slack channel (Failures and customer replies posted for the team) ## Questions ### Is there an official OmniChannels.ai app for Slack? No. Events reach Slack through an automation tool or your own function, using Slack's incoming webhooks, Workflow Builder or the automation tool's Slack step. ### Can I point your webhook straight at a Slack incoming webhook? No. Our payload is not in Slack's format and there is one webhook URL per account. An automation tool or function needs to receive it, filter it and post a formatted message. ### Should every delivery status go to Slack? Usually not. Statuses repeat and arrive out of order; post failures, rejections and replies, and keep the full record in your own system. ### Can the team reply to customers from Slack? Only if you build that flow, and replies must follow channel rules such as WhatsApp's 24-hour service window. For two-way conversations the OmniChannels.ai inbox is the better fit. ## Developer guides - https://omnichannels.ai/developers/webhooks/ - https://omnichannels.ai/developers/zapier-make-webhooks/ - https://omnichannels.ai/developers/sms/ ## Vendor documentation - [Sending messages using incoming webhooks — Slack API](https://api.slack.com/messaging/webhooks) ## Related integrations - https://omnichannels.ai/integrations/n8n/ - https://omnichannels.ai/integrations/zapier/ - https://omnichannels.ai/integrations/make/ - https://omnichannels.ai/integrations/zendesk/ Slack is a trademark of its owner. OmniChannels.ai is not affiliated with or endorsed by Slack; this page describes a connection built with Slack's own MCP, HTTP or webhook features. Updated: 2026-10-10