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

# HubSpot sequences

Use **HubSpot Enroll Sequence** after a HubSpot contact has been matched or created.

## Prepare the connection

Connect [HubSpot](/integrations/hubspot.md) with access to sequence enrollment and owner information. Your HubSpot account and sender must be entitled to use sequences and have a connected inbox.

Review the current HubSpot plan and API requirements in your account before publishing. Reauthorization may be needed when the connection lacks sequence scopes.

## Configure the step

1. Select a **Contact** output from an earlier HubSpot step.
2. Choose the **Sender**: a HubSpot owner, a mapped Distro member or an earlier routing assignee.
3. Enter the numeric **Sequence ID** from HubSpot.
4. Connect the step only to the audience that should receive the sequence.

Use the contact object returned by the earlier step, rather than substituting a raw email address. The contact belongs to a particular authorized connection.

## Check enrollment

Inspect Enrolled or Already enrolled and the returned contact, sequence and sender details. Verify one controlled live enrollment in HubSpot.

If enrollment fails, check sequence scopes, sender inbox and entitlement, owner mapping and whether the earlier contact came from the current connection.

See [Connected identities](/settings/identities.md) and [No-show follow-up](/guides/no-show-follow-up.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/integrations/hubspot-sequences.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.