# AI Landing Pages - Configuring Forms

## Checking the Forms tab

When generating a page using the [automatic creation](/en/topics/artificial-intelligence/ai-landing-pages/ai-landing-pages-creating-the-first-page.md), or importing code, the forms present will be detected automatically and displayed in the **Forms**tab. In this section, all forms found on the landing page are listed.

When a lead fills out one of these forms, they will be automatically created in the platform with the provided data or, if they already exist, will be identified. From that point, all actions configured on the form will be executed, and the lead will begin to be tracked. This means that whenever they access a tracked link or a Sprinthub landing page (or any page with the tracking script installed), their activity will be recorded in the lead's history, as well as the [UTM tags](/en/topics/settings/tracking/tracking-utm-tag.md) of the URL.

<figure><img src="/files/64446425720dfd83a87566e17660bdf308889eb4" alt=""><figcaption><p><em>Builder home page.</em></p></figcaption></figure>

<figure><img src="/files/f197870d6b01e33ac3900e6e2179665e37a8157c" alt=""><figcaption><p><em>Forms Tab.</em></p></figcaption></figure>

## Form Settings

In addition to renaming the form to facilitate organization and use in automations, you can adjust the following properties:

* **Kiosk Mode**: always creates a new lead, even if one already exists. Ideal when the form is filled out by a third party. **This mode prevents lead tracking**.
* **Overwrite information on repeated submissions**: replaces the lead's data with the most recent whenever the form is resubmitted.
* **Automatically resolve conflicts**: automatically resolves data conflicts between leads (cannot be used together with the blocking option).
* **Block submission when a conflict occurs**: prevents the form from being submitted and displays a warning if there is a lead with the same unique fields.
* **Redirect on submit**: after submission, directs the lead to a specific page (e.g., “Thank you for contacting us!”).
* **Unarchive lead on submit**: automatically unarchives archived leads who fill out the form.

<figure><img src="/files/c2ec63e99bf31befdd10099f6b09507657388127" alt=""><figcaption><p><em>Form Settings.</em></p></figcaption></figure>

## Form Fields

Fields are identified automatically. For each one, you must define:

* the type of expected value (text, number, phone, email, selector, etc.);
* the lead field that will be filled.

It is also possible to configure additional options according to the field type and specify whether it will be required on submission.

<figure><img src="/files/3149623f83b925ed2712b7825b918977a2c044a8" alt=""><figcaption><p><em>Form Fields.</em></p></figcaption></figure>

## Form Actions

You can define which actions will be executed for the lead, such as: creating opportunities in a CRM pipeline, generating tasks, changing permissions or assignees, sending WhatsApp messages, among others.

If you want these actions to be executed only once per lead, even on repeated form submissions, check the option **“Execute actions only once per lead?”** such as **Yes**.

<figure><img src="/files/7e7f16296d04494a9a53d766c7608166ac1a1090" alt=""><figcaption><p><em>Form Actions.</em></p></figcaption></figure>

## Saving and publishing changes

After modifying the settings, return to the **Preview** section and click **Save Changes** tab to record the changes.

Remember: saving the landing page **does not** automatically updates the published version. For customers to see the changes, you must click **Publish Version** on the landing page edit page. Always check which version is currently published.

<figure><img src="/files/a779d3ddf8226e06ffce2f952cd5c76fea66f819" alt=""><figcaption><p><em>Saving changes.</em></p></figcaption></figure>

<figure><img src="/files/b98c7894a5d54ca223e144eec633ecb0f9c9f6a5" alt=""><figcaption><p><em>Landing page edit page.</em></p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sprinthub.com/en/topics/artificial-intelligence/ai-landing-pages/ai-landing-pages-configuring-forms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
