Form Designer
Build multi-step forms visually - add fields, configure validation, conditional logic, branding, and CRM lead capture, then publish and share a public link.
Form Designer
Create, rename, duplicate, publish, unpublish, archive, and restore forms. Build multi-step forms visually with 15 field types, configure required fields, validation, placeholders, options, limits, and patterns, then add conditional fields and branching between steps. Configure branding, logos, colors, and post-submission behavior, preview the form and flow, generate and share a public link, and map lead-capture submissions to your CRM.
Form lifecycle
Forms move through three stages:
| Stage | What it means |
|---|---|
| Draft | The form is editable, can be published, duplicated, or soft-deleted. |
| Published | The form accepts public submissions through its public link. |
| Archived | The form is no longer available for normal public submission. You can restore it to draft. |
Publishing requires every step to contain at least one field. Lead-capture forms also require at least one valid identity mapping to a contact name, email, or phone field.
Only draft forms can be deleted. Deletion is soft deletion, so published and archived forms must be unpublished or restored before you can edit them.
Creating a form
Choose a purpose when you create a form:
- General: Collect information without creating CRM leads automatically.
- Lead capture: Turn submissions into CRM leads and map answers to contact, company, deal, or custom fields.
Create a new form
Enter a name, choose the form purpose, and save the form as a draft. Use a descriptive name that helps admins distinguish the form from other forms in your workspace.
Your new form opens in the designer with an editable first step. You can rename the form later from the form settings.
Building multi-step forms
Use steps to divide a long form into focused sections. Add steps from the designer, then use the visual canvas to arrange each step's fields in the order you want visitors to complete them.
Drag fields onto the canvas and reposition them within a step. Each step must contain at least one field before you can publish the form. There is no documented maximum number of steps or fields.
Use the canvas to configure each field without leaving the form designer. Preview the rendered form to verify labels, spacing, field order, and step navigation.
Field types
Choose the field type that matches the answer you need:
| Field type | What it captures |
|---|---|
| Short text | A brief text value such as a name or company. |
| Long text | A longer response such as a description or message. |
| Number | A numeric value. |
| An email address. | |
| Phone | A phone number. |
| Select | One option from a dropdown list. |
| Multi-select | Multiple options from a list. |
| Radio | One option from a visible group of choices. |
| Checkbox | A checkbox value, such as consent or agreement. |
| Date | A calendar date. |
| File upload | One or more supported files. |
| Image upload | One or more supported images. |
| Video upload | A supported video file. |
| Rating | A numeric rating. |
| Section header | A visual heading and description that organizes fields without collecting an answer. |
Select, Multi-Select, and Radio fields have a list of options. Configure each option with an Option Label and an Option Value. Select Add Option to add another one.
Field configuration
Configure the common settings for each field from its field panel:
| Setting | What it does |
|---|---|
| Label | The name of the field that visitors see. |
| Required | Requires a visible field to have a value before the visitor can continue or submit. |
| Placeholder | Shows an example or prompt inside an empty input. |
| Help Text | Adds supporting guidance below the field. |
| Default Value | Prefills the field with an initial value. |
Not every setting applies to every field type. Placeholder is not available for phone, radio, checkbox, upload, and section header fields. Default Value is not available for upload and section header fields. Required and Help Text are not available for section headers.
Required validation applies only to visible fields. A hidden conditional field does not block submission when it has no value.
Validation options
Validation settings depend on the field type:
| Field type | Validation options |
|---|---|
| Short text | Min Length, Max Length, Pattern (regex), Validation Message |
| Long text | Min Length, Max Length |
| Number | Min Value, Max Value, Integer Only |
| Rating | Min Value, Max Value |
| Date | Min Value, Max Value, Future Only, Past Only |
| Multi-select | Min Selections, Max Selections |
| File upload | Max File Size (MB), Max Files, Allowed Extensions |
| Image upload | Max File Size (MB), Max Files, Allowed Extensions: JPG, PNG, WEBP |
| Video upload | Max Duration (minutes), Max File Size (MB), Allowed Extensions: MP4, WEBM, MOV |
| Section header | Title, Description |
Use Pattern (regex) and Validation Message when a short text field must follow a specific format. The validation message is shown when the value does not match the pattern, and Test Pattern lets you try a sample value in the designer. Use minimum and maximum values to constrain numbers, ratings, dates, and selections.
Upload limits
The upload limits you set on a field are checked in the visitor's browser when they add a file. This covers the maximum file size and the allowed file types. The maximum number of files or images limits how many files a visitor can add in one go. It does not cap the total, so a visitor can add more files in a second round. The server does not check these per-field limits again.
The server applies the same general limits to every upload, whatever the field settings say:
| File category | Supported types | Maximum size |
|---|---|---|
| Images | JPEG, PNG, WebP, GIF | 50 MB |
| Videos | MP4, WebM, QuickTime | 500 MB |
| Other files | PDF, Word, Excel, TXT, CSV | 20 MB |
A field limit that is higher than the general limit has no effect, because the server still rejects the file.
The maximum video duration can be set on a video upload field, but it is not checked when a visitor uploads a video.
Conditional fields
Conditional fields appear only when their trigger condition is met. Open Visibility Conditions in the field panel, add one or more conditions, and choose whether they combine with AND or OR.
Supported operators are:
- equals
- not equals
- contains
- is empty
- is not empty
- greater than
- less than
Conditions can compare text, check whether a field is empty, or compare numeric values. The operators you can choose depend on the type of the controlling field. Use AND when every condition must match. Use OR when any condition can reveal the field.
Conditional fields only appear when their trigger condition is met. Conditions are evaluated in order, so a hidden field's value is treated as empty for downstream conditions. Hidden fields are excluded from required validation and submission data.
Add a conditional field
Add the field that should appear conditionally, open its visibility settings, and select the earlier field that controls its visibility.
Choose an operator, enter the comparison value when required, and select AND or OR if you add multiple conditions. Preview the form and test both the condition-matching and non-matching paths.
Branching between steps
Use branching rules to send visitors to different steps based on their answers. Add rules to the step where the decision occurs.
Each rule contains:
- Conditions: The answers that trigger the rule.
- Combinator: AND or OR.
- Target step: The step to open when the rule matches.
Rules are evaluated in order, and the first matching rule wins. If no rule matches, the form follows the next step in sequential order.
The form checks for cycles in the step flow. A cycle prevents the form from resolving a valid path, so review branch targets when you add or reorder steps.
Branding and post-submission
Configure the form's appearance and what happens after a successful submission:
- Add a logo for the form.
- Configure available branding colors and appearance settings.
- Write a rich-text thank-you message of up to 500 characters.
- Redirect visitors to a custom URL instead of showing the thank-you message.
The thank-you message and redirect URL are mutually exclusive. Choose one post-submission behavior for each form.
A form logo is scoped to that form. Adding or changing it does not change your company-wide branding.
Branding settings are copied when you duplicate a form.
Previewing forms and flow
Preview the rendered form to check its appearance, labels, field order, required states, and post-submission experience. Preview the step flow separately to verify conditional fields, branch targets, fallback navigation, and the path visitors see for different answers.
Preview both the form appearance and the flow logic before publishing. Test each meaningful answer path, including paths that hide fields or skip steps.
Publishing and sharing
Publishing makes the form available through a public link. Before publishing, confirm that every step contains at least one field and that lead-capture forms include a valid identity mapping.
Publish and share a form
Open the draft form, preview the form and its flow, then select Publish. After publishing, copy the generated public link and share it with respondents.
Use Unpublish when you need to stop accepting public submissions while keeping the form available for later editing. Restore an archived form to return it to the draft lifecycle.
CRM lead capture and field mapping
Choose the Lead capture purpose when form submissions should create CRM leads. New lead-capture forms start with these mappings:
- Name to the contact's Name
- Email to the contact's Email
- Phone to the contact's Phone
A lead-capture form cannot be published until at least one field maps to a contact name, email, or phone field.
Use Maps to CRM Field in the field panel to map answers to the following CRM targets:
- Contact: Name, Email, Phone, Role, Location
- Company: Name, Org. number
- Deal: Value
- Custom fields: Your CRM custom fields of the types dropdown, radio, checkbox, and multi-select, listed under Contact, Company, or Deal
- Timeline only: Store the answer in the lead timeline without mapping it to a standard field
Mapped submissions create or update CRM leads automatically. The CRM finds an existing contact by normalized email or phone when possible, opens a lead in the configured pipeline, and writes all submitted answers to the lead timeline.
Submission processing is queued and retried up to three times. Flagged or low-verification submissions are stored but do not create leads.
Duplicating a form
Duplicate a form when you want to reuse its structure without changing the original. The duplicate is an independent draft with:
- A new form, step, and field identity.
- A fresh public slug.
- The original name followed by (Copy).
- The same purpose, steps, fields, branding, and branching configuration.
- No submissions or lifecycle timestamps from the original form.
Conditional field conditions and branching rules are copied unchanged. They still point to the fields and steps of the original form, not to the new fields and steps in the copy, so they do not work correctly in the duplicate. Before publishing, open each conditional field and each branching rule in the copy and select the controlling field and the target step again.