It runs on every edit
How you'll know: Follow-up calls stack up on deals that never changed stage.
Fix: An updated trigger fires on any change. Add a condition on the stage value so only the move you care about qualifies.
A deal reaches Proposal sent and somebody still has to remember the follow-up call. Pipedrive's Automations take that off their plate: pick a trigger, narrow it with conditions, then choose what happens. You get it on Growth and higher plans, and only global admins or users with the right permission can build one. It gets harder when the next step depends on a record that lives outside Pipedrive.
Build one: open the account menu at the top right, go to Tools and apps, then Automations, and click + Automation.
Account menu › Tools and apps › Automations › + AutomationEvent trigger: fires when a deal, person, organization, activity, lead or project is added, updated or deleted. Date trigger: fires on, before or after a date field on a deal, person, activity or organization.
Plans: Growth, Premium and Ultimate. Lite doesn't include automations.
Example: when a deal moves to Proposal sent, create a follow-up call for the deal owner and post a note in the team's Slack channel.
Choose Event trigger, set the item to deal and the event to updated, then click Apply trigger. Prefer a date-based follow-up? A date trigger on the expected close date works the same way.
Watch for: "updated" fires on any change to the deal, a renamed contact or an edited value included. The condition in the next step is what makes it specific.
Add a condition on the stage being Proposal sent, and on the pipeline if you run more than one. Pipedrive suggests common conditions, or you can add your own on any deal field, custom fields included.
Create an activity for the deal owner, due a few days out. Then add a Slack action for the channel note. Actions cover deals, persons, organizations, leads, activities, email, notes, campaigns, projects and webhooks, plus Slack, Microsoft Teams, Trello and Asana.
Watch for: each automation holds up to ten actions. Past that, split the work into a second automation with its own trigger.
An if/else step splits the flow, for example a call for large deals and an email for small ones. A wait for condition step pauses until something becomes true, and a delay step pauses for a set time.
Watch for: a wait for condition step gives up after seven days and the automation stops there. Delays add up to 90 days at most per automation.
Name it after what it does, so the list still makes sense when there are thirty. Only active automations count toward your plan's cap, so switch off old ones you might want again instead of deleting them.
Both are fine while the logic is short. When one decision depends on several outside lookups, needs retries, or writes back to more than one system, a small service on the Pipedrive API is easier to test and to reason about.
How you'll know: Follow-up calls stack up on deals that never changed stage.
Fix: An updated trigger fires on any change. Add a condition on the stage value so only the move you care about qualifies.
How you'll know: The first actions ran, the later ones never did.
Fix: Look for a wait for condition step. If the condition isn't met within seven days, the automation ends there. Use a delay, or a second automation with its own trigger, for longer gaps.
How you'll know: You built it, but it can't be activated.
Fix: You've reached your plan's cap on active automations: 50 on Growth, 150 on Premium, 250 on Ultimate. Switch off the ones nobody relies on.
How you'll know: After an import or a mass stage move, only part of the records got the action.
Fix: Pipedrive caps executions at 10,000 per company and 5,000 per automation in any ten minutes, and runs past that are stopped or ignored. Big moves go in smaller batches.
How you'll know: A stage move should have sent a hundred emails and they're still going out.
Fix: Email actions are limited to 40 a minute per company account, and Gmail or Outlook can add their own limits on top.
An automation's conditions can only read what Pipedrive holds. The webhook action is how a step reaches outside: it sends the deal, person or activity to a URL you choose. What sits at that URL decides whether anything useful happens, and Pipedrive leaves that end to you.
n-frames builds that receiving end. A deal is marked won, the webhook calls a small service, and the service looks the customer up in QuickBooks. If the account is in good standing it creates the invoice and writes the invoice number back to a deal field. If there's an overdue balance it moves the deal to a hold stage and posts the reason for the rep. The same pattern covers assigning a lead from an ERP territory field, or holding a renewal task until usage data says it's due. Scoring leads before they're assigned is covered on Pipedrive lead scoring, and the wider picture of what links to Pipedrive is on the Pipedrive page.
Pipedrive's Workflow Automation, found under Automations, runs inside Pipedrive on its own records, with built-in actions for a few apps and a webhook action. Zapier sits outside and links Pipedrive to a much longer list of apps, billed separately. For a check across several systems before deciding, n-frames builds a service on the Pipedrive API instead.
An automation can send a templated email from the connected mailbox when a deal or activity event happens, up to 40 email actions a minute per company. For newsletters and segmented campaigns, Pipedrive's Campaigns add-on or a tool such as Mailchimp is the better fit.
Not for triggers, conditions and actions inside Pipedrive. The builder is point and click. Code comes in when a webhook needs something on the other end to receive it, check another system and reply, and that's the part n-frames writes.
Yes. Growth allows 50 active automations per company, Premium 150 and Ultimate 250, and switched-off ones don't count. Each automation can hold ten actions, and if/else steps are capped at 3, 10 and 20 per automation on those plans.