> 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/sharing-guideflow/share-via-gmail-plugin.md).

# Share via Gmail Plugin

With the Guideflow Gmail Plugin, you can send demo GIFs or links without leaving your Gmail inbox.

{% hint style="info" %}
⚠️ **Note:** The Guideflow plugin will only appear in Gmail after you've installed the Guideflow extension in your Chrome browser.
{% endhint %}

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

### How It Works:

* Open your Gmail and start composing your email as you normally would.
* Navigate & click on the **Guideflow plugin** in the compose email toolbar.&#x20;
* Choose the demo you’d like to send from your library of interactive demos.
* Select your sharing format, either a GIF with link or link only.
* The demo is automatically added to your email and ready to be sent!

It’s a perfect fit for Sales and Customer Success teams, giving them a faster, easier way to share leave-behind sales demos or product training demos as a follow-up immediately after meeting.


---

# 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/sharing-guideflow/share-via-gmail-plugin.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.