CRM and automation
Slack CRM notifications that don't turn into noise
How to connect Slack to your CRM so your team only sees what needs action, without drowning in notifications.

Slack CRM notifications always start with enthusiasm and usually end with a channel nobody reads. The cause is almost always the same: everything gets sent, so nothing means anything.
The Slack and PandoraBot CRM connection works like this: every event in the CRM, a new lead, a stage change, a message that is waiting, can send a message to a specific channel through a webhook or n8n/Zapier. The hard part is not the technical connection, which takes an hour. The hard part is deciding what you will not send, so your Slack CRM notifications stay useful.
The test for every notification
One question, and if the answer is no, the notification should not exist:
Does it require a specific person to do a specific thing, today?
A new lead that has to be called within two hours passes. “The customer opened the email” does not pass: it is information, and information belongs in a report, not in a notification.
Which Slack CRM notifications are worth sending
- A new high priority lead, with the criteria defined in advance, not left to the system's judgement
- A request waiting longer than the agreed response time
- A deal that moved backwards in the pipeline, which means something went wrong
- An automation failure, a flow that broke and nobody knows
The last one is the most underrated. Silent automation failures are the most common way to lose leads without understanding why.
Channel structure
Three channels are enough for most teams:
- one for anything that needs immediate action
- one for wins: closed deals, positive reviews
- one for technical errors and flow failures
The second is not a luxury. A team that only ever sees problems gets a distorted picture of its own work.
Name the owner in the notification
A notification without a name is a notification to nobody. “New lead: Sarah P., budget £200k to £250k, assigned to James, reply by 14:00” produces action. “New lead” produces silence.
The two week rule
After two weeks of running, do this exercise: for each type of notification, check how many times it led to real action.
Anything below 20% gets deleted. You will be surprised how much gets deleted, and how much more useful the channel becomes afterwards.
What never to send
Customer personal data beyond the bare minimum. A Slack channel is usually visible to more people than it needs to be, stays in the history indefinitely, and is rarely included in the deletion workflows you have in the CRM.
Name and stage, yes. Financial details, medical information or conversation content, no: the link to the CRM record is enough.
Step by step: making the connection
- Create the three channels in Slack before you touch the CRM, and add to each only the people who will act. An “action” channel with twelve members is already an information channel.
- Create one Incoming Webhook per channel from the Slack settings. You get a URL for each one: keep them somewhere safe, because anyone who has the URL can post to the channel.
- In the CRM, set up the first trigger: a lead with no reply for longer than the response time you have agreed, for example 60 minutes during office hours. Send it to the action channel.
- Write the message with fields, not free text: name, source channel, owner, deadline, link to the record. Nothing else.
- Test with a fake lead and see whether the owner understands what to do without asking. If they ask, the message needs fixing.
- Add the flow failure notification to the technical channel. This is the second one you set up, not the tenth.
Hypothetical example: what changes in a team of three
A hypothetical example: an estate agency with three negotiators receives 60 new enquiries a month from its website, Facebook and WhatsApp. Before the change, everything arrives in one shared channel along with every stage change, every email open and every new comment, around 400 messages a month. Two of the three have muted the channel.
With the rule “only what needs action today”, messages drop to about 80: the 60 leads with an owner's name and a deadline, a dozen or so “waiting longer than the limit” and a few flow failures. The channel becomes visible again. The numbers are invented, but the ratio, five to one, is typical for anyone who sends “everything” at the start.
Common mistakes
- @channel on every notification. After day three, nobody reads it. The @ goes only to the owner, by name.
- A notification without a link. If the owner has to search for the lead in the CRM, the notification cost them time instead of saving it.
- Duplicate notifications from two flows that catch the same event, usually an old one that was forgotten. Every quarter, list all your active flows.
- Notifying in Slack and by email and by push. Pick one. Three channels for the same event is not safety, it is noise times three.
- Leaving the flow running at weekends to people who are not working. If the response time applies during office hours, the notification needs to know that.
What to measure in the first month
Two numbers of your own, not benchmarks: how many notifications were sent per type, and how many led to a recorded action in the CRM within the deadline. The ratio between them is the only thing that matters. If for any type it falls below one in five, that type is the candidate for deletion in the two week exercise.
With PandoraBot
Pandora CRM keeps contacts, conversations and sales in one place, with automation for follow-ups and reminders. See how it works and pricing, or start with a free scan of your website.
First step
Start with a single notification: the lead that has been waiting longer than the response time. If your team starts reacting to it, add a second. If not, the problem was never the notifications.
FAQs
What is the test for a notification?
If it requires a specific person to do a specific thing today, it passes. Otherwise it is information and belongs in a report, not a notification.
How many channels do I need?
Three: actions, wins and technical errors. The second is not a luxury: a team that only sees problems gets a distorted picture.
Is it OK to send customer details to Slack?
Only the minimum: name and stage. A channel's history stays indefinitely and is rarely included in the CRM's deletion workflows, so the link to the record is enough.
Do I need n8n or Zapier for the connection?
Not necessarily. A Slack Incoming Webhook is enough for simple notifications. n8n or Zapier are needed when you want logic in between, for example sending only during office hours or formatting differently per source channel.
What do I do with notifications that do not lead to action?
Do not send them to Slack. Put them in a weekly report from the CRM, where anyone who wants to can see them whenever they like.



