The builder lays your automation out as a vertical spine. The Trigger card sits at the top; every step you add appears below it in the order it runs. Branches fan out into lanes and rejoin at a Merge.

• Each step is a flat step card showing its glyph, name, and a one-line summary of what it does.
• The card stays monochrome. The glyph and the summary carry the meaning, so the canvas reads the same in light and dark mode.
• Click any card to open its settings; click the trigger card to change what starts the automation.

Between every pair of cards is a small + connector. Hover the connector and it reads Add step after the step above it. Clicking it opens the step picker, and the new step drops in at that exact spot — you never have to add to the end and drag it up.

The picker slides in from the side. There is a Search steps box at the top and a plain divided list grouped into sections, not a grid of colored tiles:

• Timing: the Wait step, in its three flavors.
• Branches: Filter, If / Else, Switch, and Merge.
• CRM data: set a field, hand the record to a teammate, distribute round robin, create tasks, log activities.
• Communication: notify a teammate, send an email, enroll the contact in a campaign.
• Advanced: call an external URL with the record’s data.

Every row carries a one-line “when to use” description so you can pick the right step without guessing.

When the right move needs judgement instead of a fixed step, that is an AI agent. Agents are built and supervised from their own home, the Agents page in the sidebar; see AI Agent Steps for how they fit alongside rules.

Selecting a card opens a side panelover the canvas with just that step’s options. Filling it out is what turns a placeholder into a finished step:

• Placeholder — a step you dropped in but have not configured yet. You can save it; it shows as Not configured. The trigger and steps you have not set up still let you save a draft.
• Configured — a step with everything it needs. Publishing requires every step to be configured.

A toggle switches between two reads of the graph:

• Flow — the visual canvas with the spine, branches, and Merge nodes. Best for authoring and seeing where paths split.
• Outline — the same steps as a plain indented list. Best for scanning a long automation or reviewing it on a smaller screen. Selecting an Outline row highlights the matching card so you never lose your place; an Open in Flow link jumps back to the canvas.

• Repeat runs: how often the same record can re-enter. Once ever (the default) lets a record enroll a single time; Every time it matches re-enrolls whenever the trigger fires again; Once per period re-enrolls at most once within a window you set.
• Goal — an optional condition that marks a record as having succeeded. When a record meets the goal it exits the flow early and counts toward the conversion rate on the Hub.
• Version history — every publish snapshots the flow. Records already running keep the version they enrolled on, so editing a live automation never changes a run mid-flight.