Choose a field type
The Input tile includes short text, long text, email, number and URL presets. Composite presets group related parts such as full name, address, phone, date of birth and email confirmation. Multipart presets combine their parts under one field key, usually as text. Check an actual submission before mapping parts to SQL columns or API properties. See the illustrated field reference and all 19 composite presets.
Use Dropdown or Radio Buttons for one choice. Use Checkboxes, MultiSelect or Chips when several answers are valid. Store durable option values separately from labels so a wording change does not break a workflow.
Keep stable field keys
Labels are for people; keys are for mappings, expressions and APIs. Use short descriptive keys such as guest_name, workshop and seats. Changing a key can disconnect existing rules, SQL mappings, translations and automation.
Arrange the canvas
Use Rows/Columns or Flex Grid to group related fields. Add a Section Break for a heading. For multiple steps, enable multi-step behaviour and mark the appropriate Section Break as the start of a new page. Check Next, Back and required-field validation on each step.
At narrow widths, columns should stack in a logical reading order. Avoid fixed pixel widths on fields. Use help text for examples rather than relying entirely on placeholders, which disappear while typing.
Review widgets for files, signatures, repeaters and richer controls.