> 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/apollo-sequences.md). # Apollo sequences Use **Apollo Start Sequence** to enroll an eligible person from a workflow. ## Prepare Apollo Connect [Apollo](/integrations/apollo.md) with a **master API key** that can access sequences and mailboxes. Choose the sequence and email account in the step; a basic enrichment-only key may not be sufficient. Map the prospect email and supported person fields. Map the appropriate sender identity when using a member's provider context. ## Configure enrollment Choose the Sequence and Mailbox. Review the options for contacts active in other sequences and contacts who finished other sequences. Keep those options aligned with your team's contact policy. Turning them on can permit enrollment that you otherwise intended to skip. Place the step after qualification and ownership checks. For abandoned booking follow-up, use the Show Scheduler **Not booked** branch rather than enrolling every form submitter immediately. ## Check the outcome Inspect the returned status, contact ID and sequence ID. An already enrolled or skipped prospect is different from a failed provider request. Simulate first, then verify a controlled live enrollment in Apollo. Check the chosen mailbox and sequence, not only the existence of the contact. For a complete journey, see [Unbooked lead follow-up](/guides/unbooked-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/apollo-sequences.md?ask=&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.