Address
A structured address field with separate sub-fields for each component. Ensures consistent, parseable address data.
Sub-fields
| Sub-field | Description | Required? |
|---|---|---|
| Name | Recipient name | Configurable |
| Line 1 | Street address | Configurable |
| Line 2 | Apt, suite, unit | Optional |
| Zip Code | Postal code | Configurable |
| City | City name | Configurable |
| State | State/province/region | Configurable |
| Country | Country selector dropdown | Configurable |
Configuration
| Field | Description |
|---|---|
| Country selector | Default country |
| Required sub-fields | Which sub-fields must be filled |
| Country list | Which countries to show in the dropdown |
Common uses
- Shipping address
- Billing address
- Event venue location
- Office location
- Home address for employee records
Tip
Use the Address field instead of separate Short Answer fields for each address component. It gives you structured data that's easier to process in workflows. Each sub-field is a separate variable.
Configuration tabs
Every field has 5 configuration tabs when clicked on the form canvas:
| Tab | What you configure |
|---|---|
| Design | Question text, description, placeholder, help text |
| Data | Default value, variable name, prefill from URL parameters |
| Settings | Required/optional, read-only, hidden |
| Validations | Format rules, min/max, custom error messages |
| Image | Attach an image alongside the question |
Using in workflows
When this field is part of a form connected to a workflow via the Form Submission trigger, its value is available as a variable:
{{trigger.fieldName}}
Use it in any downstream node: send it in an email, store it in a database, pass it to an AI node for analysis, or use it in an If-Else condition for routing.