Pipedrive automation lets the CRM create activities, assign owners, flag stalled deals and send data to other tools on its own. We build Pipedrive Automations, assignment rules and rotting settings within your plan's limits, then add Zapier, Make or n8n through webhooks when Pipedrive cannot do a step alone.
We check your plan's automation limits first, so nothing stops working later.
The short answer
Pipedrive automation is Pipedrive's built-in Automations feature plus a few related tools. An automation starts with a trigger, such as a deal being added or a date arriving, then runs up to ten actions: create an activity, update a field, send an email, post to Slack, or send a webhook.
Pipedrive's help centre lists six trigger objects: deals, people, organisations, activities, leads and projects. Each can fire when a record is added, updated or deleted. Date triggers fire before, on or after a date field. If/else and "wait for condition" steps let one automation split into paths. (Source: Pipedrive Knowledge Base, "Workflow automation", updated 3 Sep 2026, checked 7 Nov 2026.)
Three other features sit next to Automations and matter just as much for sales teams:
What we automate
For a sales-led team, six jobs give most of the value. They follow the life of a deal, from the first enquiry to the hand-over after it is won.
Leads from forms, chat, ads and outbound tools land in the Leads Inbox with source, label and region set, and a person or organisation that already exists is linked, not duplicated.
Assignment rules hand leads to a person or rotate them across a team, using fields like country, deal value or product. A last rule catches anything the others miss.
Lead routing with Zapier →When a deal enters Demo Booked, Proposal Sent or Negotiation, the right call, email or task is added with a due date, so the next step is never left to memory.
Rotting days set per stage to match your real sales cycle, plus an automation that warns the owner and, later, the manager, when a deal goes quiet.
Closed-won deals create a project or onboarding activity, notify delivery in Slack or Teams, and send the customer record to billing through a webhook.
Enrichment, AI scoring, spreadsheets and multi-app steps run outside Pipedrive and write their result back to a deal or person field.
Our Zapier consultant service →Sample automations
These five automations solve the problems sales managers raise most: slow first touch, uneven lead sharing, missing next steps, silent deals, and messy hand-overs after a win. Each fits inside Pipedrive's ten-action limit, and only the last one needs an outside tool.
| Automation | Pipedrive feature | Trigger | Actions |
|---|---|---|---|
| Same-day first call | Automations | Lead added | Create a call activity due today for the owner; Slack message to the team channel |
| Fair lead sharing | Automatic assignment | Lead or deal added | Owner set by region, then round robin within that region's team |
| Next step on every stage | Automations with if/else | Deal stage updated | Different activity per stage; if deal value is above your threshold, also add the manager as a follower |
| Quiet deal warning | Rotting + Automations | Date trigger on a "next follow-up" field | Email the owner; wait for condition; if still untouched, alert the manager |
| Won deal to billing | Automation webhook action | Deal status set to won | Webhook sends the deal to n8n, Make or Zapier, which creates the customer in your billing tool and posts the invoice link back to a deal note |
Before you start
You need Growth or higher. Lite has no Automations. Growth allows 50 active automations with three if/else steps each. Premium raises this to 150, adds automatic assignment for round robin, and includes LeadBooster. Ultimate allows 250. Webhooks through the API work on every plan.
| Feature | Lite | Growth | Premium | Ultimate |
|---|---|---|---|---|
| Automations | No | Yes | Yes | Yes |
| Active automations per company | None | 50 | 150 | 250 |
| If/else steps per automation | None | 3 | 10 | 20 |
| Actions per automation | None | Up to 10, plus up to 10 delays and 10 "wait for condition" steps | ||
| Webhook action inside automations | No | Yes | Yes | Yes |
| Automatic assignment (incl. team round robin) | No | No | Yes | Yes |
| LeadBooster (forms, chatbot, live chat) | No | No | Included | Included |
| Regular webhooks and API | All plans | |||
Sources, checked 7 Nov 2026: Pipedrive Knowledge Base, "How many workflows can I have" and "Automation limits" (updated 12 Oct 2026); "Automations: webhook requests" and "Automatic assignment" (updated 3 Sep 2026); Pipedrive's 2025 plan changes article. We do not quote Pipedrive prices here; see pipedrive.com/pricing.
Two limits catch teams during bulk work. A company can run up to 10,000 automation executions in ten minutes, and one automation up to 5,000. Email actions are capped at 40 a minute across the account. A large import or bulk edit can hit these quickly, so we pause the relevant automations before any big data job.
Deal rotting
Set rotting days per stage to about one and a half times the normal time a healthy deal spends there, not one number for the whole pipeline. Then pair rotting with an automation, because a red card only helps if someone opens the pipeline view and looks at it.
Pipedrive starts the rotting clock from a deal's last update. Marking an activity done, adding a note or file, or emails linked to the deal reset it. One detail surprises people: a scheduled activity in the future does not stop a deal from rotting. A deal with a call booked three weeks away will still turn red. (Pipedrive Knowledge Base, "The Rotting feature", updated 3 Sep 2026.)
We use that on purpose. A long gap before the next touch is often the real problem, and a red card makes it visible. This is how we size rotting days for a typical B2B pipeline:
Stage Healthy time Rotting after Qualified 3 days 5 days Demo booked 7 days 10 days Proposal sent 10 days 14 days Negotiation 14 days 21 days
Use your own numbers. Our pipeline calculator helps you work out stage conversion and cycle length first.
What we usually find
Pipedrive is easy to start with, so automations are often added fast by whoever needs one. After a year, the account hits its active automation limit, reps get duplicate activities, and a Zapier task does the same job as a native rule. These six problems are the ones we fix most.
Speed of first contact matters most of all. Our guide to lead response time explains why.
Tell us your Pipedrive plan and pipeline stages. We will review your automations, assignment rules and rotting settings and send a short fix list.
Book a Pipedrive automation review →Our view
Build it natively when the job only touches Pipedrive: activities, owners, fields, emails and Slack alerts. Use Zapier for quick links to common apps, Make for multi-step flows with branching, and n8n for AI steps or high volume. Mixing them is fine, as long as each job lives in one place.
| Job | Where we build it | Why |
|---|---|---|
| Activities, owner changes, field updates | Pipedrive Automations | Native, visible to the admin, no per-task cost |
| Round robin by team | Pipedrive automatic assignment (Premium+) | Rotation and history are built in |
| New form lead to Pipedrive, plus a sheet and an email | Zapier | Fast to build; Pipedrive app is ready-made |
| Enrich a person, then branch by company size | Make | Visual branching and data shaping |
| AI reads the enquiry and scores it | n8n or Zapier, score written to a custom field | Model, prompt and checks managed outside the CRM |
n8n offers a ready Pipedrive node and a Pipedrive Trigger node (n8n docs, checked 7 Nov 2026). For a fuller comparison, read our n8n vs Zapier vs Make guide or our n8n consultant service.
How a project runs
We run five steps: list what is live in Pipedrive and in any outside tool, agree the sales rules with your sales lead, build in small batches, test with sample leads and deals, then hand over notes and review real data after 30 days. A focused project usually takes two to three weeks.
Our naming pattern keeps the automation list readable:
[Object] › [Result] › [Trigger] › [Owner] Lead › Call today › Added › Sales Deal › Proposal follow-up › Stage = Proposal sent › Sales Deal › Manager alert › Follow-up date passed › Sales lead Deal › Send to billing › Won › Finance
Proof from our own work
Our published case study scores each enquiry with fixed rules plus an AI read of the message, then routes it HOT, WARM or COLD. It runs in Zapier, which connects to Pipedrive, so the score can land in a custom field that your automations and assignment rules act on.
Read the AI lead qualification case study, including the mapping bug we found and fixed in testing. It was tested on sample enquiries, not live lead volume.
Is this right for you?
Comparing CRMs first? See our best CRM for startups comparison, which covers Pipedrive, HubSpot and Zoho. Moving off HubSpot? Our HubSpot alternatives guide covers seat costs and migration. Need a person running this every week? Hire a marketing automation specialist.
Common questions
Tell us your Pipedrive plan and where deals slow down. We will review your setup and suggest the first three automations to build or fix.
We reply within one business day.