Workflow Triggers
Six events a CRM rule starts from, agreed in four separate places so nothing else can ever be stored. The event carries a coarse filter, and the fine one belongs to each action underneath it.
Six events a rule starts from, and what raises each one
raised at the save- entity typedeal
- fieldstage_id
- valueProposal Sent
- 1find the live rules for this event
- 2apply the coarse filter
- 3open a run row
- 4execute each action in order
- 5close the run with a verdict and any errors
Product figures from the platform’s own defaults - not customer averages
How it works.
Six names, agreed in four separate places
Deal stage change, field update, record created, assignment change, time based, inactivity. The identical six appear in the code constant, in the database type, in the model, and in the validation on both writing endpoints, so nothing else can ever be stored.
The event carries its own coarse filter
Beside the name sits a small object: a record kind to narrow to, and optionally one field with one required value. An empty object matches everything. This is the wide sieve; the fine one belongs to each action.
One class carries a fire from end to end
It finds the live rules for the event, applies the sieve, opens a run row, executes each action in the order stored, then closes the run with a verdict, a finish time and any collected errors. A rule that matched and did nothing is therefore distinguishable from one that never matched.
Four are raised where the change is written; two are swept for
Stage changes, field updates, creations and reassignments are raised by the code doing the writing. Time based and inactivity have no such moment, so a repeating job looks for dates that have arrived and records nobody has touched, and raises them from there.
One moment in every run.
Every run passes through the same seven. Workflow Triggers is the lit one, and everything either side of it is a different page in this category.
- 01Trigger
the thing that happened first
- 02Enrol
how somebody gets onto it
- 03Wait
the pause, and what governs its length
- 04Branch
the fork, and which side is taken
- 05Act
the mail, the text, the task that goes out
- 06Measure
what counts as it having worked
- 07Exit
how somebody comes off it
The specifics.
8 facts- Event names
- Deal stage change, field update, record created, assignment change, time based, inactivity
- Filter stored beside it
- A record kind, plus optionally one field and one value it must have changed to. Empty matches all
- Where each is raised
- Four from the code that writes the change. The other two from a repeating sweep
- The sweep
- Looks for dates that have come round and records untouched past their window, then raises the two events that need it
- Storage
- Three tables. The rule, its ordered actions, and a run log carrying status, error and timing
- The screen
- A list with create, edit, delete and an active toggle, so a rule can be stood down without being taken apart
- Permission
- A manage-workflows flag on the profile, gating the menu entry and the endpoints behind it
- Not the same as
- This fires on what changed to a record. Carrying somebody through steps over days is Email Sequences
What starts this, and what it starts.
Automation is only ever a middle. These are the things that set it running and the things that run because of it.
More in Automation & Flows
13 capabilitiesSequences, dispositions and webhooks that act without being asked.
Thirteen node kinds on a canvas: send, wait, branch on behaviour, split, call task, tag, goal. Publish a version and in-flight leads keep their own place.
A unique URL per integration with HMAC signing, rate limits, payload caps and idempotency - plus a log of every delivery it ever accepted or refused.
Enrol a lead once and the sequence carries them: sends, waits, branches and exits, with a ledger that makes a duplicate send structurally impossible.
Branch on whether they opened, clicked or replied, and on how the last call was dispositioned - so the next step answers what actually happened.
Weighted splits assigned by a deterministic hash of the enrolment, so a lead always takes the same arm no matter how often that step is run again.
Hold a lead for minutes or days between steps, clamped to the sending window you set, so that an overnight wait never lands at four in the morning.
Set the hours a sequence may send inside, as a fixed offset you enter yourself, and every wait is pushed forward into them before it is stored.
One do-not-contact roll per workspace, checked when a lead is enrolled and again inside the send, straight after that send has taken its own claim.
Drop a call step into a sequence and it raises an assigned task on the lead's owner, with the outcome the rep logs coming back as a branchable answer.
Name a linked deal as the outcome that means the sequence worked. Reaching it stamps goal met on the run and takes the branch you wired behind it.
Twenty-six behaviours attach to wrap-up codes, and twenty codes ship already pointing at one, so ending a call the right way books the follow-up.
A text is a step on the same canvas as the email and the call task, written into the real thread and carried out by the number it is going out from.
A versioned path, a key minted once and kept as a hash, and the same role and profile model the interface runs on deciding what that key may touch.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Automation & Flows
See workflow triggers on your own floor.
Thirty minutes, your numbers and your data. We will set workflow triggers up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included