How to connect Pipedrive to Slack for deals that have gone quiet

To connect Pipedrive to Slack usefully, send each deal owner a private, grouped nudge about open deals that have no next activity scheduled, and keep the team channel for wins, large deals and a weekly summary. Pipedrive is organised around activities, so a deal with no next activity is, by the tool's own design, not being worked.

Build the Slack integration around that signal. A feed of stage changes duplicates a board that is already open on someone's screen, while a quiet nudge about silent deals tells people something the board does not.

What we'll cover

• The one signal worth acting on
• Nudging without nagging
• Building it with CodeWords
• What belongs in the team channel
• Context that makes a call better
• What Pipedrive's own automation already does
• The handoff when a deal is won
• Forecast conversations, which the channel should not replace
• Making it survive
• Limits worth knowing about
• What to set up first
• Frequently asked questions

Key takeaways

• The best Pipedrive signal for Slack is an open deal with no next activity scheduled, because it needs no interpretation and is hard to game.
• Send stalled-deal nudges privately to the deal owner, grouped into one message, once, at the start of the day.
• Keep the team channel to wins, large deals moving, losses with reasons and a weekly summary.
• Check Pipedrive's own workflow automations before building, because posting a won deal to Slack may already be possible.
• Report forecast inputs, not a forecast, and never post per-person numbers to a shared channel.

The one signal worth acting on

No next activity scheduled is the signal worth acting on. It is a clean measure of a stalled deal, and Pipedrive computes it natively.

It needs no interpretation. A deal with nothing planned is not waiting on a decision; it is waiting on nobody.

It is hard to game without doing the work. A salesperson can move a stage to look busy, but scheduling a call means having a call.

Combine it with value and stage so the nudge is proportionate. A large deal with nothing scheduled is more urgent than a small one.

Report coverage, not completion. The share of open deals with a next step tells a manager whether the pipeline is being worked, and it is a better measure than the number of activities completed.

Three other signals are related: expected close dates in the past, deals that sit in one stage for an unusually long time, and values that have not changed since creation. All three are quiet, all accumulate, and none produces an event.

Nudging without nagging

Nudge without nagging by following six rules. The tone of these messages decides whether people act on them or filter them out.

Send to the owner, privately. A public list of whose deals are stalling is a different message, and not a better one.

Send once, not daily. People learn to dismiss a recurring reminder about the same deal, and the habit of dismissing then covers the useful reminders too.

Group into one message. People read "Four deals have nothing scheduled" with the list. They skip four separate messages.

Send it at the start of the day, when the owner can act, not at the end when they cannot.

Let them act from the message. Offer to schedule an activity or mark the deal as lost. Lost is often the honest answer, and it is the one that takes longest to admit.

Report the total to the manager weekly, not the individual nudges, so the pattern is visible without singling anyone out daily.

Building it with CodeWords

CodeWords connects to 3,000+ integrations (CodeWords integrations directory, 2026), and you make each connection once and reuse it.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which deals, what condition, and who should be told.
3. Authorize the connection to Pipedrive with an API token for a dedicated integration user, and authorize your Slack workspace.
4. Describe the exceptions: a deal already won or lost, an owner who is away, a deal deliberately parked.
5. Test against one pipeline and a test channel before anything reaches the sales team.

You describe the outcome; Cody builds it, connects it, and deploys it. The Free plan covers light use. Pro costs $39 per month and Business costs $100 per month as usage grows (CodeWords pricing page, 2026); details are on the pricing page.

What belongs in the team channel

The team channel should receive four things, because a channel of deal activity is a worse version of the board.

Deals won. A win is worth announcing. It is good for the team, and it tells the people downstream that work is coming.

Deals above a threshold changing stage. Send these to leadership, not everybody, because large deals warrant attention that routine ones do not.

Deals lost, with the reason. Send these to whoever should learn from the loss, usually product and marketing.

The weekly pipeline summary: total value by stage, what moved, and the coverage number.

Nothing per activity, per email or per field edit. Those are the record of work, not events, and forwarding them buries the four items above.

Context that makes a call better

Context from other systems makes a sales call better, and this is where a Slack integration does something the CRM cannot.

Product usage on a trial. The salesperson sees whether the prospect has used the product before calling to ask how they are finding it.

Open support tickets. Nobody makes an upsell call to an account with an unresolved escalation.

Payment status for an existing customer. This lives in a different system and changes the conversation.

Recent activity from the company, such as a new signup from the same domain. This is a buying signal that no CRM shows.

Deliver it as a lookup that someone triggers, not as a push. The useful moment is just before a call, and the automation cannot know when that is.

What Pipedrive's own automation already does

Pipedrive's own automation already covers some of this, so check it before building. Verify each feature against Pipedrive's current documentation and your plan, because availability depends on the plan.

Workflow automations create activities, move deals and send emails, and can connect to Slack.

Required fields per stage enforce data entry at transitions.

Email sync attaches correspondence to deals for users who enabled it.

Activity reminders notify owners about scheduled activities.

If the requirement is "tell the channel when a deal is won", use Pipedrive's own automation, which whoever manages the sales process can see in the settings. Build a custom automation for the stalled-deal analysis, for anything that joins Pipedrive with product or support data, and for any message that needs to be actionable.

The handoff when a deal is won

When a deal is won, tell the delivery or onboarding team in their own channel, with what was promised. The handoff is the moment where a good sales process most often produces a poor customer experience.

Use the delivery team's channel, not the sales channel, where they are not looking.

Carry what was promised. The commitments made during the deal live in notes and emails, not in fields, and they are the most useful thing to move across.

Record what was actually sold, including any non-standard terms. Delivery and billing disagreements start here.

Name the salesperson, because the handoff will generate questions and knowing who to ask saves a day.

Close the loop back when onboarding completes or stalls, so the salesperson hears it from a colleague and not from the customer.

Forecast conversations, which the channel should not replace

A weekly pipeline summary is not a forecast, and the channel should not replace the forecast conversation. Mixing the two causes trouble.

A summary reports what the CRM says. A forecast is a judgement about what will close. The gap between them is the job of a sales manager.

Report the inputs, not the conclusion. Share value by stage, deals with close dates this period, and the coverage number, then let the conversation happen.

Flag close dates that have passed instead of quietly rolling them forward. That is where optimism accumulates.

Show the change since last week. A stage distribution on its own looks the same every week and tells nobody anything.

Do not post individual forecasts to a shared channel. A public per-person number turns a planning conversation into a performance one.

Keep the summary to five lines. A summary that reads like a report gets skipped. People should be able to glance at it before the meeting, not during it.

Making it survive

Make it idempotent, keyed on the deal and the condition, so the automation does not nudge a deal repeatedly for the same reason.

Resolve stage identifiers per pipeline. They differ, and a hard-coded one works on exactly one pipeline.

Handle the away owner. A nudge to someone on holiday should hold or escalate, not disappear.

Respect deals that are deliberately parked, using a field or label the team agrees. Otherwise the nudge becomes noise for deals that are legitimately waiting.

Report the outcome. Nudges sent, deals covered, and anything skipped.

Limits worth knowing about

Rate limits apply and depend on your Pipedrive plan. Bulk work can use up the token budget quickly. Check the current limits in Pipedrive's API documentation.

Search is not immediately consistent. Use the identifier returned when you created a record instead of searching for it.

Custom field identifiers are opaque strings. That makes them stable and makes queries hard to read.

Pagination applies to listings. A report built from the first page understates everything.

Some features depend on your plan, including parts of the automation and reporting capabilities.

What to set up first

Set up the stalled-deal nudge first: open deals with no next activity scheduled, grouped into one private message to the owner at the start of the day, with the option to schedule something or mark the deal lost from the message. Pipedrive produces this signal natively, and a manager cannot easily assemble it by hand.

Two habits make the difference. Group the deals into one message instead of sending one per deal, because people dismiss four separate notifications as a batch. And include marking the deal lost as an option, because a pipeline full of deals nobody will close is what the nudge is really about.

Frequently asked questions

What number belongs at the top of the weekly summary?

Put the share of open deals with a next activity scheduled at the top. This one figure, compared with last week, tells a manager whether the pipeline is being worked. A stage distribution looks identical every week and never answers that question. Add the change since last week next to the figure.

Should stalled deal alerts go to a channel?

No, send them privately to the owner, grouped into one message, once. A public list of whose deals are stalling is a different message from a quiet nudge, and it produces defensive behaviour instead of scheduled calls. Report the weekly total to the manager so the pattern is visible without singling anyone out.

Should the nudge offer to move the deal?

No, offer to schedule an activity or mark the deal lost, not to change stage. Those two actions resolve a stalled deal honestly. Moving a stage from a chat message only makes the board look tidier, and it hides the fact that nothing is planned. Lost is often the honest answer.

What should the team channel receive?

The team channel should receive wins, large deals moving, losses with reasons, and a weekly summary. Leave out activity, email and field-edit events. Those are the record of work, not news, and they bury the four items that matter. Send large-deal movement to leadership, not to everybody.

Can I see product usage before a sales call?

Yes, as a lookup that someone triggers, not as a push. The useful moment is just before a call, and the automation cannot know when that is. Joining product usage, support tickets and payment status is what Pipedrive alone cannot do, and it stops the salesperson asking a prospect how they find a product they have not used.

Why does the alert cover one pipeline and not another?

Stage identifiers are specific to each pipeline, so a rule written against one pipeline's stages matches nothing in another pipeline. Nothing errors, so the only way to notice is to report how many deals each run examined. Resolve stage identifiers per pipeline instead of hard-coding one.

Should wins be announced to everybody?

Yes, announce the win in the team channel, and send the handoff detail to the onboarding team's channel separately. They are two different messages for two different audiences. Combining them means the delivery team skims past the part it needed, and the sales channel fills with delivery detail.

Should the weekly summary be a forecast?

No, the summary should not be a forecast. Report what the CRM says: value by stage, close dates this period, coverage and the change since last week. Leave the judgement about what will close to the conversation. Mixing the two makes the summary something people argue with instead of read.

What is the most revealing line in a pipeline summary?

Deals whose expected close date has already passed are the most revealing line. Optimism accumulates there, they are easy to miss on a board, and quietly rolling those dates forward is a common way for a forecast to stay wrong. Flag them in the summary instead of rolling them forward.

Related reading

• Pipedrive and CodeWords
• Connecting HubSpot to Slack
• CodeWords integrations and templates