The Textbox field is used to capture text-based information in a form. You use it when users need to type names, contact details, descriptions, or formatted content. It supports different text formats so you can control how much text is entered and how it is stored.
Choose the Textbox variant based on the type of text you expect and how the data will be used later.
| Category Types | Description |
|---|---|
| Text |
Example: Full name, John Doe |
| Text Area |
Example: Address, 123 Main Street, City, Country |
| Email ID |
Example: example@gmail.com |
| Email IDs |
Example: example1@gmail.com, example2@gmail.com, example3@gmail.com |
| Phone Number |
Example: 1234567890 |
| Rich Text |
What users can format
Use cases
|
| Rich Text Editor (RTE) Modes |
The platform supports two RTE modes: Static Mode
Dynamic Mode
|
Note
This field supports all standard field properties. Refer to the Form Field Properties article for validation, visibility, and styling options.
Case Type
Available options
Use this setting when consistent text formatting is required for reporting, matching, or integrations.
Validation controls how and when text input is accepted. You use validation to prevent incomplete, incorrect, or unusable data from being saved.
Common validation options and when to use them.
| Type | Description |
| Required |
|
| Minimum and maximum length |
Example
|
| Email format validation |
|
| Numeric validation for phone numbers |
|
| Case enforcement |
|
| Types | Mistake | Impact | Fix |
|---|---|---|---|
| Using Text instead of Text Area | Using single-line text for long content. | Text becomes hard to read and edit. | Use Text Area for addresses, remarks, or explanations. |
| Using Text for email input | Allowing free text for email addresses. | Invalid emails get stored. | Use Email ID or Email IDs to enforce format. |
| Using Rich Text for simple inputs | Using Rich Text for names or short comments. | Unnecessary formatting and messy data. | Use plain Text or Text Area for clean data. |
| Allowing multiple emails in a single Email ID field | Users enter comma-separated emails in a single email field. | Email actions fail or behave unpredictably. | Use Email IDs when multiple addresses are required. |
| Not enforcing case rules | Storing the same value in multiple formats. | Filtering and matching becomes unreliable. | Use Case Type to standardize text storage. |
Note
Choosing the right textbox type and validation rules early prevents data cleanup problems later.