5 Pipedrive Automations Every Sales Manager Sets Up First

Reps forget to create follow-up tasks. Deals sit in “Proposal Sent” for three weeks with no activity. You spend your mornings asking “what’s happening with the Acme deal?” instead of actually coaching your team.

Pipedrive has automation built in. But most managers either don’t know it exists or set up the wrong things first. Here are the five automations that actually matter—in the order you should build them.

1. Auto-Create Follow-Up Activities When Deals Move Stages

The problem it solves: Reps move a deal to “Demo Scheduled” and then… nothing. No task to prepare the demo. No reminder to send the agenda. The deal just sits there until someone remembers.

How to set it up:

1. Go to Automations in the left sidebar
2. Click Create automation → Start from scratch
3. Trigger: Deal - Stage changed
4. Condition: Deal moved to [specific stage]
5. Action: Create activity
6. Fill in: Activity type, subject, due date (e.g., “2 days from now”), assigned to deal owner

The automations worth creating per stage:

• Qualified → Demo Scheduled: Create task “Send demo agenda and confirm time” (due: 1 day)
• Demo Scheduled → Proposal Sent: Create task “Follow up on proposal” (due: 3 days)
• Proposal Sent → Negotiation: Create task “Prepare negotiation talking points” (due: 1 day)
• Negotiation → Contract Sent: Create task “Follow up on contract” (due: 2 days)

Why this matters: Pipedrive’s own data shows that companies using automations are 16% more likely to hit targets. Most of that comes from not letting deals go cold between stages. Your reps don’t need to remember what happens next—the system tells them.

Pro tip: Don’t automate every stage transition on day one. Start with the two stages where deals stall most. For most teams, that’s post-demo and post-proposal. Add more once those are running smoothly.

2. Stale Deal Alerts

The problem it solves: You’ve got 47 open deals. Eight of them haven’t been touched in two weeks. You don’t know which eight until you manually scan the pipeline—which you’ll do once, then forget about until month-end panic.

How to set it up:

Pipedrive has a built-in “rotting” feature, but the automation approach gives you more control:

1. Trigger: Deal - Updated (check on a schedule)
2. Condition: Days since last activity > [your threshold]
3. Action: Send email to the deal owner (or you)

Alternatively, use Pipedrive’s deal rotting settings:

1. Go to Pipeline → click the pencil icon next to stage name
2. Set “Days to rot” for each stage
3. Rotting deals show a visual indicator in the pipeline view

Recommended rot periods by stage:

Why this matters: Deals don’t usually die with a dramatic “no.” They die quietly—an email that doesn’t get a reply, a call that never gets scheduled, a follow-up that falls through the cracks. Rotting alerts catch these before they’re unrecoverable.

The key is setting honest thresholds. If your typical sales cycle is 30 days, a deal with no activity for 7 days in the “Demo Scheduled” stage is a red flag. Adjust based on your actual data, not optimism.

3. Lead Assignment and Round-Robin Distribution

The problem it solves: New leads come in and sit unassigned. Or one rep grabs everything. Or leads go to whoever happened to check Pipedrive last.

How to set it up:

1. Trigger: Deal - Added
2. Condition: (optional) Filter by lead source, deal value, or label
3. Action: Change owner → select team member

For round-robin, you’ll need to get a bit creative since Pipedrive’s native automation doesn’t have a built-in round-robin. Two options:

Option A: Use Pipedrive’s LeadBooster add-on if you have it. It includes automatic lead assignment with distribution rules.

Option B: Manual rotation with labels. Create a label system (Rep A, Rep B, Rep C) and use automations to assign activities based on the label. Rotate labels weekly or by lead source.

Option C: Use Pipedrive’s “Teams” feature (available on Professional and Enterprise plans). Create team-based assignments and Pipedrive handles distribution.

Why this matters: Speed-to-lead is one of the few sales metrics with rock-solid data behind it. Responding to a lead within 5 minutes makes you 21x more likely to qualify them compared to waiting 30 minutes. Unassigned leads don’t get responded to in 5 minutes. They don’t get responded to at all until someone notices.

Pro tip: Don’t just assign the deal—assign the first activity too. “Call new lead” due in 1 hour. That creates urgency. An assigned deal with no next step is barely better than an unassigned one.

4. Real-Time Team Notifications via Google Chat

The problem it solves: Your team is spread across the pipeline. Rep A closes a deal—nobody knows until the next standup. Rep B’s prospect just moved to a new stage—the account manager who needs to prepare onboarding has no idea.

The problem with Pipedrive’s built-in notifications: They’re email-based or in-app. Email notifications get buried. In-app notifications require your team to be inside Pipedrive—and let’s be honest, they’re not checking Pipedrive every 10 minutes.

How to set it up:

This is where Pipedrive’s native automation has a gap. You can trigger internal emails, but you can’t natively push to Google Chat.

Your options:

1. Zapier/Make: Set up individual Zaps per event type. Works, but gets expensive and has delays (covered in detail in our comparison guide).
2. PipeToChat: Purpose-built for this. Connect Pipedrive and Google Chat in 5 minutes, choose your events, and your team gets rich notification cards in 2-5 seconds.

What good team notifications look like:

Instead of a plain-text email saying “Deal updated,” your team should see:

• What changed: “Deal ‘Acme Corp’ moved from Proposal → Negotiation”
• Who changed it: “Updated by Sarah K.”
• Key context: Deal value, expected close date
• A link: Click straight to the deal in Pipedrive

Why this matters: This isn’t about micromanagement. It’s about situational awareness.

When your team sees deals moving in real-time:

• Reps celebrate wins together. Sounds soft, but culture drives retention.
• Managers spot coaching moments. A deal that skipped the demo stage? Worth a conversation.
• Adjacent teams can act. Customer success sees a closed-won deal and starts prepping onboarding before anyone sends a Slack message asking them to.

According to Pipedrive, companies using AI and automation in their CRM see 44% faster deal progression and 25% fewer stalled deals. A lot of that comes from faster information flow—which starts with notifications that actually reach people.

5. Won Deal Workflows (The Post-Close Handoff)

The problem it solves: A deal is marked “Won.” Confetti emoji in the team chat. Then… what? Someone needs to send the contract. Someone needs to set up onboarding. Someone needs to update the finance tracker. But there’s no automatic trigger for any of it.

How to set it up:

1. Trigger: Deal - Stage changed → moved to “Won”
2. Actions (chain multiple):
3. Create activity: “Send welcome email to customer” (assigned to account manager, due today)
4. Create activity: “Schedule onboarding call” (assigned to CS team, due in 2 days)
5. Create activity: “Send invoice” (assigned to finance contact, due in 1 day)
6. Send email: Notification to the customer success team with deal details

Advanced version:

If you’re on Pipedrive’s Professional plan or higher, you can also:

• Automatically move the deal to a “Post-Sale” pipeline for onboarding tracking
• Update custom fields with the close date for reporting
• Trigger a webhook to update external systems (billing, project management, etc.)

Why this matters: The handoff from sales to post-sales is where a shocking amount of customer experience breaks down. Your rep promises the moon during the sales process, closes the deal, moves on to the next prospect—and the customer sits in limbo wondering what happens next.

Automating this handoff means the customer experience starts the moment the deal is won, not whenever someone remembers to do something about it.

Pro tip: Create a “Lost Deal” automation too. When a deal moves to “Lost,” automatically create a task to send a brief “what went wrong” survey 2 days later. That feedback is gold for improving your process—and sometimes, the follow-up re-opens the conversation.

What Order to Build These In

Don’t try to set up all five in one afternoon. Automation fatigue is real—you’ll build too many, forget what they do, and end up with reps getting contradictory notifications.

Week 1: Follow-up activities (#1) and stale deal alerts (#2). These fix the biggest productivity leaks immediately.

Week 2: Lead assignment (#3). Once reps are reliably working their existing deals, make sure new ones land in the right hands fast.

Week 3: Team notifications (#4). Now that deals are moving consistently, give the broader team visibility.

Week 4: Won deal workflows (#5). With everything else running, close the loop on the post-sale handoff.

Each automation should run for a few days before you add the next. Watch for unintended side effects—duplicate tasks, notification overload, activities assigned to the wrong people. Fix those before layering on more complexity.

The Automation Trap to Avoid

One thing I see constantly: managers automate everything and then wonder why their reps feel micromanaged.

Not every action needs an automation. If a rep is senior enough to manage their own follow-up cadence, don’t force a rigid task creation sequence on them. Use automations as a safety net for the team, not a straitjacket for individuals.

The best automation setup is one your team doesn’t think about. Deals get assigned. Tasks appear when they should. Stale deals get flagged. Wins get celebrated. Nobody has to remember to do the busywork—so they can focus on actually selling.

Want to set up automation #4 (team notifications) in 5 minutes? Start a free PipeToChat trial and connect your Pipedrive pipeline to Google Chat today.

FAQ

Can I set up Pipedrive automations on any plan?

Pipedrive automations are available on the Advanced plan ($34/user/month) and above. The Essential plan doesn’t include workflow automation. If you’re on Essential, you can still use deal rotting and some basic features, but custom automation triggers require an upgrade.

How many automations should a typical sales team have?

Start with 5-10 core automations. More than 20 active automations usually means you’re over-engineering your process. If you can’t explain what each automation does without looking it up, you have too many.

Do automations work retroactively on existing deals?

No. Pipedrive automations only fire on new events after the automation is created. Existing deals won’t be affected. If you need to update existing deals in bulk, use Pipedrive’s bulk edit feature or import/export.

Can I notify my team in Google Chat when automations trigger?

Not natively through Pipedrive. Pipedrive’s automation actions include internal emails and activity creation, but not Google Chat messages. You’ll need a tool like PipeToChat or Zapier to bridge Pipedrive events to Google Chat.

What’s the difference between Pipedrive automations and workflows?

They’re the same thing. Pipedrive renamed “Workflows” to “Automations” in their interface. You might see both terms in older documentation, but they refer to the same feature.