> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/email-experiences/import-an-advocate-email-template.md).
# 导入或导出 Advocate 邮件模板
如果您想在导入新邮件模板之前保存要替换的邮件，可以导入现有邮件模板并导出邮件模板。
#### 导入邮件模板
邮件编辑器可以接受任何 HTML 格式的邮件代码，您可以导入为您创建的任何基于 HTML 的邮件。
1. 从左侧导航菜单中，选择  **\[Engage] → 内容**.
2. 在……中 *电子邮件* 卡片中，选择 **编辑电子邮件** 以编辑现有模板。
3. 选择您想为其导入自定义邮件的邮件。
* 选择  **\[退出图标]** 以最小化侧边菜单。
4. 选择 **导入模板** 在水平工具栏中打开导入窗口。
5. 将您的脚本添加到 *导入模板* 窗口中。检查复制的代码是否准确且完整。
6. 选择 **导入** 以将自定义代码加载到邮件编辑器画布中。
7. 更新完成后，给自己发送一封测试邮件。
* 选择 **行动**  **\[下拉菜单]** 以给自己发送测试邮件。
8. 选择 **保存** 在屏幕右上角。
9. 如果您的项目正在运行，您必须 [发布您的项目草稿](/brand/zh/what-would-you-like-to-learn-about/advocate-program/getting-started-with-advocate/create-and-publish-a-program-draft-for-advocate.md) 以向参与者推出更改。
#### 导出邮件模板
1. 从左侧导航菜单中，选择  **\[Engage] → 内容**.
2. 在……中 *电子邮件* 卡片中，选择 **编辑电子邮件** 以编辑现有模板。
3. 选择您想为其导入自定义邮件的邮件。
* 选择  **\[退出图标]** 以最小化侧边菜单。
4. 选择 **导出邮件模板** 在水平工具栏中打开导入窗口。
5. 在以下位置查看代码： *导出模板* 窗口。
6. 选择 **复制 HTML** 以复制并粘贴 HTML。
---
# 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.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/email-experiences/import-an-advocate-email-template.md?ask=&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.
