Pipedrive Automations Not Triggering
Quick answer
Automations fail to fire most often because of condition logic, a missing trigger field, or an inactive owner. Use the automation History log to see what happened.
Most likely fix: Read the History log
How to fix it
Try these in order — the most common fix is first.
1. Read the History log
- Open the automation and view its history
- Identify if it did not trigger, was delayed, or errored
Did this fix it?2. Fix trigger fields and logic
- If the condition is Deal Stage has changed to X, select Deal Stage in the trigger step Fields
- Switch AND to OR where appropriate
- Save and test again
Did this fix it?3. Check ownership
- A global admin can transfer ownership of the automation to another user who can then reactivate it
Did this fix it?4. Reinstall integrations
- For failing integration steps reinstall the app from the Marketplace
Did this fix it?5. Check status page
- Look at status.pipedrive.com for delays
Did this fix it?
Symptoms
Automation never runs, runs late, or runs with an error.
Why it happens
- 'has changed to' condition without the matching trigger field selected
- AND logic where OR is needed
- Field already had the value, so no change occurred
- Automation owner deactivated
- Integration step (e.g. Slack) uninstalled
- Pipedrive incident causing delays
This guide also covers
- pipedrive automation not working
- pipedrive workflow automation not triggering
- pipedrive automations unreliable
Still not working?
If Pipedrive keeps failing, you're not alone. See every Pipedrive problem users report or the alternatives people switch to.
Done fighting Pipedrive? Our small team builds your own Pipedrive alternative, made for how you work. On your domain or hosted by us. Price agreed together.
Get a quote