Pre-filling form fields

Pre-filling means a form opens with values already populated, so the user doesn't have to type them. It speeds up requests and reduces errors — for example, showing the requester's department automatically, or carrying an amount entered earlier into a later approval step.

There are a few ways to pre-fill a field, depending on where the value comes from.

Ways to pre-fill

1. Static default value

Set a default value on the field in the field settings. The field opens with that value, which the user can change (unless it's read-only). Best for a fixed, common answer.

2. Carry data forward from earlier steps (Data Center)

A later Input or Approval form can open pre-filled with values captured earlier in the request — form responses from a previous step or a node's output. You reference those values from the Data Center using {{...}}, and the field opens with the resolved value.

3. Live data at initiation — Trigger Sync

To pre-fill the initiator form with live data (for example, fetch the requester's profile, manager, or current balances from an integration before they see the form), use a Trigger Sync: a Sync Block on the trigger path that runs synchronously at initiation, before the form is shown.

  1. On the trigger path (before the initiator input), add a Sync Block so it executes synchronously at start.
  2. Inside it, add the steps that fetch/compute the data — for example an Action node that calls an integration, or a Function node.
  3. Map the step's output into the form fields (via the Data Center {{...}}), so each field opens populated with the fetched value.

Because the block runs synchronously up front, the data is ready by the time the form renders.

4. Conditional autofill

To populate a field automatically when conditions are met as the user fills the form, use Form Settings › Conditional autofill. This can be toggled per node.

5. Saved drafts

If a user saves a task as a draft and returns later, the form restores their in-progress values automatically — no setup needed.

Per-component notes

How a value pre-fills depends on the field type:

  • Text / number / date — the value is shown directly in the field.
  • Dropdown / Master / User fields — pre-fill the selected option; these need both the underlying value and its display label to show correctly. Multi-select fields pre-fill with a list of values.
  • Field Array — can open with one or more rows already populated.

Where it's configured

  • Default value — in the field's settings in the Form builder.
  • Trigger Sync — in the workflow builder: a Sync Block on the trigger path, with its outputs mapped to the initiator form's fields.
  • Carry-forward — reference Data Center values ({{...}}) in the field.
  • Conditional autofill — under Form Settings › Conditional autofill.