Forms & fields

How to build a form in the designer, the input fields you can drop onto it, the field-name binding that turns an input into saved data, and how a submit lands a response in your inbox.

A form in FlowRunner is just a page (or a section of one) that contains input fields and a submit button. You build it the same way you build any page — drag blocks onto the canvas — and when you publish it, every submission is captured for you automatically. There is no wiring to set up: a published page is wrapped in a form that posts to FlowRunner's own submission endpoint, so responses always land in the Submissions inbox.

Build a form

1. Open the designer and add the input blocks you need (see the list below) from the Input group in the block palette.
2. Give each input a Field name so its answer is saved — this is the single most important step (covered next).
3. Add a Button and set its Type to submit so clicking it sends the form.
4. Publish the page. Visitors fill it in, submit, and see a success message.

INFO

📸 Screenshot — the Input group in the block palette, with Text input, Dropdown, Checkbox and File upload visible.

The input fields

These live under the Input category in the palette. Only the fields with a Field name actually record an answer — the rest are interaction controls or layout helpers.

Block	What it is	Records an answer?
Text input	Single- or multi-line text. Supports typed inputs (email, number, tel, url, date, time…) and a validation pattern.	Yes — set a Field name
Dropdown	A drop-down list of options you type one per line.	Yes — set a Field name
Checkbox	A tick-box for a yes/no answer (saved as true/false).	Yes — set a Field name
File upload	Lets a visitor attach a file. See File uploads.	Yes — set a Field name
Toggle, Radio, Slider	On/off, one-of-many and numeric controls.	Not yet — they render but don't expose a field-name binding
Button	The action control. Set Type to submit to send the form.	No
Field group	Groups a label, input and helper text together for layout.	No

NOTE

To collect a single yes/no answer today, use a Checkbox (which has a Field name) rather than a Toggle. Text input, Dropdown, Checkbox and File upload are the four fields that capture data.

The name binding

A field is only saved if it has a Field name (the "Field name (form binding)" property in the inspector). On submit, FlowRunner reads every named input on the page and builds an object of name → value:

{
  "email": "sam@example.com",
  "message": "Please call me back",
  "subscribe": true
}

The field name becomes the column in your responses table and the key your flows read. Choose short, stable names like email, name, phone — an unnamed field is invisible to the submission, no matter what the visitor types into it.

TIP

Reuse the same field name across pages when it means the same thing (always email, never email on one form and emailAddress on another). Consistent names keep your CSV exports and flows tidy.

The submit button

There is no special "submit" block — a submit button is an ordinary Button with its Type set to submit. When a visitor clicks it, the whole page's named fields are collected and sent in one request.

What happens on submit

Required-field checks and spam filtering happen on the server, where they can't be bypassed — see Validation. Once saved, a submission can optionally kick off a flow with its data, so you can send an email, write to a database, or call another service.

See also

• Submissions inbox
• File uploads
• Validation
• Form triggers