> 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/outreach.md). # Outreach Connect Outreach to start a sales sequence for an eligible prospect. ## Connect An admin opens **Settings → Integrations → Outreach** and authorizes Distro's Outreach application. The deployment must have Outreach OAuth configured; ask Distro support if connection setup is unavailable. The authorization covers the prospect, sequence, sequence-state and mailbox operations used by the workflow. Connecting does not start a sequence. ## Configure Start Sequence Choose the sequence and sending mailbox. Map the prospect email and supported person fields. Check member Outreach identities when the workflow depends on the assigned sender. Place enrollment after your qualification, ownership and suppression decisions. A connected mailbox is an operational sender, not the prospect's address. ## Verify Inspect the returned prospect ID and sequence-state ID, then confirm a controlled live enrollment in Outreach. If the resource picker is empty, check OAuth permissions, the connected Outreach organization and access to the sequence and mailbox. If enrollment is skipped or already present, inspect that status before retrying. A simulation does not contact Outreach or prove that a mailbox can send. See [Sequence enrollment outcomes](/workflows/sequence-outcomes.md) for success, skipped and failure handling. --- # 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/outreach.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.