Can the thresholds differ per stage?

Yes. A single node holds a table of stage name and idle days. The shipped default is seven days for every stage; edit the rows you want to change and leave the rest.

What if an owner is not on Slack?

Their deals still get the follow-up activity in Pipedrive. The DM step skips any owner without a Slack ID in the mapping, and the execution log lists who was skipped so you can fill the gap.

Will it run on Make or Zapier?

Make can do it: a scheduled scenario with the Pipedrive module, an array aggregator for the grouping and the Slack module. Zapier can schedule the run but has no clean way to fold one owner's deals into a single message, so the package ships for n8n only.

Does it need a paid n8n plan?

Not beyond the entry plan. One run per weekday and a handful of API calls sit well inside n8n Cloud's Starter plan, and a self-hosted instance runs it at no licence cost.

PSMade to order

Sales & CRM hygiene

Pipedrive stale deals → Slack nudge to the owner + follow-up activity

Idle deals get a follow-up activity and a Slack nudge every weekday morning.

Deals go quiet because nobody watches all of them at once. Every weekday at 08:00 this workflow reads every open deal in Pipedrive and flags any with no activity in seven days and nothing scheduled. Each owner gets one Slack DM listing their idle deals, and each deal gets a follow-up activity due that day. No deal is nudged more than once a week, so the message stays short enough to read.

How it works

P
Trigger
Weekday 08:00 scan of all open deals (Schedule Trigger polling the Pipedrive deals API)
Pipedrive
P
Step 1
Pull every open deal with owner, stage and activity dates
The deals endpoint, filtered to open status and paged to the end, returns each deal's title, value, stage, owner, last activity date, next activity date and the date it last changed stage.
if
Step 2
Flag deals idle for seven days with nothing scheduled
A deal is flagged when its last activity is older than the threshold for its stage and no next activity exists; thresholds live in one node so each stage can have its own.
if
Step 3
Skip anything nudged in the last seven days
The custom deal field Last nudged holds the date of the previous nudge, and any deal stamped inside the window is dropped from this run.
S
Step 4
DM each owner a list of their idle deals
Deals are grouped by owner and sorted by value, then one direct message per owner lists title, value, stage, days idle and a link back to the deal in Pipedrive.
P
Step 5
Create a follow-up activity on every flagged deal
Each flagged deal gets a call or task activity, assigned to the owner and due the same day, so the nudge also appears in the owner's Pipedrive activity list.
P
Step 6
Stamp the deal with today's date in Last nudged
Once the DM and the activity succeed, the custom field is updated, which is what keeps the next six runs from nudging the same deal again.

What changes once it runs

Every open deal is checked every weekday morning, not just the ones a manager remembers.
Owners see one message with their idle deals ranked by value and a link to each.
Each flagged deal carries a follow-up activity due that day, so the nudge shows up in Pipedrive too.
No deal is nudged more than once in seven days.
Idle thresholds can differ by stage: three days in Negotiation, fourteen in Qualified.

What you get

The n8n workflow export with the schedule, filters and per-owner grouping already wired
Setup guide covering the API token, the custom field and the owner-to-Slack mapping
Thresholds sheet listing each stage and its idle limit, ready to edit
Recorded walkthrough of a morning run against a test pipeline

Before you start

Pipedrive on any plan; the API token is available in every user's personal preferences
Permission to add one custom deal field in Pipedrive: Last nudged, date type
Slack with an app installed that can send direct messages to members
A short mapping of Pipedrive owner emails to Slack member IDs, filled in once during setup
An n8n instance, cloud or self-hosted; no public URL is needed because nothing calls in

Built for

Questions before you buy

Can the thresholds differ per stage?: Yes. A single node holds a table of stage name and idle days. The shipped default is seven days for every stage; edit the rows you want to change and leave the rest.
What if an owner is not on Slack?: Their deals still get the follow-up activity in Pipedrive. The DM step skips any owner without a Slack ID in the mapping, and the execution log lists who was skipped so you can fill the gap.
Will it run on Make or Zapier?: Make can do it: a scheduled scenario with the Pipedrive module, an array aggregator for the grouping and the Slack module. Zapier can schedule the run but has no clean way to fold one owner's deals into a single message, so the package ships for n8n only.
Does it need a paid n8n plan?: Not beyond the entry plan. One run per weekday and a handful of API calls sit well inside n8n Cloud's Starter plan, and a self-hosted instance runs it at no licence cost.

Nearby on the shelf

Whole catalog