A merge field is a token you drop into question text that resolves to a live value when the form is shown — another answer the user already gave, today's date, or your organisation's name. Tokens look like {{field_key}}, and the form replaces them with the real value as it renders, so your questions read naturally instead of repeating information.
Merge fields are authored in the form builder at https://input.ziplineos.com.au. They are supported anywhere a question carries text — the Label, the Help text, and Message (Display) blocks. For the settings those fields share, see Question Settings.
Inserting a merge field
Next to any text field in the builder is an Insert merge field button (a { } icon). Clicking it opens the Insert Merge Field picker with a search box and three groups:
| Group | What it offers |
|---|---|
| Form Fields | Every other question on the same form, listed by its label. Selecting one inserts that field's token. |
| Dynamic Generator | Extra tokens the form makes available for values it derives as the deal runs. Each shows a Dynamic chip. |
| System | Built-in values that don't come from the form (see below). |
Pick an entry and its token is inserted at the cursor. The token's raw form (e.g. {{first_name}}) is shown beside each label so you can see exactly what will be written.
System tokens
| Token | Resolves to |
|---|---|
{{current_year}} | Current Year — e.g. 2026. |
{{current_date}} | Current Date — the date the form is viewed. |
{{organization_name}} | Organisation Name — your org's name. |
How tokens resolve
The syntax is always {{field_key}} — double curly braces around the target field's key (not its label). The picker writes the correct key for you; if you type a token by hand it must match the key exactly, or it won't resolve.
At display time the platform swaps each token for its value, on both Input Hub (broker side) and Collect (client side). If the referenced field hasn't been answered yet, the token resolves to nothing — the surrounding text simply closes up.
Use the picker rather than typing tokens by hand. It guarantees the key is correct and shows you the exact value at a glance — a mistyped key silently renders as blank text.
Worked example
Goal: ask for a child's date of birth using the parent's first name.
- Add a Short Text field labelled "First name" (key
first_name). - Add a Date field. In its Label, click Insert merge field → Form Fields → First name.
- The label becomes:
What is {{first_name}}'s date of birth?
When the applicant has entered "Sam", the question reads "What is Sam's date of birth?" — no duplicate field, no manual wording.
Merge fields vs visibility rules
Merge fields only read and display a value — they create no dependency and change nothing about whether a question shows. To make a question appear, hide, or become required based on another answer, use a visibility rule instead. See Show, Hide & Require Questions with Rules.
Things to keep in mind
- Put the source question first. A merge field can only show a value once it's been answered. Order the source field ahead of any question that references it.
- Tokens follow the key, not the label. Renaming a field's label is safe; the token keeps working. Deleting the source field leaves the token unresolved (blank).
- Preview has no deal context. The builder preview may render system or cross-field tokens as blank — confirm them on a real deal.