Sequence Builder
A canvas where every step is a box and every edge is the answer to a question. Thirteen kinds to place, and what you leave behind is the thing the engine walks rather than a picture of it.
One catalogue, thirteen kinds, and the ports each hands back
2 outgoingProduct figures from the platform’s own defaults - not customer averages
How it works.
Thirteen kinds, sorted into six shelves
Email, timing, branches, actions, multichannel and end. The entry box is placed for you and cannot be added again; the other twelve you drag on or click in. Builder and engine read the same catalogue file, so neither can hold an opinion the other does not.
Ports are how a fork gets wired
A plain box has one outgoing port. A behaviour question has two, named for the answer. A split has one per arm, and the disposition box one per category you type in plus a catch-all. Dropping a second edge on a port that already has one replaces it, so a port only ever leads somewhere.
It writes itself down while you work
A second after you stop dragging, the whole graph goes back as JSON with each box position tucked in beside that step's settings. Reopen it anywhere and the layout survived. Open one that was written straight to the database and it gets laid out top to bottom for you.
Publishing takes a copy; the draft moves on
Publish compiles first and rejects two shapes: a graph with no valid entry box, and a box whose own edge points straight back at itself unless that box is a pause. Nothing looks for a longer ring. What passes is frozen as a numbered version, and anybody already mid-cadence stays on the number they began under.
Two moments in every run.
Every run passes through the same seven. Sequence Builder is the lit ones, 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- Kinds available
- Send email, pause, opened, clicked, replied, call outcome, split, call task, text, goal, tag, end, and the entry box
- Palette shelves
- Six. Email, timing, branches, actions, multichannel and end
- Edges per port
- One. Wiring a new edge from a port drops whatever was there before
- Rejected at publish
- No valid entry box, and any box wired directly back into itself unless that box is a pause. A longer ring is not looked for
- Versioning
- Publish freezes a numbered copy. Editing the draft afterwards does not disturb anybody already running
- Set on the box itself
- Split weights, the pipeline-stage filter on the goal box, and the person a call step is assigned to, each on the inspector for that kind of box
- Not the same as
- This is the drawing surface. The machinery that walks what you drew is Email Sequences
- Who may change one
- Manage-settings on the workspace, or any tenant administrator. Reading one needs only a seat
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
12 capabilitiesSequences, dispositions and webhooks that act without being asked.
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.
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.
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.
New leads enrol themselves the moment they are created, and the four guards that can refuse an add are read on every single route into a cadence.
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.
Six event types a CRM rule fires from: stage change, field update, new record, reassignment, schedule and inactivity, agreed in four places at once.
Send the email, assign the owner, raise the task, set the field, move the stage or call a webhook. Six modules, run in the order you stored them.
Eight comparison operators guarding each action, combined with AND and only AND, so a rule meaning either of two things is built twice, as two rules.
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 sequence builder on your own floor.
Thirty minutes, your numbers and your data. We will set sequence builder up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included