Text
Collects text answers
Last updated
Was this helpful?
Collects text answers
Last updated
Was this helpful?
Text questions are used to collect short or long-form free-text input from responders. Common use cases include gathering names, email addresses, or open-ended feedback.
Text question answers are stored as a string data type.
By default, a text question shows a single-line input. To enable multiline responses:
Select the question.
Enable Multiline? in the settings panel.
Specify the minimum and maximum number of lines for the input box.
To customize the dimensions of the input box further (e.g. to create a longer feedback box):
Open the Style tab.
Toggle Override default text input style.
Apply your desired styling.
To control the length of a responder’s answer:
Enable Max length restriction?
Choose a limit by characters or words.
You can also enable Show remaining count? to display the number of characters or words remaining as the responder types.
To provide additional context and guide responders on the expected input, you can add:
A Prefix (e.g. $ or @)
A Suffix (e.g. USD or .com)
These can be configured in the Settings menu under Prefix? and Suffix?.
To allow a responder to submit more than one value for a single question:
Enable Allow multiple answers in the settings.
Each new input will be treated as an individual item in an array of string values.
Use the Default answer setting to prepopulate the text field with a preset value. This value can still be edited by the responder.
You can dynamically set the value of a Text question by referencing other variables in your flow:
Enable Another answer/variable in the settings.
Any other data-type-compatible variables will be available to choose (e.g. from a previous question, a calculated variable, or an API response).
This is useful for personalization or autofill behavior (e.g. pulling a first name from a previous step).
To assign a static value to a Text question that never changes:
Use the Constant setting.
This is helpful for storing a fixed value (e.g. an internal tag or a source code) in the answers payload without requiring responder input.
