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

# Routed leads to sequences

Add a routed lead to a sequence, cadence, campaign, or flow in your sales engagement tool.

A workflow picks the rep with **Assign from Queue** or **Apply Rulebook**, writes them to the CRM, then a sequencing step enrolls the lead in your tool. The sequence itself (emails, steps, schedule) runs in that tool.

## Supported tools

| Tool        | Step                            | Identifies the lead by                 | Sender                                                             |
| ----------- | ------------------------------- | -------------------------------------- | ------------------------------------------------------------------ |
| Apollo      | **Add to Apollo Sequence**      | Email                                  | The mailbox chosen on the step                                     |
| Outreach    | **Add to Outreach Sequence**    | Email                                  | The mailbox chosen on the step                                     |
| Salesloft   | **Add to Salesloft Cadence**    | Email                                  | The user chosen on the step, or the key's owner                    |
| Amplemarket | **Add to Amplemarket Sequence** | Email or LinkedIn URL                  | A mailbox email, or the sequence's senders                         |
| Smartlead   | **Add to Smartlead Campaign**   | Email                                  | The campaign's mailbox rotation                                    |
| Gong Engage | **Add to Gong Engage Flow**     | CRM record ID                          | **Sending user** email                                             |
| HubSpot     | **Enroll in HubSpot Sequence**  | A HubSpot contact from an earlier step | **Sender**: a HubSpot owner, a member, or the **Earlier assignee** |

{% hint style="info" %}
To send as the rep the workflow picked, use **Enroll in HubSpot Sequence** with the earlier assignee as **Sender**. Amplemarket and Gong Engage take a sender email you enter on the step, and Apollo, Outreach, and Salesloft send from the mailbox or user selected on the step.
{% endhint %}

A sequencing step appears in the step picker once its tool is connected under **Settings** › **Integrations**.

## Build it

1. **New form submission** on your `Download the guide` form.
2. **Match Salesforce Record** on `Lead` by email. On **Matched**, alert the owner's channel and stop, so existing people keep their owner.
3. On **Not matched**, **Assign from Queue** with `Outbound SDRs`, then **Create Salesforce Record** with the assignee as `OwnerId`.
4. Add the sequencing step with the form's email.

When the tool skips an enrollment, for example because the person is already in another sequence, the step reports it and the workflow continues.


---

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