> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/forms/lead-forms.md).

# Create a lead form

Build a branded form in Distro and share it as a hosted page or embed it on your website.

**Open Lead forms.** You need admin access and a workflow-enabled workspace to configure the routing journey.

## 1. Create and save the questions

Create a form, enter its name and page details, and add the questions you need.

Give fields stable keys and clear labels. Include email and the values your qualification or routing rules use. Choose suitable types and required settings.

Configure appearance and the completion message, then select **Save draft**.

The completion message is shown when the workflow finishes successfully without opening a scheduler or redirecting.

## 2. Build its workflow

Open **Workflows** and create or edit a workflow with **New form submission**.

Select this form. The trigger reads the saved questions. Add qualification, routing, and **Show Scheduler** as needed.

After changing questions, use **Refresh form connection** in the trigger, review affected mappings, and publish a compatible workflow version.

## 3. Select the published routing

Return to the form and choose **Change routing**.

Select the **Workflow** and **Published version**, then **Apply to draft**. Only versions that start with this form are available.

Save the form draft.

## 4. Publish the form

Choose **Preview saved draft** to review the saved form. Select **Publish saved draft** when it is ready.

The header shows the published form version. Unpublished changes stay in the draft.

Publishing the workflow first does not automatically switch an existing published form to the new version. Update its routing selection and publish the form again.

## 5. Share it

After publication, open **Share the published form**.

Copy **Hosted page** for a direct link. Copy **Website embed** for your website. The generated embed includes an iframe with `data-distro-lead-form` and the resize script.

```html
<iframe
  src="YOUR_PUBLISHED_FORM_URL"
  title="Request a demo"
  data-distro-lead-form
  style="width:100%;height:760px;border:0">
</iframe>
<script src="YOUR_DISTRO_ORIGIN/lead_forms_embed.js" defer></script>
```

Use your form's generated code and deployment origin.

## Review submissions

Open **Submissions** to inspect captured answers and the connected workflow outcome. Follow the run into Logs when routing or scheduling needs investigation.

Test a qualified lead, a disqualified lead, and a visitor who does not book. Use controlled details for tests that can send notifications or update your CRM.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/forms/lead-forms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.