Pipeline Rot Alert
Every pipeline contains deals that are technically open and actually dead, and they inflate the forecast that decisions get made from. This workflow sweeps the pipeline weekly, finds deals with no activity for longer than the stage should take, and pushes each one to a decision: advance it, set a date, or lose it. Deals are not allowed to simply sit.
What you get
Workflow blueprint
The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.
Getting it into Zapier
Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 7 steps, so it is a copy-and-paste job rather than a design job.
You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →
Not on Zapier?
An n8n workflow JSON ships with this template. Import it and all 7 steps arrive on the canvas wired in order, and 4 of the 7 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Every step maps to a native n8n node.
What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.
A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.
Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →
Setup steps
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Implementation notes
- Set the rot threshold per stage, not per pipeline. A week of silence after a proposal means something quite different from a week of silence at first contact.
- Marking deals lost is the point of the workflow. A forecast built on deals nobody will admit are dead is worse than no forecast, because it gets used.
- The value floor keeps the list short enough to be read. A rot list of forty deals is ignored; a list of five gets worked.
- HubSpot, Salesforce, Close and Copper all substitute for Pipedrive. Slack, Discord and Google Chat all substitute for Teams.