Integration
Slack and Naffes CRM: your pipeline, posted to a channel
Whenever a deal moves to another stage in Naffes CRM, a message lands in the Slack channel you choose, naming the deal, the stage it left, the stage it entered and the amount.
One job: announce pipeline movement
The Slack integration is deliberately narrow. It does not copy contacts or conversations into Slack. It gives the team a running feed of deals moving through the pipeline, whether a rep changes the stage on the deal page or drags the card on the Kanban board.
Each post follows a fixed format:
- the deal name in bold;
- the previous stage, an arrow, and the new stage in bold;
- the amount with two decimals and a thousands separator but no currency symbol, when the deal has one.
A post reads like Fleet tracking rollout moved Demo → Proposal · 125,000.00, with the deal and new stage in bold. One channel serves several readers: the sales manager spots deals entering negotiation, delivery prepares handovers as deals near closing, and leadership senses weekly momentum without opening a report. Because every post goes to a single channel, pick one all of them follow.
From Slack app to first message
Create a Slack app with a bot token
In Slack's app dashboard, create an app, give the bot the chat:write scope, install it to your Slack workspace, and copy the bot token (it starts with xoxb-) and the signing secret.
Invite the bot to the channel
Add the app to the channel you want. Slack refuses posts from a bot that is not a member of the channel.
Open Slack in the Marketplace
As a workspace admin, open Marketplace, choose Slack and click Configure Slack to reach its credentials screen.
Enter the details and save
Paste the bot token and signing secret, and enter the default channel: its name if public, its ID if private. Click Save.
Test, then go live
Click Test connection to validate the token, then Send test message to see a real post in the channel. From then on, every stage change is announced. The Slack alerts help article repeats these steps with fixes for common errors.
The Marketplace is available from the Starter plan. Saved secrets are never sent back to the browser; the screen shows only that a value is set and when.
Data and direction
| Item | Direction | When |
|---|---|---|
| Deal name, both stages, amount | Naffes to Slack | On every deal stage change |
| Test message | Naffes to Slack | When you click Send test message |
| Anything from Slack | Nothing | The integration is one-way |
Nothing about contacts, conversations or tasks is sent. For other events, use signed outgoing webhooks or connect Make for wider scenarios.
Limits
- One channel. All posts go to the default channel; you cannot route a pipeline to its own channel.
- One event. Stage changes only. No post when a deal is created or a contact is added.
- One-way. No slash commands, no @mention routing, no replies back into Naffes.
- No retries. If Slack is unreachable at the moment of the move, that post is not sent later.
- The workflow Slack step is not usable from the builder today. It needs an incoming-webhook URL the builder has no field for. The practical workaround is an HTTP request step in automation that posts text you write to another channel's incoming-webhook URL.
Questions
Questions 4
Can one team's deals go to a separate channel?
Not through the Slack connector, which posts to one default channel. You can add a workflow on the deal stage changed trigger with an HTTP request step to another channel's incoming-webhook URL.
Test connection passed but the test message failed. Why?
The first check only validates the token. The message usually fails because the bot was not added to the channel, or because a private channel was entered by name instead of ID.
Is the amount shown with a currency?
No. It is a number with two decimals. Each workspace runs in a single currency, so the team reads it in that currency.
Does this use Slack OAuth sign-in?
No. You paste the bot token and signing secret on the settings screen, and only workspace admins can change or remove them.