Choose a Workflow Trigger: Events You Would Bet On
How to choose a workflow trigger: pick an event that definitely happened, not a guess about intent, because every later step is only as good as the start.
To choose a workflow trigger, pick an event that definitely happened, such as a form being submitted or a deal changing stage, and avoid triggers that guess at intent from weak signals. A trigger you would bet on is the foundation of everything after it.
The trigger is what starts a workflow for a particular person. It is the first line of the sentence you write before you build: when this happens, do that. Because everything downstream depends on it, it is the single place where care pays back the most. A rule that fires for the wrong people is wrong at every step, and wrong at scale.
How to choose a workflow trigger: the test
The test is a bet. Would you stake something on the claim that this event really happened, and that it means what you think it means? If the answer is an easy yes, you have a good trigger. If you find yourself explaining why the signal probably indicates interest, you have a guess.
The best triggers are unambiguous changes of state. Something was recorded that was not recorded before. It is a fact about the world, not an interpretation of it.
| Kind of trigger | What it rests on | How reliable it is |
|---|---|---|
| A form was submitted | A person took a deliberate action | High, if the form still does what it did |
| A tag was applied | A record was changed on purpose | High, but only as reliable as whatever applies the tag |
| A deal moved to a new stage | A recorded state change | High, but it includes moves you may not want |
| A score crossed a threshold | A rule you wrote earlier | As reliable as the scoring behind it |
| A set number of days passed since something happened | A date and a fact | High, as long as the starting event is real |
| A guess that someone seems interested | An inference from weak signals | Low |
The first five are all facts that were recorded. The last is a story. Choose from the first group whenever you can.
Why weak signals are dangerous
A trigger that infers interest from a weak signal feels clever, because it promises to catch people early. The cost appears later. If the signal fires for people who were never interested, every message and task after it lands on the wrong person, and it does so automatically and repeatedly.
That is why the guide advises being wary of triggers that infer interest. A workflow is only as reliable as the event that starts it. The inconvenience of a trigger that misses a few people is small. The incident caused by a trigger that catches the wrong ones is not.
Match the trigger to the sentence
Go back to the plain-language version of your workflow. The first clause is your trigger. Read it aloud and ask whether it describes an event or a hope.
| The clause | Event or hope? |
|---|---|
| "When someone submits the enquiry form" | Event |
| "When a deal moves to the proposal stage" | Event |
| "When someone seems ready to buy" | Hope |
| "When a score crosses the line we agreed" | Event, provided the score is trusted |
| "When someone has been quiet for a while" | Hope, unless the wait is a defined number of days since a recorded event |
If a clause is a hope, rewrite it until it is an event. Often the fix is to move the hope into a condition and keep the event as the trigger. The deal moving stage is the trigger. Whether the contact is already a customer is the check that follows. How to write that check is the subject of how to set workflow entry criteria.
Ask what else the event includes
Even a clean trigger catches more than you meant. The guide uses a deal changing stage as the example: it includes deals moving backwards, deals moving into stages that do not need this workflow, and deals belonging to customers already handled elsewhere. The event is real, but it is broader than the intention.
Before you settle on a trigger, list what else could cause it to fire. Ask three questions.
- Could the same event happen for someone I do not want in this workflow?
- Could it happen twice for the same person?
- Could it happen as a side effect of something else I do, such as tidying records?
The second question leads straight to re-entry, which is covered in how to test a workflow before switching it on, because a test is where duplicate enrolment tends to show.
Prefer the earliest real event
Interest is perishable, and the moment someone raises a hand is the moment they are most willing to hear from you. For that reason, the best trigger is often the first event that proves the hand was raised, such as the form being submitted. A trigger that waits for a later signal adds hours of silence in exchange for a confidence you may not need.
The exception is when the later event is itself the thing you care about. A deal reaching the proposal stage is a real handoff in its own right, and it deserves its own workflow with its own trigger.
What can quietly break a trigger
Triggers do not stay fixed because you wrote them down. The event they rely on can change underneath them.
- A form was rebuilt. The workflow depends on the old form, and it stops firing after the new one replaces it. No error appears. The numbers simply fall to nothing.
- A stage was renamed. The trigger still points to something, but not the thing it meant.
- A field went stale. A trigger that reads a field fires on old data or on none.
- People started arriving by a route you did not anticipate. The trigger fires for a group you never planned for.
These are the ways the workflow in your head and the one that runs drift apart. The defence is to check, after any change to forms, fields, stages or pipelines, that the trigger still means what it meant when you built it. The loop that does this is described in how to spot a silently failing workflow.
Rewriting a weak trigger
Most weak triggers can be repaired by finding the recorded fact that sits behind the hope. The table shows the move, using only the kinds of event already named above.
| The weak version | The problem | A stronger version |
|---|---|---|
| Someone seems interested | It infers intent from signals that may mean nothing | The person submitted a form |
| The deal looks ready | It rests on a feeling | The deal moved to a named stage |
| The lead has gone cold | It has no definition | A set number of days passed since the last recorded event |
| The lead is hot | It has no agreed meaning | The score crossed the threshold you set |
The pattern is always the same. Replace the feeling with something that was written down at a definite moment. If nothing was written down, you do not yet have a trigger, and a task for a person to judge the case is the more honest tool.
A short procedure
- Write the workflow as two or three plain sentences.
- Underline the first clause: that is the trigger.
- Rewrite it until it names an event that was recorded.
- List everything else that could cause the same event.
- Decide what to do about each extra case, using entry criteria.
- Write down what the trigger means, so a later change can be checked against it.
Write down what the trigger means
A trigger is a promise that an event means something. Six months from now, you will not remember exactly what you meant by it, and neither will anyone who takes the workflow over. Keep the plain sentence beside the workflow, and add a note on what the starting event is and why you trust it.
This small habit pays off at review time. When the numbers surprise you, the first thing to check is whether the trigger still means what it meant when you built it. A written meaning turns that from a guessing game into a comparison.
Timing as a trigger
Some triggers are about time rather than action: a set number of days passed since something happened. They are useful because they let you follow up on silence without relying on anyone to notice it. They are only as good as the event they count from, so make sure the starting event is real.
When time is involved, think about when messages land as well as when the rule fires. A message that arrives in the middle of the night or on a public holiday announces that nobody was there to send it. Where you can, make waits respect working hours, and ask what should happen if the situation has changed during the wait.
Frequently asked questions
Can I trigger on a score?
Yes, a score crossing a threshold is a reasonable trigger, provided you trust the score. A rule built on a doubtful score inherits every doubt.
Is one trigger per workflow enough?
Usually, yes. A workflow with one clear starting event is easier to read, review and trust. If a process truly has several phases, build several small workflows that hand off to each other.
What if my best signal is a weak one?
Do not trigger on it directly. Use it to prompt a task for a person, who can judge whether it means anything.
How often should I recheck a trigger?
Whenever forms, fields, stages or pipelines change, and in your regular review. If a workflow's numbers drop to zero, assume the trigger is broken until you have proved otherwise.
The full method, with the checklists, is in The Automation Playbook, a free 29-page playbook.