> 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.md).

# Forms and website capture

Capture leads with Distro forms or forms already on your website.

Capture prospect details with a Distro lead form, connect a form you already use, or review forms detected by website tracking.

## Choose the route

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Lead forms</strong></td><td>Build a branded form, then share or embed it.</td><td><a href="/forms/lead-forms.md">Create a lead form</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FEQvWVFslhl70isnK7yCH%2Fdistro3-form.webp?alt=media">distro3-form.webp</a></td></tr><tr><td><strong>Existing forms</strong></td><td>Keep your website form and connect its confirmed submission.</td><td><a href="/forms/existing-forms.md">Connect an existing form</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2F1ISmHDTp6o54IcOa6MDE%2Fdistro3-link.webp?alt=media">distro3-link.webp</a></td></tr><tr><td><strong>Form SDK</strong></td><td>Connect a custom frontend or provider callback.</td><td><a href="/forms/sdk.md">Form SDK</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FPFXIrjam7bKgkiYYqgyt%2Fdistro3-api.webp?alt=media">distro3-api.webp</a></td></tr><tr><td><strong>Website tracking</strong></td><td>Track activity and review detected website forms.</td><td><a href="/forms/website-tracking.md">Website tracking</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FBEoplt233SPp8pp36XOz%2Fdistro3-tracker.webp?alt=media">distro3-tracker.webp</a></td></tr></tbody></table>

A form collects the answers. Its workflow decides what happens afterward: routing, scheduling, CRM actions, and follow-up.

## Two publications to check

A workflow has a published version. A form or external connection also has an active configuration that selects the workflow version.

When you change workflow routing, publish the workflow first, then deliberately update the form or connection to that version. Saving either draft alone does not change the live journey.

## Test the whole website flow

Check the original form destination, Distro submission, scheduler, booking, and workflow actions. A successful form preview or simulation does not prove the published website integration works.

Coming from a Form Router? Follow [Move a Form Router](/migrate/form-router.md).

## More guides

* [Capture HubSpot form submissions](/forms/hubspot.md)
* [Capture Marketo form submissions](/forms/marketo.md)
* [Capture Pardot and other embedded forms](/forms/pardot.md)
* [Review detected forms and field changes](/forms/review-detected.md)
* [Tracker consent and capture exclusions](/forms/privacy.md)
* [Tracker browser storage and attribution](/forms/storage.md)
* [Troubleshoot form capture and scheduling](/forms/troubleshooting.md)


---

# 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.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.