A CRM workflow trigger is the event that starts an automated rule: a lead is created, a stage changes, a field is edited, a date arrives, or a message is logged. The workflow then checks conditions and runs actions such as assignment, a task, a field update, or a notification.
The general shape of workflow automation—states, handoffs, and human waits—is explained in what is workflow automation. This page stays on CRM triggers: what fires them, how they run twice by accident, and how to contain a failure.
Events, conditions, and actions
Event. The moment the CRM evaluates the rule. “Record created” and “stage changed to Quotation sent” are events. “Every night” is a scheduled event. “Someone might call tomorrow” is not an event.
Condition. A filter on that event. Stage equals Quotation sent, and amount is at least a given figure, and owner is not empty. Conditions stop a rule written for large deals from firing on every spare-part quote.
Action. The work: create a task, notify a manager, set a follow-up date, or call another system. Actions should be reversible or at least visible. A rule that emails a customer with no record on the opportunity is hard to explain later.
Keep one business outcome per workflow. A single rule that assigns the lead, sends three emails, and updates finance is difficult to test.
Delays and recurring runs
A delay waits after the event: “two days after quotation sent, if stage is unchanged, create a follow-up task.” The condition must be checked again when the delay ends, not only when the wait started. Otherwise you remind someone about a deal that was already won.
Recurring triggers, such as a daily job for stale leads, need a marker so the same lead does not get a new task every night. A “reminder already open” flag or a last-run timestamp is enough.
Duplicate execution
Duplicates happen when:
- The event fires on every edit, not only when the stage value changes
- An integration updates the record and the user’s edit both qualify
- A delayed job and a scheduled job both create the same task
- The action itself updates a field that retriggers the workflow
Guard with “run only when the stage value changes” and “stop if this task type is already open.” Log the run. Audit trails should show the workflow identity, not a mystery edit.
One CRM trigger, checked twice
- Stage changes to the triggering value
- Conditions pass at that moment
- A delay starts
- When the delay ends, conditions are checked again
- Action runs only if it has not already run
Failure handling
Decide what “failed” means. A notification that nobody receives is a failure. An update rejected by accounting is a failure. The CRM should keep the error on the record or in a queue a human reviews. Do not silently retry forever. Do not roll the stage backwards unless that is an explicit compensation step someone has tested.
Test with a non-production user and a sample opportunity. Include the case where conditions fail, not only the happy path.
A practical example
When an opportunity enters “Quotation sent,” the CRM creates a task due in three business days for the owner, but only if no open “quotation follow-up” task exists. If the stage has already moved on when the delay ends, no task is created. A separate rule notifies the manager only when the amount exceeds an agreed figure. WhatsApp enquiries can create the lead that starts this path; the inbox product is a channel, not the workflow engine.
Key takeaways
- A trigger is an event plus conditions plus a small set of actions.
- Re-check conditions after a delay.
- Block duplicate tasks when the same event repeats.
- Surface failures for a person to resolve.
FAQ
Should every stage change send an email to the customer?
No. Customer messages need a template, a reason, and a record of what was sent. Internal tasks are the safer default.
Can a trigger replace pipeline discipline?
No. Automation can create the follow-up. It cannot invent a stage meaning. Define stages first in sales pipeline stages.
Who may edit live workflows?
The same small admin group that can change permissions. A salesperson experimenting on production can email the whole customer list.