Automations → Workflows lists workflows (name, first trigger, status, steps, and a "Last Run" column that actually shows when it was last updated). Filter by name, status and trigger type. Workflow Templates offers 23 starting points that create a draft; their wording follows the site's default language. New Workflow starts empty.
The editor
Name (up to 200), Description, and, for an existing workflow, Status (Draft, Active, Paused, Archived). Active is blocked while the graph has validation errors; this is checked in the browser only. New workflows are always drafts.
The graph needs at least one trigger, no cycles, every node reachable, a condition with an operator, a delay with a time, a wait with an event name, and each action with a type. Up to 500 nodes.
Run Now and Delete appear for existing workflows. Run Now is enabled by the status shown on the screen even if unsaved, but the server needs the saved status to be Active. Delete removes the workflow and its entire execution history for good.
Expressions
Write {{trigger.field}}, {{steps.<id>.field}} or {{vars.name}}. An unresolved path becomes empty text; a value that is exactly one placeholder keeps its type. Email, SMS, notify, chat message and AI prompt fields interpolate; HTTP request, webhook and log fields do not, even though the form suggests it.
Conditions
Field path (default trigger.status), operator and a value that is always typed as text. "Equals" compares strictly, so a number or yes/no field never equals the text you typed; use contains, exists or greater/less than. "In" and "Not in" cannot be used from the form.
Test run
Choose a sample payload (from the event catalog, or the last real run) and press Run test. Only log, transform and condition steps actually run; everything else is simulated ("Nothing was sent"), and waits are reported rather than waited on.
Settings
Loop guard (per hour), step timeout (default 30 s), maximum run time (default 15 minutes), default retries, variables, rate control (max concurrent up to 100, throttle, debounce up to an hour) and failure alerts (in-app on by default, optional emails). A condition action is different from a condition node and fails the step when false; prefer the node.