Building a Form

This page explains the everyday editor workflow for creating a lead form.

1. Add the form block

When you add a form to a page, ResultFly can insert a ready-made starter instead of an empty box.

Typical starter content includes:

• a heading
• a couple of fields
• a consent checkbox
• a submit button

This helps you begin from a realistic form instead of assembling everything from scratch.

Starter content is just a starting point:

• You can always delete any starter fields you don’t need.
• You can reorder fields inside the form by moving them up or down in the component tree.

2. Add fields inside the form

Inside a form, use Add field.

This opens a picker with form-specific field tiles rather than generic page components.

Examples:

• Email
• Phone
• Textarea
• Consent
• Checkbox
• Number input
• Date input
• Time input

These tiles are preconfigured so they already behave like form fields.

For example:

• Email starts as an email field
• Phone starts as a phone field
• Consent starts as a required consent checkbox
• Checkbox starts as an optional checkbox (not required by default)

3. Edit field settings

When you select a field inside the form, the right panel shows Field settings.

The most important settings are:

• Semantic key: optional meaning tag (email/phone/name) that helps with validation and prefill
• Field name: a stable name used for integrations and webhook data
• Label: the text shown above or next to the field
• Placeholder: helper text inside the field
• Value type: the expected format, such as text, email, phone, date, or time

For the Phone field, additional settings are available:

• Default country: sets the preselected country and phone mask
• Country mode: controls whether the user can change the country, or if it is fixed (visible or hidden)
• Allowed countries: limits the list of countries available for selection
• Placeholder example: shows an example phone number format inside the field

Each field can also be configured with these behavior toggles:

• Required: visitors must fill this field before they can continue or submit
• Hidden: the field is not shown to visitors, but it can still be pre-filled and sent with the form
• Readonly: the field is shown, but visitors cannot change its value

These settings are per field, so the same form can include a mix of required/optional and visible/hidden fields.

Make sure these combinations are logical:

• If a field is Required and Hidden, it must be pre-filled (for example via query parameters), otherwise the visitor cannot complete the form.
• If a field is Required and Readonly, it must also be pre-filled, since the visitor cannot change its value.

4. Edit form settings

When you select the form itself, the right panel shows Settings.

The most common options are:

• Form name
• Allow resubmit after final submit
• Form action

Form action controls what happens when the button is clicked:

• Next Step: go to the next step of the same form
• Final Submit: complete the form

5. Use templates for speed

Form field tiles are the fastest way to build forms.

They insert preconfigured fields (Email, Phone, Consent, etc.), so you don’t have to start from generic inputs and configure everything manually.

You can use tiles in two ways:

• Add the fields each time you build a form
• Or, if you often reuse the same set of fields, build it once, save it as a workspace template (Save to My Components), and insert it later from My components in other pages or campaigns

6. Use query parameters for prefill

Form fields can be linked to query parameters to automatically pre-fill them from the page URL.

For example, a URL like ?email=john@company.com&utm_source=linkedin will automatically fill the corresponding form fields.

This is useful for:

• Pre-populating visitor data from your CRM or database
• Tracking which campaign sent the visitor (utm parameters)
• Passing data between multi-step forms
• Reducing friction by eliminating re-entry

See Query Parameters for Prefill for detailed setup instructions and examples.