> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/integrations/outreach-integration.md).

# Outreach integration

Guideflow can be accessed directly in Outreach, so you can attach interactive demos to your email sequence templates. Embed a guideflow using the Guideflow widget at the bottom of the template builder.

This integration keeps your demos inside your outbound workflow, helping your team engage prospects faster and more effectively.

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/zkj6q01uep>" %}

### How to use Guideflow with Outreach

To add a guideflow to your Outreach templates, follow these steps:

* In Outreach, open the email template you want to use.
* Select the spot where you want to embed the guideflow.
* Open the Guideflow widget at the bottom of the template builder.
* Select the guideflow you want to use in Outreach.
* Choose from the following options:
  * Share link + GIF
  * Share custom link
  * Share link
* Save the template.

Your guideflow now exports as a GIF and pastes into your Outreach email template. The GIF is hyperlinked with the guideflow's URL, so recipients can access the demo in one click.

{% hint style="info" %}
**Note:** Your guideflows must be public to appear in the widget. Set each guideflow to be public before you add it to a template.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guideflow.com/help/integrations/outreach-integration.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 `automate deployments from our CI pipeline` 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.