> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/message/email/content-and-media/how-to-import-an-email-created-in-figma.md).

# How to import an email created in Figma?

Figma is a popular content creation solution, that can be used by marketing team to create emails. See how to leverage them in Batch.

### Create emails in Figma

Marketing teams can compose messages in Figma while reusing their content library and brand designs. Using Figma as the central place for content composition centralizes all assets, wherever they are used.

### Use a plugin to export the HTML

Figma exports to Customer Engagement Platforms and Email Service Providers through plugins. Several options exist, such as Emailify, Email Love, and Hypematic. Use one to generate email-ready HTML from your design.

### Upload the HTML into Batch

In Batch, go to **Campaigns > New campaign > Email message**, open the **Message** section, and select **Upload your ready-to-use HTML template** or **Open the code editor \</>** to add the exported HTML.

For the full import steps, see [how to upload your email templates](https://doc.batch.com/guides-and-best-practices/message/email/templates-and-modules-management/how-to-upload-your-email-templates).


---

# 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://doc.batch.com/guides-and-best-practices/message/email/content-and-media/how-to-import-an-email-created-in-figma.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.