Alert Slack on overdue Pipedrive deals using Workflow Automation

Prerequisites

Why Workflow Automation?

Workflow Automation is the simplest approach because everything stays inside Pipedrive — no external tools, no API keys, no hosting. A date-triggered automation fires when a deal's expected close date passes without the deal being won, and the native Dealbot integration sends a Slack notification automatically. There's zero ongoing cost beyond your existing Pipedrive license.

The trade-off is detection accuracy. Pipedrive's date-triggered automations only check the expected close date field — they cannot detect true inactivity (days since last call, email, or meeting). A deal could have daily activity but an outdated close date and still trigger the alert. Conversely, a deal with zero activity for months won't trigger anything if its close date hasn't passed yet. If you need activity-based staleness detection, use n8n instead.

How it works

• Deal rotting periods (configured per stage) give reps a visual indicator in the pipeline view when deals go stale — but rotting alone does not trigger automations or send notifications
• Date-triggered automation fires X days after the expected close date passes on open deals
• Condition filters for deals that are still open (skips already-won or already-lost deals)
• Slack notification action sends a Dealbot message to your channel with the deal name, value, owner, and how overdue it is

Overview

You'll set up two things: deal rotting periods for visual pipeline hygiene, and a date-triggered Workflow Automation that sends Slack alerts when deals pass their expected close date. The rotting periods help reps spot stale deals in the pipeline view. The automation adds proactive alerts so overdue deals don't get ignored.

Step 1: Configure deal rotting periods per stage

This step is optional but recommended. Rotting periods add a red visual indicator to deals that have been idle in a stage too long, giving reps an at-a-glance view of pipeline health.

1. Navigate to Settings > Company settings > Pipelines
2. Select the pipeline you want to configure
3. Click the pencil icon next to each stage name to edit it
4. Set the rotting period in days (e.g., 14 days for Discovery, 30 days for Proposal, 45 days for Negotiation)
5. Click Save

Repeat for each stage. Shorter periods for early stages (where deals should move quickly) and longer periods for later stages (where procurement cycles slow things down) is a common pattern.

Step 2: Install Dealbot for Slack

If you've already installed Dealbot for another automation, skip to Step 3.

1. Navigate to Settings > Tools and apps > Marketplace apps and search for Slack
2. Click Dealbot for Slack in the results
3. Click Install and authorize access to your Slack workspace
4. Select which Slack channels Dealbot can post to (you can adjust this later)
5. Complete the OAuth flow to connect both accounts

Once installed, the Slack notification action becomes available in all Workflow Automations.

Step 3: Create a date-triggered Workflow Automation

Navigate to Automations > Create (or Automations > + Automation depending on your UI version).

Configure the trigger:

• Trigger type: Date-based
• Entity: Deal
• Date field: Expected close date
• Timing: After date
• Offset: Choose how many days after the close date to fire (e.g., 7 days for a one-week grace period)

This trigger evaluates daily and fires for any deal whose expected close date is exactly 7 days in the past (or whatever offset you set). Pipedrive checks this once per day, so alerts arrive on a daily cadence rather than in real time.

Step 4: Add a condition for open deals

Add a Condition after the trigger to skip deals that have already been won or lost:

• Field: Status
• Operator: Equals
• Value: Open

Without this condition, the automation would also fire for deals that were lost months ago but still have a past close date — generating noise in your Slack channel.

Step 5: Add a Slack notification action

Add an Action after the condition:

1. Select Send Slack channel message (or Send Slack notification depending on your UI)
2. Choose the target Slack channel from the dropdown (e.g., #pipeline-hygiene or #sales-alerts)
3. Configure the message content using merge fields:

Example message template:

Overdue Deal Alert
Deal: [Deal Name]
Value: [Deal Value]
Owner: [Deal Owner]
Expected close: [Expected Close Date]
Pipeline: [Pipeline]
Stage: [Stage]
 
This deal is past its expected close date. Update the close date, add next steps, or close it out.

Insert merge fields using Pipedrive's field picker — click the field insertion button (the + icon) in the message editor and select the appropriate fields. Don't type field names manually.

Step 6: Activate the automation

1. Click Save and name your automation descriptively (e.g., "Slack Alert — Deal overdue by 7 days")
2. Toggle the automation to Active
3. To test, set a deal's expected close date to 7 days ago (matching your offset), ensure its status is "open," and wait for the next daily evaluation cycle

To cover multiple urgency levels, create additional automations with different offsets — for example:

• 7 days overdue: Gentle nudge to #sales-alerts
• 30 days overdue: Escalation to #pipeline-hygiene with manager tagged
• 60 days overdue: Final warning before pipeline review

Common questions

Can I trigger an automation based on deal rotting status instead of close date?

No. Pipedrive's deal rotting is a visual indicator only — it shows a red highlight on deals in the pipeline board view, but rotting status is not available as an automation trigger or condition. The only date-based automation trigger for deals is the expected close date field (or custom date fields). If you need activity-based staleness detection, use the n8n approach which queries last_activity_date via the Pipedrive API.

Can I set different overdue thresholds per pipeline stage?

Not with a single automation. Each Workflow Automation has one fixed date offset. To alert at different thresholds, create separate automations — for example, one that fires 7 days after close date for deals in Discovery, and another that fires 30 days after for deals in Negotiation. Add a condition on each automation to check the Stage field. For dynamic per-stage thresholds in a single workflow, use n8n.

Will this catch deals that have been sitting idle with no activity?

Only if their expected close date has also passed. A deal could have zero activity for 90 days, but if the expected close date is set to next month, this automation won't fire. That's the core limitation of the date-triggered approach — it measures overdue-ness by close date, not by activity recency. For true activity-based staleness detection, the n8n approach queries each deal's last_activity_date field from the API.

Cost

$0 additional — Workflow Automations and Dealbot for Slack are included on Growth ($24/seat/mo), Advanced ($44/seat/mo), Professional ($64/seat/mo), Power ($79/seat/mo), and Enterprise ($99/seat/mo) plans. No external tools or API keys required.