> 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/platform-features/review-partner-applications/automate-partner-application-processing/set-up-a-workflows-reject-message.md).
# 设置工作流拒绝消息
参加 PXA 课程
您可以通过设置在其中配置的拒绝消息，拒绝合作伙伴对您项目的申请，设置方式如下： [工作流](/brand/zh/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/create-workflows-to-automatically-process-partner-applications.md)。该消息可帮助合作伙伴了解其申请被拒绝的原因、如何纠正问题，以及是否可以重新申请。
#### 设置工作流拒绝消息
1. 在左侧导航菜单中，选择  **\[Engage] → 合作伙伴 → 自动化 →** [工作流](https://app.impact.com/secure/advertiser/engage/fr/ps-bar-ui.ihtml).
2. 选择 **创建工作流** 位于屏幕右上角。
* 或者，找到您要更新的现有工作流，将鼠标悬停在其上，然后选择 **编辑**.
* 填写必填字段。请参阅 [工作流表单参考](/brand/zh/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/create-workflows-to-automatically-process-partner-applications.md#create-a-workflow-0-0) 以获取更多指导。
3. 在……中 *动作类型* 部分，使用  **\[下拉菜单]** 选择 **处理申请** 和 **拒绝**.
* 会出现一个消息框，您可以在其中输入自定义拒绝消息，并将其发送给合作伙伴。
* 请注意字符限制为 255 个。
4. 在完成工作流构建后，选择 **创建** 或 **保存**.
#### 更新项目特定的拒绝邮件
如果您使用自定义的项目特定拒绝邮件，则需要更新邮件正文以包含 `{rejectReason}` 令牌。这将确保您的自定义工作流拒绝消息包含在拒绝邮件中。
1. 从顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在右侧的 *品牌设置*下，选择 **系统邮件和 UI 消息**.
3. 前往 *拒绝邮件* 字段，并选择  **\[编辑]**.
4. 选择  **\[单选按钮]** **发送项目特定的拒绝邮件**.
5. 在……中 *主题* 字段，输入该邮件的自定义主题。
6. 在……中 *HTML 邮件正文* 字段，输入包含任何相关 HTML 代码的自定义邮件消息。
* 您可以在文本中添加特殊标签，这些标签会在生成邮件时被动态替换。
* 设置拒绝消息时，请务必包含标签 **`{rejectReason}`**.
7. 选择 **保存**.
示例邮件
{% hint style="info" %}
**注意：** 其他系统生成的拒绝原因也可能出现在拒绝邮件中。这些原因示例包括被 Impact AI 拒绝、被暂停，或被列入封禁名单。
{% endhint %}
---
# 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/platform-features/review-partner-applications/automate-partner-application-processing/set-up-a-workflows-reject-message.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.
.png?alt=media&token=4c2ab257-156a-4a38-a320-ca8fc4c3217d)
