Skip to content

Form trigger

The Form Trigger publishes a hosted form. Each submission starts a workflow run with the submitted values as trigger data.

The Form Trigger panel: the form title and description, then the first two fields, Full name as a required Text field and Work email as a required Email field.The Form Trigger panel: the form title and description, then the first two fields, Full name as a required Text field and Work email as a required Email field.

When to use it

  • Simple intake: request a refund, ask for access, log a support ticket.
  • Internal forms, such as an expense claim.
  • Collecting files from people who do not use Flero.

The form is intentionally simple: one page, no conditional logic. For multi-step flows, build your own front end and call a webhook.

Configuration

The form

Field Notes
Form Title Shown at the top of the form.
Description Instructions shown under the title.
Submit Button Text Defaults to "Submit".
Success Message Shown after a successful submission. Defaults to "Thank you! Your submission has been received."
Allow Multiple Submissions When on, the success screen offers a button to submit another response.

Fields

Click Add Field for each question.

Setting Notes
Label The question people see.
Type Text, Text Area, Number, Email, Dropdown, Checkbox, Date or File Upload.
Required The form will not submit without it. Flero checks this again on the server.
Placeholder For Text, Text Area, Email and Number.
Options For Dropdown. Comma-separated.
Minimum / Maximum For Number.
Allowed file types / Max files For File Upload, for example pdf, jpg. Max files defaults to 5.

The form URL

Save the workflow to generate the URL. It appears under Form URL in the inspector:

https://acme.flero.ai/forms/public/<token>

Anyone with the link can open the form. They do not need a Flero account. The URL stays the same when you edit the form.

Form changes reach respondents only after you save the workflow (Ctrl+S / ⌘S).

Trigger data

Submitted values are keyed by each field's internal ID, which Flero generates when you add the field (for example field_1760000000000). The trigger node outputs:

{
  "formData": {
    "field_1760000000000": "Ada Lovelace",
    "field_1760000000001": "ada@acme.example"
  },
  "submittedAt": "2026-10-13T10:00:00.000Z",
  "formTitle": "Access request"
}

The same values are on {{ $trigger.payload }}. Because the keys are IDs rather than labels, pick the field from the data picker after a test submission instead of typing the expression by hand.

Files

File Upload fields upload each file when the person picks it. The field's value is a list of file references:

[
  { "fileId": "...", "fileName": "receipt.pdf", "fileSize": 48213, "mimeType": "application/pdf", "url": "/api/files/.../receipt.pdf" }
]

The files are stored in your workspace and count against its storage quota. The form refuses files over 100 MB. If the workspace is over quota, the upload fails.

Activating the form

  1. Save the workflow.
  2. Set the workflow to Active in the editor toolbar's version menu.
  3. Share the form URL.

While the workflow is inactive, the form shows "Form not found or the workflow is no longer active".

Tips & gotchas

  • One submission, one run. A form with 20 fields still starts one run.
  • Do not put secrets in placeholders or options. Everything in the form definition is visible to anyone with the link.
  • A failed submission tells the person. If Flero cannot queue the run, the form shows an error asking them to try again, rather than a false success.
  • Submissions appear in the execution history like any other run.

Found something out of date? This page lives in the Flero docs content set.