Slack + SalesCrew
Plainly: there is no Slack app, no slash commands and no in-Slack CRM. What works is an outbound webhook from your instance to a Slack incoming webhook URL.
- Via webhooks only
- No Slack app
- You control the channel and format
The short answer
- SalesCrew has no customer-facing Slack integration. There is no app in the Slack directory, no slash commands, no interactive buttons and no way to approve a queued action from Slack.
- What does work: 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.
- 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 honest answer is short.
| What | Mechanism | Direction | Objects | Status |
|---|---|---|---|---|
| Slack app in the directory | Does not exist | , | , | Not available |
| Notifications into a channel | Outbound webhook to a Slack incoming webhook URL | Outbound | Any registered event | Available |
| Formatted or interactive messages | Through Zapier, Make or n8n between the two | Outbound | Any registered event | Available |
| Slash commands | Not built | , | , | Not available |
| Approving a queued action from Slack | Not built. Approvals live in the SalesCrew queue | , | , | Not available |
| Reading Slack messages into the CRM | Not built | , | , | Not available |
Mechanisms read from the SalesCrew integration table, September 2026. Slack's own documentation is the authority on incoming webhook payload format.
Setup
Five minutes, and it is worth doing even though it is not an app.
- 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
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
Test before you announce it
webhook_test fires a sample so you can see the raw shape land in the channel.
- 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
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
Rotate the secret when people leave
webhook_rotate_secret changes the signing key, and webhook_delete removes a channel nobody reads.
Where Slack is actually used
Questions
- Can I approve an AI draft from Slack?
- No. Approvals happen in the SalesCrew queue, where the artefact, the evidence, the confidence and the cost are all visible and the decision is written to the audit log. A Slack ping can tell you one is waiting.
- Is a Slack app on the roadmap?
- It is not on the published roadmap. The webhook path is the supported answer today.
- 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 answer and same mechanism. Any endpoint that accepts an HTTP POST can receive an outbound webhook.
- Why not only build the app?
- It is a real piece of work and it is not what launch is about. Rather than list Slack as an integration and let you discover the gap, the page says what exists.
Get the alert without pretending it is an app
One outbound webhook, one Slack channel, and an honest label on what it is.