Workflows
A workflow has three parts:
- When: the trigger that starts a run.
- Then: an ordered list of steps, which can branch. Who the workflow is for is a condition step at the top, typically Only continue if… is in segment X.
- Measure: a goal event and window, and an optional holdout.
How often one contact may enter is a setting on the workflow: once (the default, later triggers are ignored), again after their previous run has ended, or any time, with several runs at once.
Triggers
| Trigger | Starts a run when |
|---|---|
| A contact performs an event | An event with that name is tracked. Email and webhook steps can read the event's properties. |
| A contact property changes | The property changes, to anything, to a given value, from unset to set, or from set to unset. Fires on identify calls, edits on the contact page, and workflow steps that set properties. |
| Another workflow hands the contact over | Nothing on its own. Only an Enter another workflow step in another workflow puts contacts in, the building block for sub-workflows. |
Steps
Wait
Pause for an amount of minutes, hours or days before the next step. Durable, survives deploys and restarts.
Wait for an event
Pause until the contact performs an event, or a timeout passes; on the timeout either continue or stop the run.
Wait until a time
Pause until the next given time of day (optionally only on certain weekdays) in a time zone.
Only continue if…
Check the contact against segment-style conditions now. If they don't match, the run exits here. As the first step it is the workflow's audience ("is in segment Trial accounts"); later on, the usual pattern is "has not reached activation". Conditions are the same as in segments, plus In segment to reuse a saved one.
If … else
Check the contact against conditions and walk the Yes lane if they match, the No lane otherwise. Either way the run continues with the step after the branch. Lanes hold steps of their own, including further branches.
Switch
Reads one value, a contact field such as plan, or a property of the trigger event, and runs the lane for that value; if no case matches, Otherwise runs. Enum properties offer their values, with one click to add a lane per value. Then the run continues after the switch.
Stop here
End the run. The goal is still measured.
Send email
Sends an email preset. You pick the preset, then bind each of its parameters, and the recipient, to a source:
| Source | Resolves to |
|---|---|
| Fixed value | The text you type |
| Contact field | name, email, externalId, or properties.<key> |
| Trigger event property | A property of the event that started this run (empty for other trigger kinds) |
| (none) | The parameter's sample value from the preset |
The recipient defaults to the contact's email; set it to a fixed address to notify your own team, or to another contact field. A required parameter that resolves to nothing (and has no sample) fails the step rather than sending an email with a hole in it. A missing recipient skips the step.
Call webhook
POSTs JSON to your URL (10-second timeout; a non-2xx response fails the step):
{
"workflowId": "…",
"runId": "…",
"contact": {
"id": "…", "externalId": "user-123",
"email": "ada@example.com", "name": "Ada",
"properties": { "plan": "trial" }
}
}The request carries User-Agent: JourneyKit-Workflows/1.
More actions
Set a contact property, Increment a property, Tag the contact, Track an event (as if your product sent it, segments and other workflows react), Enter another workflow (optionally stopping this one), and Notify your team by plain-text email.
Runs
Every entry creates a run. It records the step it is on (as a path, e.g. 2 › yes › 1 for the second step of a branch's Yes lane), every step it has visited, and ends as one of:
| Status | Meaning |
|---|---|
completed | All steps done, or the goal was reached mid-run (the nudge already worked, so it stops) |
exited | A check didn't match, a Stop here step ran, the contact was deleted, or they were in the control group |
failed | A step threw, the error is stored on the run |
Everything a step sends is recorded as a nudge (channel, payload, sent / failed / skipped, error), visible on the contact's profile, the workflow page, and Email → History.
Measurement
Set a goal event and a window (hours). A run counts as a success if the contact performs the goal event within the window of entering, whether or not the run is still walking steps. Goals are matched as events arrive, so nothing needs to poll.
Set a holdout (0–50%) to turn the workflow into an experiment: that share of entrants is assigned to a control group that receives no steps. The workflow page then shows the goal rate of nudged vs. held-back contacts, the lift, and whether the difference is statistically significant. 0% means no experiment, the goal rate is still reported.
Settings
The Enabled switch controls whether the trigger enters contacts. A new workflow starts enabled, so contacts enter as soon as it is saved; one saved without steps starts disabled, since enabling requires at least one step. Workflows an AI assistant creates through the JourneyKit plugin start disabled, for you to review and switch on. Disabling stops new entries, runs already in progress finish on their own.
Run once per contact (default on) means a contact who has been through the workflow never enters again. Off, they can re-enter, and Allow parallel runs decides whether a new trigger waits for their current run to end, or starts another run alongside it.