How to Use Pipedrive to Stop Deals From Going Cold

The short answer: name each stage after the action that moves a deal into it, set a probability and a rotting limit per stage, import your open deals from a spreadsheet, connect email sync on Growth, add an automation that schedules a follow-up activity whenever a deal enters a key stage, and once a week ask an assistant connected through Pipedrive's MCP server which open deals have not moved, then approve the next steps it proposes.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

The job: a proposal goes out, nobody touches the deal for three weeks, and the buyer signs elsewhere. Pipedrive's answer is mechanical and visible: deals that sit too long in a stage rot, and every deal should carry a next activity. For plans and prices, see the Pipedrive glossary entry.

Before you start:

• Price the automation. Lite has rotting but not automations. For example, a team of three on Growth costs 3 x $39 = $117 a month billed annually, against 3 x $14 = $42 on Lite, using the pricing page checked on 24 October 2026, so automatic follow-ups cost $75 a month for that team.
• Reuse your sheet. Each column becomes a field and each row one record, per the import guide; include emails or phone numbers to cut duplicates.
• Fix the Monday reading. The number of rotting deals, and the number of open deals with no activity scheduled.

What you need

• Deal admin permissions to create and edit pipelines, per the pipeline guide.
• Growth or higher for email sync and automations, per the email sync guide and the automations guide. The 14-day trial covers the build.
• Permission to add automations. Only global admins or users given that permission can create them.

Step 1: Name the stages after actions

Open the pipeline dropdown and choose New pipeline, or edit the default one. The pipeline guide recommends stage names tied to a real action, such as Meeting scheduled or Proposal sent, fewer stages rather than more, and separate pipelines only where teams sell differently. It also warns against moving deals between pipelines, which affects reporting in Insights.

Step 2: Set probability and rotting per stage

In the same editor, set a stage probability if you have historical win rates, or enable deal probability to set it per deal; when both are on, the deal's own probability wins. Then enable rotting and set the number of days after which a deal in each stage starts to rot. A shorter limit belongs on Proposal sent than on Discovery. Save changes.

Step 3: Import the open deals

Go to the account menu, Tools and apps, Import data, Import from spreadsheet, and click Get started. The import guide accepts one tab per file with a header row, up to 200,000 rows and 50 MB. Create custom fields before the import if your columns do not match the defaults. Imports do not set off event-triggered automations, except for leads, per the automations guide, so imported deals will not get the step 5 activity until they change stage.

Step 4: Connect email

Open the account menu, Personal preferences, Email sync, enter the address, choose the provider, sign in and grant access, per the email sync guide. Choose a personal account (Growth) or a team account (Premium), set visibility to private or shared, choose how much past email to sync, then Start sync. Automations can only send from an address synced this way.

Step 5: Schedule the next step automatically

Go to Tools and apps, Automations, click + Automation and choose an Event trigger: Deal, updated. Add the condition that the stage is Proposal sent, then an action that creates an activity, Call about proposal, assigned to the deal owner, with a relative due date such as In one day or next Tuesday, per the automations guide. Without a due date, the activity lands on the same day. Save and set the automation to Active.

Step 6: Ask the pipeline what has stalled

Connect ChatGPT or Claude through the Pipedrive MCP server, which uses an OAuth login and your own permissions. On Monday, ask the prompt Pipedrive itself publishes: show me all open deals over $10K that have not been updated in two weeks. Then ask for one proposed next activity per deal. The human check: read the proposals and approve only the ones you would have scheduled yourself; each action the assistant takes is recorded in Pipedrive's change log, so the week's changes can be reviewed afterwards.

Step 7: Read the two numbers

In pipeline view, count the rotting deals and the open deals without a scheduled activity. If rotting climbs, look first at one stage: the limit may be too short, or that is where deals die.

What Pipedrive's guides warn about

• Deleting a stage. It deletes the deals in it; move them first. Deleted deals can be restored within 30 days.
• Open deal limits. An automation that creates deals fails at that step once you reach your plan's open deal limit, and does not resume later.
• One check per condition. Unless you use a wait-for condition, an automation checks each condition once and stops if it is not met.
• Whose email sends. An automation's emails always come from the user who created it.

Pipedrive includes the MCP server on every plan within token limits and sells extra tokens, so an assistant that rereads the whole pipeline every hour spends your allowance. Once a week is enough for this job.

FAQ

How many days should a stage take to rot?

The pipeline guide leaves the number to you per stage. Start near the time a healthy deal spends there, and shorten it where silence usually means a lost deal.

Do rotting alerts need a paid upgrade?

No. Deal rotting is listed on Lite and every plan above it, per the plan features article; automations are what need Growth.

Can the automation send the follow-up email instead of creating a task?

Yes. An action can send an email from the address synced to Pipedrive, per the automations guide, and it will always come from the automation's creator.