Building your first Flow

This guide builds a complete Flow: as soon as someone submits a sign-up form, a confirmation email goes out and the status in the Grid gets set.

Prerequisite: a Grid with a field of type E-Mail and a field of type Single Select (e.g. Status with the options New and Confirmed), plus a form on it.

1 · Create the Flow

1. Open the Flows area in the sidebar.
2. Click Create Flow.
3. The Flow is initially named New Flow. Rename it — this pays off quickly once you have several Flows.

You land in the Editor, an empty canvas.

2 · Choose a trigger

The editor asks: When should the Flow start?

1. Open the Trigger tab.
2. Choose Entry via form — New entry added via form.
3. In the step, select the Grid and the form.

You can click the step or drag it onto the canvas.

The trigger determines which data is available

The choice of trigger decides what all subsequent steps can work with. Entry via form delivers the newly created entry with all its fields — that's the foundation for everything that follows.

The trigger can't simply be swapped out afterward without adjusting the following steps. So think it through first.

3 · First action: send email

1. Open the Actions tab.
2. Choose Email.
3. Connect the trigger to the new action, if it doesn't happen automatically.
4. Click the action to configure it.

In the Recipient field, you don't want a fixed address — you want the one from the entry. Use Use values from previous steps and select the trigger's email field.

Fill in the subject and body the same way — fixed text and values from the entry can be mixed.

Inserting field values

In text fields, Ctrl + Space opens the selection of available Grid fields. The editor shows this hint on its own too.

4 · Second action: update entry

1. In the Actions tab, choose the Update entry step.
2. Connect it after the email action.
3. As the entry to update, choose the entry from the trigger.
4. Set the Status field to Confirmed.

The Flow is complete.

5 · Test it

Test before you go live. A faulty Flow that reacts to real form submissions sends faulty emails to real people.

The editor offers several test types. For this case, With data from the Flow form — Open the form and test with submitted data — fits.

Alternatively, Test Flow uses the last row of the Grid.

After the test, check the History tab to see whether the run has the status Done. On Error, open it and use Show error details to see what went wrong.

→ Testing Flows

6 · Go live

If the test runs cleanly, the Flow is ready. From now on it reacts to every real form submission — a newly created Flow is switched on.

Verify with a real submission first

Submit the form yourself once, using your own address. A test run in the editor and a real run don't always behave identically — especially for fields that are only set via the form.

Using the switch to the right of the Editor and History tabs, you can take the Flow out of service at any time without deleting it.

Working in the editor

Tool	Purpose
Center on all nodes	Brings all steps into view
Auto-arrange nodes	Tidies up the layout
Show/hide minimap	Overview for large Flows

The menu on a step offers Rename, Configure, Add connection, and Delete.

Rename your steps

Default names like "Email" stop meaning anything once you have five mail steps. Name steps after their purpose — "Confirmation to attendee", "Info to team". It pays off when debugging.

Typical beginner mistakes

Symptom	Cause
Flow doesn't start	No trigger set, or the trigger points to a different Grid or form
Flow starts but does nothing	The steps aren't connected to each other
Email goes to no one	The recipient field contains fixed text instead of a field value
Update doesn't take effect	The step doesn't update the entry from the trigger
Flow still has errors	A step is incompletely configured

Next

• Trigger
• Actions
• Data between steps
• Testing Flows