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

# Capture HubSpot form submissions

Use Distro's website tracker to receive supported HubSpot form submission callbacks while keeping the existing form on your site.

## Connect the form

1. Install the workspace tracker snippet on the same allowed site that hosts the HubSpot form.
2. Make a controlled form submission.
3. Open **Website Tracker → Forms** and inspect the detected HubSpot form and fields.
4. Review the mapping, especially email, name and qualification fields.
5. Connect a published workflow using the relevant external-form trigger.
6. Confirm a second submission starts the intended live run.

The integration listens for HubSpot's `hsFormCallback` → `onFormSubmitted` event and captures supported values. A HubSpot iframe is not the same as a plain HTML form whose DOM Distro can freely inspect.

## Keep the guest journey coherent

Check the HubSpot form's own success behavior alongside the Distro workflow outcome. An existing redirect can navigate away before the intended scheduling experience is visible.

Where a controlled workflow scheduling experience is needed, use the supported [Form SDK](/forms/sdk.md) submission path rather than assuming passive capture replaces every HubSpot redirect.

## Troubleshoot

Check tracker loading, allowed hostname, form callbacks, mapped email, review status and workflow activation. A HubSpot submission in HubSpot alone does not prove Distro received the callback.

The [HubSpot API connection](/integrations/hubspot.md) is separate; authorize it when the workflow needs matching, writes or sequence enrollment.


---

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