> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/videos-in-email.md).

# Videos in Email

Videos in Emails

{% embed url="<https://rechatq.wistia.com/medias/bma40a973y>" %}

Rechat now allows members to upload MP4 video files directly into an email template in Marketing Center.&#x20;

1. Drag the Video block into your email template.
2. Select Your Gallery.&#x20;
3. Find and select Click here to Upload.&#x20;
4. Browse for and select the video you wish to upload from your computer.&#x20;

Rechat will generate a video GIF and insert it into your layout. When you’ve finished editing your template, select Continue in the upper-right corner of your screen.


---

# 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://help.rechat.com/whats-new/videos-in-email.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.
