> 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/guides/marketing/marketing-center/canva.md).

# Canva

Design your marketing in Canva, then send it directly into Rechat’s Marketing Center as a reusable marketing asset.

<div data-full-width="true"><figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2FreoPkjGV6Uejp6IYLckg%2F1.png?alt=media&amp;token=12c662cc-850c-41e3-9dd1-782cd93ba18a" alt=""><figcaption></figcaption></figure></div>

### Overview:

* [Rechat + Canva: Getting Started](/guides/marketing/marketing-center/canva/getting-started.md)
* [Design with Rechat Data in Canva](/guides/marketing/marketing-center/canva/design-with-rechat-data-in-canva.md)
* [Send Emails from Canva Using Rechat](/guides/marketing/marketing-center/canva/send-emails-directly-in-canva-using-rechat-email-sender.md)

This is perfect for:

* Emails
* Social posts and stories
* Flyers
* Just Listed/Just Sold graphics
* Agent branding pieces
* Custom creative that goes beyond standard templates

Once connected, Canva allows you to insert live property and agent data from Rechat directly into your design.


---

# 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/guides/marketing/marketing-center/canva.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.