Forms

Forms collect input from people, including people without an account. A form can start a flow (an entry form, such as a request or intake page) or pause a flow for a person to review, correct or approve data (an in-flow form).

The Forms list

Open Build › Forms. Each row shows the name, identifier, status (Draft or Published, switchable right in the Status cell), version and last update. Use New Form, Import (a form file) and Trash at the top. Row actions: Edit, and in the menu Access Link (copies a signed, expiring link), History, Duplicate and Delete.

Building a form

1. 1
   Create the form. On Forms click New Form and give it a Form name. The builder opens on the Design tab.
2. 2
   Add fields. Open the field palette (Build your form) and drag fields onto the grid, or search them. The Outline tab lists every field in order.
3. 3
   Arrange them. Drag fields between cells. Set the grid's Columns (1 to 6) and Rows with no field selected, and each field's Span and Align.
4. 4
   Configure each field. Click a field to edit its Field Properties: label, help text, placeholder, required, validation and visibility rules.
5. 5
   Preview and save. Switch to Preview and try Desktop, Tablet and Mobile, then click Save. If something is invalid, the builder lists what to fix.

Field types

Field settings

Validation, cross-field rules and visibility are enforced on the server as well as in the browser: a hidden field is never accepted, even if someone tries to send it.

Records grid

A Records grid shows rows from The data passed into this step (on an in-flow form) or from A flow. Switches: Allow editing, Search box, Allow add row, Allow delete row; Rows per page (1 to 100); Columns with a header and an Editable switch each (leave empty to derive columns from the data). Use it for batch review: a reviewer corrects twenty invoice lines in one task.

Button actions

Form settings and appearance

• With no field selected: Title, Description, Submit button label, grid structure and a light/dark/auto Theme switch.
• More › Settings: Display name, Form id, the Public Link, and Theme (brand color, surface, text color, mode, corner radius, logo URL) with a contrast check.
• Uploads: choose a Storage destination (one of your storage connections, such as a bucket or file share) and a Folder such as intake/claims. Files people upload go to your storage. Without a destination, uploads are refused in production.
• Translations: set the Original content language, Add language (for example de or fr-CA) and translate the title, description, submit button, and every label, help text, placeholder, choice and grid column. The coverage view shows what is missing, and stale translations are flagged when you change the original. Visitors see the best match for their browser language.
• More › Export downloads the form definition.

Publishing and sharing

1. 1
   Publish. Click Publish in the builder (or switch the status in the Forms list). Only published forms can be opened by the public; Unpublish takes it offline.
2. 2
   Copy the link. Use More › Copy public link for the open address https://if.neblex.com/f/<workspace>/<form>, or Access Link in the Forms list for a signed, expiring link.
3. 3
   Share it. Send the link to the people who should fill it in. They do not need an account.

History, duplicate, Trash & restore

Every save is kept as a version. History shows the versions; Compare shows side-by-side changes and Restore this version makes an old version the new current draft. Duplicate creates an independent draft copy with a new name and identifier. Delete first checks where the form is used; unused forms move to Trash, where Restore brings them back.

Starting a flow with a form (entry form)

1. 1
   Add the trigger. In the flow, add Form (starts flow) from the Triggers group.
2. 2
   Select the form. Choose the form; the Output sample shows the record the flow will receive, one key per field.
3. 3
   Choose who can submit. Anyone with the link, Capability link only, or Named people only.
4. 4
   Save and activate. Publish the form and set the flow Active. Each submission starts a run with the answers as input.

Pausing a flow for human input (in-flow form)

1. 1
   Add the step. Add Wait for form where a person must act, and connect the steps before it (their records pre-fill the form).
2. 2
   Select a form. Any form can be used in-flow, published or not.
3. 3
   Decide who acts. Add people under Notify these people, route to named people or skills, or leave it in the shared Tasks pool. See Human tasks.
4. 4
   Continue with the answer. Connect the next steps. The submitted data is the step's output, and a decision button adds _outcome to branch on.

Notifying people (recipients)

1. 1
   Open the Wait for form step and find Notify these people.
2. 2
   Add recipients, one per line. A fixed address ([email protected]) or a value from the data ({{ ticket.assignee_email }}).
3. 3
   Save. When the run reaches this step, each recipient receives a private, expiring link that opens the pre-filled form. Anyone listed can act; the first submission continues the flow.

Multi-page forms (journeys)

A flow can pause on several forms in a row. When a person submits one page and the flow immediately reaches the next form, that page opens right away in the same session, pre-filled with everything collected so far: intake, then review, then confirm. If the next form has recipients, it becomes a task for them instead and the current person is done. When the flow finishes, the person sees the flow's closing message.

Decision buttons (approve / reject)

1. 1
   Add a Button field for each choice.
2. 2
   Set its action to Record a decision and a value such as approve or reject, with a clear label.
3. 3
   Branch the flow. On edges after the step, add conditions on _outcome. A decision can only be one the form offers, and each decision is recorded with who acted and when.

What happens after submit

The submission is validated (required fields, patterns, ranges, cross-field rules, visibility). If it is valid, an entry form starts a run and an in-flow form resumes one. The page then shows what the flow decides: a message, a redirect, the next form, or the default Thank you. Your response has been recorded. If validation fails, the invalid fields are highlighted so the person can correct them.