Slack + SalesCrew

SalesCrew reaches Slack via webhooks. An outbound webhook from your instance posts to a Slack incoming webhook URL, in the channel you choose.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

Want to see it first? Book a demo

  • Via webhooks
  • Deliveries logged and retried
  • You control the channel and format
app.salescrew.io/settings
Settings: MCP tokens, integrations and the audit log

The short answer

  • The connection runs via webhooks. Register an outbound webhook on your instance pointed at a Slack incoming webhook URL, so events reach a channel.
  • Deliveries are logged and failures retry. The signing secret rotates whenever you need it to, and a channel nobody reads is one delete away.
  • If you want more than a message, put an automation tool in the middle. Zapier, Make or n8n can catch the SalesCrew webhook and post a formatted Slack message with whatever structure you like.

Mechanism

A short table, because the setup is short.

WhatMechanismDirectionObjectsStatus
Notifications into a channelOutbound webhook to a Slack incoming webhook URLOutboundAny registered eventAvailable
Formatted or interactive messagesThrough Zapier, Make or n8n between the twoOutboundAny registered eventAvailable
Delivery log and retrieswebhook_deliveries and webhook_retryOutboundWebhook deliveriesAvailable
ApprovalsDecided in the SalesCrew queue, with a Slack ping when one waitsInternalApproval items, audit logAvailable

Mechanisms read from the SalesCrew integration table, September 2026. Slack's own documentation is the authority on incoming webhook payload format.

Setup

Five minutes from a blank channel to live alerts.

  1. 1

    Create a Slack incoming webhook

    In your Slack workspace, add an incoming webhook for the channel you want and copy the URL it gives you.

  2. 2

    Register it in SalesCrew

    webhook_create with that URL and the events worth interrupting people for. Choose few: a channel that pings on everything gets muted within a week.

  3. 3

    Test before you announce it

    webhook_test fires a sample so you can see the raw shape land in the channel.

  4. 4

    Format it if the raw JSON is ugly

    Put Zapier, Make or n8n in the middle and build the Slack message you actually want.

  5. 5

    Keep approvals where they belong

    The approval queue stays in SalesCrew. A Slack message can tell you something is waiting; the decision and its audit line happen in the app.

  6. 6

    Rotate the secret when people leave

    webhook_rotate_secret changes the signing key, and webhook_delete removes a channel nobody reads.

Why approvals stay in the queue

The approval queue shows the artefact, the evidence, the confidence and the cost side by side. The decision is written to the audit log with the person named. A Slack ping tells you an item is waiting, and the queue is where it gets decided.

Questions

Where do I approve an AI draft?
In the SalesCrew approval queue, where the artefact, the evidence, the confidence and the cost are all visible. A Slack ping can tell you one is waiting.
Can I get deal alerts in a channel?
Yes, through the webhook. Register the events, point them at the Slack URL and keep the list short enough that people still read it.
What about Microsoft Teams?
Same mechanism. Any endpoint that accepts an HTTP POST can receive an outbound webhook.
What does SalesCrew cost?
Tiers are $299, $699 and $1,200 a month, with unlimited seats on every tier. Webhooks are included from Core.

Get the alert in the channel your team reads

One outbound webhook, one Slack channel, and a delivery log behind every message.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

Want to see it first? Book a demo