How to Automate Deal Follow-Ups with Pipedrive Workflows

Most deals are lost to silence, not to competitors. A four-touch follow-up sequence recovers a meaningful share of them, and it takes about forty minutes to build in Pipedrive.

Direct answer: to automate deal follow-ups in Pipedrive, open Automation → Workflows, set the trigger to “Deal stage changes” for a specific stage, then add an “Email” action followed by a “Wait” action and a second email. Workflow automations require the Professional plan at $49 per user per month, billed annually.

What plan do you need?

Workflow automations are not on the Essential plan. This is the most common gotcha — teams build a flow in a trial, then discover it disappears when the trial ends.

Plan	Price/user/month (annual)	Automations
Essential	$14	no workflows
Advanced	$34	no workflows
Professional	$49	yes, plus sequences
Power	$64	yes, plus phone support
Enterprise	$99	yes, plus SSO

Sequences are a separate feature from Workflows, and they behave differently. Sequences require manual enrolment per person; Workflows fire automatically on a trigger. For deal follow-ups you want Workflows.

How should the trigger be defined?

“Deal stage changes” with a to stage, not from. Deals skip stages and get edited backwards; triggering on the target stage is the only reliable anchor.

Add a condition on deal value or owner if the sequence is not universal. A $50 deal and a $50,000 deal should not get the same six-touch cadence.

One critical filter: add “Only run once per deal”. Without it, a deal moved out of the stage and back gets the whole sequence again, and the prospect sees the same four emails twice. This looks like a bug to the customer and is easy to miss in testing because you rarely move deals backwards during a demo.

How do you write the follow-up emails?

Short. Three to five sentences, one question, no attachments. Sequences that perform have a plain subject line and a specific ask.

A working four-touch cadence:

• Day 0 — recap the call and confirm the next step date.
• Day 3 — one useful thing: a doc, a case study, a benchmark relevant to their stated problem.
• Day 7 — a direct question: “Is this still a priority for Q1?”
• Day 14 — a graceful close: “I will stop following up; here is my calendar if it comes back.”

That fourth email gets more replies than the other three combined. It works because it removes pressure, and most sellers never send it.

Use the {{deal_title}} and {{person_name}} placeholders rather than writing generic text. Merge fields default to blank when missing, so test with a deal that has all fields populated.

How do wait steps interact with weekend scheduling?

“Wait 3 days” means 72 hours, not three business days. A deal that enters the stage on Friday night sends touch two on Monday night, which lands in a crowded inbox.

Set the wait to 3 days and add a condition, or use the “Send at” option to pin delivery to a weekday morning. Sending Tuesday through Thursday between 9 and 11 AM local time consistently outperforms Friday afternoons.

Also be careful with long waits. A 14-day wait survives a stage change unless you explicitly cancel the flow. If the deal advances, the email becomes irrelevant and embarrassing.

Cancel conditions save you from that: add “Deal stage changes away from X → end workflow” checkpoints between each wait.

What should you measure?

Three numbers, checked monthly:

• Reply rate per touch. Touch 1 should be 15-25%; anything under 8% means the subject line is wrong.
• Stage conversion change. Compare the 30 days before and after enabling the workflow with similar deal volume.
• Opt-outs. Above 2% means you are mailing too often.

Pipedrive’s email tracking shows opens, but open rates are unreliable since Apple’s Mail Privacy Protection pre-fetches images. Weight replies, not opens.

Where this gets painful

Email deliverability depends on your sending domain, not Pipedrive. If you send from a Gmail address with no SPF or DKIM record, most of these emails hit spam and the workflow looks like it does nothing. Set up your domain in the email settings before trusting any results.

Workflow limits also matter: Pipedrive caps active workflows per account by plan tier, and complex conditions with many branches get hard to audit after six months. Name every workflow with the segment it targets and the date it was built.

And none of this fixes a pipeline problem. Automating follow-up on bad-fit leads just annoys more people, faster.

Key Takeaways

• Workflows need the Professional plan at $49/user/month, billed annually; Sequences are a different feature.
• Trigger on “Deal stage changes to X” and always enable “Only run once per deal”.
• A four-touch cadence ending with a graceful close outperforms endless follow-up.
• “Wait 3 days” is 72 hours, not three business days — pin delivery to weekday mornings.
• Add cancel checkpoints between waits, or a deal that advances still receives stale emails.