> ## Documentation Index
> Fetch the complete documentation index at: https://help.dingtalk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Message Notification Templates

> Learn how to configure message notification templates on the YiDA workbench, including creating templates, setting template types (such as plain messages or DingTalk to-dos), and applying them. This article also covers built-in variable formats to help you customize message content.

Message notification templates send DingTalk message notifications or to-do tasks to specified users when a form workflow reaches a specific step, based on the preconfigured template. Refer to this article to learn how to configure message notification templates.

| Feature                       | Free plan     | Basic edition | Professional edition | Dedicated edition |
| ----------------------------- | ------------- | ------------- | -------------------- | ----------------- |
| Message notification template | Not supported | Supported     | Supported            | Supported         |

## Configure a Message Template

<Steps>
  <Step title="Step 1">
    Sign in to the [YiDA workbench](https://www.yidaapps.com/workPlatform) as an Admin.
  </Step>

  <Step title="Step 2">
    Click the platform management button in the upper-right corner to open the platform management page.
  </Step>
</Steps>

<Steps>
  <Step title="In the left-side menu, click Message notification templates" />

  <Step title="Click Create template, configure the template as described below, and then click Confirm to finish" />
</Steps>

<table>
  <tr>
    <td>Attribute</td>
    <td>Description</td>
  </tr>

  <tr>
    <td>Template name</td>
    <td>Enter a name for the message template.</td>
  </tr>

  <tr>
    <td>Admin</td>
    <td>The administrator of this message template. You can assign multiple administrators.</td>
  </tr>

  <tr>
    <td rowSpan={2}>Template type</td>
    <td>**Plain message**: Currently supports sending DingTalk message notifications only.<br /><ul><li>**Message title**: The title of the message notification. This title appears in both the Chats list and the chat list.</li><li>**Message content**: The main body of the pushed message. The message content supports configurable variables. Each variable is the ID of a form component, formatted as `$!{Field ID}`. When the message is sent, YiDA automatically replaces the variable with the value of the form component. For details, refer to [Built-in variable formats](/yida/platform-admin/fkfhud).</li></ul></td>
  </tr>

  <tr>
    <td>**DingTalk To-Do**: The DingTalk To-Do notification type is available only in the Basic edition and above. For details, refer to [Edition differences](https://www.yidaapps.com/pricing).<br /><ul><li>**Message title**: The title of the to-do task.</li><li>**Message content**: The details of the to-do task. Supports configurable variables. Each variable is the ID of a form component, formatted as `$!{Field ID}`. When the message is sent, YiDA automatically replaces the variable with the value of the form component. For details, refer to [Built-in variable formats](/yida/platform-admin/fkfhud).</li></ul><br />**Note**: Each organization can create up to 200 DingTalk To-Do templates. Exceeding this limit triggers an error.</td>
  </tr>
</table>

## Use a Message Template

You can apply a message template in two ways:

* Method 1: Use it in the Message notifications step of a workflow form's workflow design. For details, refer to Message notifications step.
* Method 2: Use it in the form page settings. For details, refer to Form message notifications.

<Note>
  Regular forms do not currently support DingTalk To-Do message templates.
</Note>

## Built-In Variable Formats

The message content in a message template supports configurable variables. Each variable is the ID of a form component, formatted as `$!{Component ID}`. When the message is sent, YiDA automatically replaces the variable with the value of the form component.

| Variable                 | Field                          | Form | Workflow |
| ------------------------ | ------------------------------ | ---- | -------- |
| \$!\{formInstId}         | Instance ID                    | ✓    | ✓        |
| \$!\{formUuid}           | Form code                      | ✓    | ✓        |
| \$!\{formTitle}          | Form name                      | ✓    | ✓        |
| \$!\{formTitleEn}        | Form name in English           | ✓    | ✓        |
| \$!\{title}              | Form instance title            | ✓    | ✓        |
| \$!\{titleEn}            | Form instance title in English | ✓    | ✓        |
| \$!\{creator}            | Creator's employee ID          | ✓    | ✓        |
| \$!\{originator}         | Originator's employee ID       | ✓    | ✓        |
| \$!\{originatorName}     | Originator's name              | ✓    | ✓        |
| \$!\{originatorNameEn}   | Originator's name in English   | ✓    | ✓        |
| \$!\{serialNo}           | Serial number                  | ✓    | ✓        |
| \$!\{createTime}         | Created time                   | ✓    | ✓        |
| \$!\{modifiedTime}       | Modified time                  | ✓    | ✓        |
| \$!\{processInstStatus}  | Workflow instance status       | ✗    | ✓        |
| \$!\{approvedResult}     | Approval result                | ✗    | ✓        |
| \$!\{approvedResultCode} | Approval result code           | ✗    | ✓        |