Skip to main content
This is the hands-on path from an empty canvas to a published, running workflow. For what each individual step does, see the step reference; this page is about the builder itself.

Three ways to start

  • From scratch — the Create workflow button opens a blank canvas at once.
  • From a template — pick a proven pattern from the templates gallery and refine it in the editor.
  • With AI — describe your goal in plain language and let the assistant assemble a first version for you to adjust.

Build it

1

Configure the trigger

A new workflow starts as a draft with a Manual run trigger. Click the trigger card at the top of the canvas to pick a different start — a schedule, a webhook, or an intent signal. See Triggers for every option. Trigger changes also stay in draft until you publish.
2

Pick contacts or companies and add the first step

Use the + button to open the step picker. For the first step, the Contacts / Companies tabs decide what the workflow operates on; the picker then shows the import steps that fit. Hover any step for a description and a link to its reference entry.
3

Chain enrichment, conditions, and actions

Keep adding steps with + after any node: enrich the records, branch with a condition, then act — lists, campaigns, CRM export, notifications. The picker only offers steps compatible with what the previous step outputs.
4

Save the draft

Drafts are lenient: steps can stay unconfigured while you sketch the flow. The header shows Unsaved changes / All changes saved — there is no autosave, and navigating away with unsaved edits asks whether to stay, discard, or save the draft first. A name is optional (“Untitled workflow” is fine until publish).
5

Publish

Publish makes the workflow live and takes you to its Runs tab. If the button is disabled, its tooltip says exactly what’s blocking — an empty or broken graph, an unconfigured step, a condition branch with no steps after it, or a webhook trigger whose first step can’t accept the declared input. A blank name is filled in automatically on publish.

Editing a published workflow

Published workflows keep running while you edit:
  • Structural edits show an Unpublished changes badge in the editor and a Draft changes badge on the workflows list — the live version is unaffected until you publish again.
  • Republishing bumps the version (Published v2, v3, …); every published version is kept in the version history.
  • If someone else edits the same workflow, the second save is rejected with “Someone else edited this workflow” — reload to pick up their changes before continuing.
Once a condition branch has configured steps under it, the condition locks its branch layout — remove the downstream steps first if you need to restructure the branching.

Next steps

Manage workflows

Runs, versions, settings, permissions, and templates.

Triggers

Every way a workflow can start.