Introduction

The workflow editor

The editor is a canvas with the trigger at the top and the steps below it. Everything you change is saved to a draft; nothing you change runs until you publish.

PartWhat it does
HeaderThe workflow's name (click it to rename), the «Editor» and «Runs» tabs, undo and redo, and the buttons «Discard» and «Publish». They appear only when there is something to discard or publish.
CanvasThe trigger and the steps. Click a block to configure it; drag a block to move it. Zoom, fit-to-view and add-note controls sit at the bottom.
Side panelThe status and the «Live» switch, the public/private toggle, the settings gear and four counters («Completed», «Failed», «In progress», «Average time»). With a block selected it shows that block's configuration.
PaletteThe list of blocks, titled «Add a block». It opens from the plus buttons between blocks.
  • Click a plus button on the canvas to open the palette, which has three groups: «Utilities» (including «Flow control» and «Signals»), «Filmo» (one drop-down per kind of record) and «Integrations». The search box matches names and keywords and ignores accents.
  • Some palette entries add two linked blocks at once, for example the AI classifier together with the switch that routes on its answer.
  • Drag a card to a drop area to move it. There are no move-up and move-down buttons.
  • Deleting a block deletes everything inside it as well. Undo brings it back while the editor is open.
  • Free-floating sticky notes («Add note») are part of the workflow definition, so they are saved in each version.

Not available

There is no search across the canvas, and no duplicate action. To copy a workflow, start a new one from a template or build it again.

Edits are saved to the draft a moment after you stop (after about a second and a half, and never later than five seconds into a long burst). The editor shows no "saving" or "saved" indicator and does not report an autosave that fails.

A saved draft is not a running workflow. When the draft differs from what runs, the editor says so: the «Discard» and «Publish» buttons appear, and the side panel shows «Unpublished changes» if the workflow is live ("it is running the previous version") or «Workflow paused» if it is not.

You doWhat happensDoes it change what runs?
«Publish»Freezes the draft as a new numbered version and rebuilds the triggers. Blank required fields do not stop it (an invalid definition does); if the workflow is live and fields are blank, it is switched off and the editor tells you.Yes: new runs use the new version.
«Publish and activate»Publishes and switches the workflow live. It appears in the notice of the side panel when the workflow is not live. It refuses (422) if required fields are blank or a connected integration is not fully set up.Yes.
Live switch onTurns the automatic triggers on for the version that is already published. It does not publish the draft. The exception is a workflow that was never published (status Draft): there the switch publishes and activates in one step, with the same checks as Publish and activate.Usually no: it runs the old version.
Live switch offStops the automatic triggers. Runs already in flight finish. You can still run the workflow by hand.No.
«Discard»Resets the draft to the published version. It cannot go back past that, and undo cannot recover what you discard.No.
«Run workflow»Only in the side panel of a manual trigger. Publishes first if the draft has changes, then queues a run of the published version.A new version may be created.

A test run is a publish

Running a workflow by hand from the editor publishes a draft that has unpublished changes first. If the workflow is live and has blank required fields, that publish also switches it off. The editor shows a toast, but it is easy to read it as "test started" only.

A step with a required field left blank gets a red border, and the side panel lists the incomplete steps with a button to jump to each. You can save and publish with blanks, but you cannot switch a workflow live while they remain. See Versions.

  • The status pill shows «Live», «Paused», «Draft» or «Archived». A draft is a workflow that was never published.
  • A workflow is «Public» (the whole company can open it) or «Private» (only its creator and administrators). Any workflow with an email or calendar step, or an email or calendar trigger, is forced private and cannot be made public. See Integrations.
  • The gear opens «Workflow settings»: the name, who is told when a run fails («Notify me if it fails»), «Archive» and «Delete workflow». Archiving switches the workflow off; restoring it does not switch it back on. Deleting is permanent and removes its runs.

Administrators only

Every change is restricted to administrators: creating, editing (including autosave), publishing, switching live, running, archiving and deleting. Other members can open the list and (unless the workflow is private) the editor and the run history, but a non-administrator's edits are rejected, and an autosave rejection is silent, so their changes are lost without a warning. The interface does not hide these controls from non-administrators.

Details and the list of roles: Permissions.

  • Run

    Versions

    A workflow has a draft that you edit and a published version that runs. They are different on purpose, and the way they differ is where most surprises come from.

  • Build

    Steps

    Steps run in order, one after another. Each can read what the trigger and the steps before it produced, and each can publish a value for the steps after it.

  • Run

    Workflow permissions

    Two questions get mixed up: who may manage a workflow, and what a run is allowed to do. The first is about administrators. The second is about one person: the creator.

Was this page helpful?