Blocks
Form
The form trigger: a hosted form you define field-by-field; submissions fire the workflow with the answers keyed by field label.
A hosted form MadMax serves for you: define the fields, share the URL, each submission fires the workflow.
When it runs
On each submission of the form (URL in the Inspector). Active workflows only.
Config
Title plus a field list — label, type, required.
- Title — the form's heading.
- Fields — each with a label, a type (text, textarea, email, number, dropdown with options, …), and required.
Output
The answers, keyed by field label, verbatim:
{ "Name": "Dana", "Email": "dana@bigcorp.com", "Need": "sales" }
Labels are the keys — capitalization included:
{{ payload.Email }}, not {{ payload.email }}. The build-time
linter catches label/ref mismatches, but name fields the way you
want to reference them.
Patterns
- Intake router — dropdown field → switch on the answer → different channels per choice.
- Lead scoring — form → AI score → hot-lead alert + record.
- Internal tools — a form is the fastest UI you'll ever ship.
Gotchas
- Renaming a field's label renames the payload key — downstream refs need the same edit (the linter will point at them).
- Like uploads, verification wants one real submission — the walk opens the form window for you.