Field settings control how a field behaves in forms, APIs, and integrations. They define its technical identifier, display label, default behavior, and rules for visibility.
General Properties
- System name – the internal identifier of the field. Used in integrations mapping.
- Type – the field type (Text, Number, Checkbox, etc.). Determines what kind of data can be collected. See the section Field Types below for more information.
- Label – the name shown to end users in forms.
- Placeholder – helper text displayed inside the input when it is empty (e.g. “Enter your ZIP code”).
- Default value – a pre-filled value that appears unless the user overwrites it.
- Input mode – defines the expected input method in the frontend (e.g. text, tel, email). It mainly affects mobile devices, where it prompts the appropriate on-screen keyboard. See the section Input mode below for more information.
- Value format option – an optional mask that formats the value in the frontend (e.g. ### ### ### for phone). This setting overrides the default mask defined by the field type.
- Note – internal note for admins, describing the purpose or usage of the field.
Conditional Display
- Not Show If System Name Equals – hides this field if another field’s system name has the specified value.
- Show Only If System Name Equals – displays this field only if another field’s system name matches the specified value.
Checkboxes
Options that define the behavior of the field:
- Required field – the field must be filled before submission.
- Editable – the field can be modified by the user.
- Hidden field – the field is stored but not shown in the form.
Field-Type Specific Options
Some field types add extra configuration sections:
- Checkbox Accordion – includes a Description section to enter the explanatory text shown with the field.
- Select / Radio Button – include a Values section to define the available options for selection.
Input mode
The Input mode setting defines the expected input method in the frontend. While it has little impact on desktop browsers, it is important on mobile devices, because it determines which type of keyboard will appear.
Supported input modes:
- text – default mode, shows the standard keyboard for free text.
- tel – optimized for telephone numbers, shows a numeric keypad with 0–9, +, *, #. We usually recommend using this input mode even for phone numbers, as it provides a better keyboard layout.
- email – optimized for email addresses, shows @ and . keys prominently.
- url – optimized for URLs, shows /, ., and www. shortcuts.
- numeric – numeric keypad for entering numbers only (does not allow symbols like + or -).
- decimal – numeric keypad with a decimal separator (“,” or “.” depending on locale).
👉 Tip: Always choose the input mode that best matches the expected content. This makes form filling faster and reduces input errors, especially on mobile.
Special use cases
Hidden field with default value – You can hide a field from the user and set a default value in the field settings. This ensures that every record created with this structure contains the same constant value, even though the user never sees the field. Typical examples include internal flags, campaign IDs, or fixed country codes.
Hidden field with Autofill – Instead of a static default, you can hide a field and let its value be filled automatically through integrations. Using the Autofill feature, the system can import values from an external service (via Connection Creator). For example, you might provide a company ID in one visible field, and have the system automatically fill hidden fields such as company address, postal code, or operator.