The flow editor: steps, saving, publishing and testing

The editor opens when you create a flow or click one in Flows. It needs a computer: on a phone or a small tablet the flow is view-only — Open on a desktop to edit.

The parts of the editor

• The canvas in the middle — the trigger at the top and the steps under it, joined by lines. Drag to move around, scroll to zoom.
• The step library on the left — Triggers first, then CRM, Push, CDP, Logic & Flow, Pages & Agents and the other apps. Search with Search steps….
• The step panel on the right — opens when you click a step, with three tabs: Settings, I/O and Test.
• The toolbar — the flow's name (double-click to rename), Unsaved changes / All changes saved, undo and redo, the AI builder ✦, the variables panel { }, the guide ?, then Save, Publish and Run.

Add a step

• Click a step in the library — it is added at the end and opens — or drag it onto the canvas.
• + on the line between two steps inserts one there and opens a search box.
• Add Step under the last step adds one at the end.

A step that needs an account says Needs a connection — you'll be asked to connect: Connections. Delete a step by selecting it and pressing Delete; Ctrl+Z brings it back.

Fill in a step

On Settings:

1. Step Name — what it does, in your words.
2. Connection — for apps that need one; Monfri's own (CRM, CDP, Push, Pages) are set up for you.
3. Action — what to do, for example Create Deal.
4. The action's fields. Required ones are marked; a field can take text or a value from an earlier step.
5. Execution Options — Continue on failure lets the flow go on if this step fails; Retry on failure with Max Retries tries it again.

Use data from earlier steps

Every step can use what the trigger and the steps before it produced. Click { } to open the variables panel, then click a value to put it into the field you are in. It appears as a pill, and when the flow runs it is replaced with the real value — written out it looks like {{trigger.body.email}} or {{steps.step_1.email}}.

The panel shows sample values until something has run; run the flow or test the steps from the top down to see real ones.

Test a step

Test → Test Step runs only that step and shows the result.

• It really does the action. A test of Send email sends the e-mail; a test of Create Deal creates the deal. Test with your own address and records you can delete. The one exception is Run agent: its test does not start the agent.
• The AI assistant never tests a step that sends to people — an e-mail, an SMS, a push or a message. Test it yourself, with your own address.
• In a test, the trigger's values are samples, and earlier steps give what their own last test returned. Test from the top down, so each step works with real values.

I/O shows a step's Input and Output from the last run. A trigger cannot be tested on its own — run the flow.

Save, publish, run

• Save (Ctrl+S) keeps your changes as a draft. Nothing is saved until you click it; the browser warns you before you leave with unsaved changes.
• Publish (Ctrl+Shift+P) saves and makes the draft live. A flow with errors does not publish — the message says what to fix. The published version keeps running while you edit the next draft.
• Run (Ctrl+Enter) runs the published version now — Publish first before a flow has been published. Publish your changes before you try them.

Every publish is kept as a version; a run's page shows the versions and what changed: Runs.

Shortcuts

On a Mac, use Cmd for Ctrl.

If something doesn't work

Flow is not valid: …

The draft has a problem — a step without an action, a required field left empty, a connection missing. The message lists them; fix each and publish again.

My changes are gone

They were not saved. The editor saves only with Save or Publish.

Run is greyed out

The flow has not been published yet. Click Publish.