DataWorks:AI Assistant in practice: Configure IM account mapping to accurately @ responsible persons and on-call staff

Step 1: Go to account mapping of the target channel

1. Log on to the DataWorks console and click AI Assistant Service in the left-side navigation pane.

2. In the instance list, find the target instance and click the instance name to go to the instance details page.

3. In the Channel Configuration area, find the target channel card (DingTalk, WeCom, or Lark / Lark), and configure the corresponding channel integration.

4. After you complete the channel configuration, click Account Mapping in the upper-right corner of the card.

Step 2: Add an account mapping

1. In the upper-left corner of the Account Mapping panel, click Add Mapping.

2. Configure the following parameters in the Add Mapping dialog box, and then click OK.

   Parameter	Required	Default value	Description
   Member	Yes	N/A	Search for and select the RAM user or role that corresponds to the responsible member. The drop-down list labels each entry as User or Role. After you select a member, the nickname, account name, and account ID are automatically populated and used as the primary key of the mapping.
   Phone number	No	Empty	The phone number registered for this member in the current channel. This number is used as a generic identifier for @-mentioning by phone number. The list always displays the number in masked format. When you edit the mapping, keeping the masked value retains the original number. To change the number, enter the complete new number.
   Channel @ identifier	No	Empty	The platform identity of this member in the current channel. The field name varies by channel: For DingTalk, the field is DingTalk User ID, which you can obtain from the personal details page. For WeCom, the field is WeCom Account. A WeCom administrator can obtain it from the user details page in Contacts. For Feishu / Lark, the field is Feishu Open ID / User ID. You can enter an Open ID or User ID that starts with ou_. For how to obtain the ID, see How to obtain user IDs.
   Enable mapping	No	Enabled	Enabled by default. When disabled, this mapping no longer takes effect, which lets you temporarily suspend @-mentions for a member without deleting the record.

3. After you save the mapping, the list refreshes and the member appears. If the instance also uses other channels, go back to Channel Configuration and repeat the preceding steps for the same member on the other channel cards.

Step 3: Send a test message for verification

You can send a single test message to verify whether the account mapping configuration for a specific member takes effect.

1. Start the test

   In the Account Mapping list, find the target member and click the **Test** button in the Actions column.

   Tip: If the mapping information (@ identifier or phone number) for this member on the current channel is empty, the system blocks the test and prompts you to complete the information first.

2. Configure and send

   In the dialog box that appears, paste the Webhook URL of the target group bot, and then click Submit.

   Important

   • The smart bots of WeCom and Lark do not support Webhooks. You can add a Webhook bot to a group chat to test @-mention message delivery.

   • If the same bot is used in multiple groups, its Webhook URL differs for each group. When testing a push, make sure that you select the correct group chat URL to avoid sending the message to the wrong group.

   • The system sends an actual test message to the group, which is visible to all group members. To avoid disruption, notify the relevant group members in advance.

3. Verify the result

   Go to the corresponding IM group chat and check the test message:

   • Success: The member is successfully @-mentioned (the name appears as a clickable blue link).

   • Failure: The member name appears as plain text and cannot be clicked.

4. Troubleshooting

   If the test fails (the member is not successfully @-mentioned), check the following configurations one by one and test again after you fix any issues:

   • Enable status: Make sure that the Enable Mapping toggle for the member is turned on in the mapping list.

   • Identity information: Make sure that at least one of the Channel @ Identifier or Phone Number fields is filled in for the member on the channel being tested.

   • Identifier accuracy: Double-check that the @ identifier you entered (such as a DingTalk user ID) is completely correct, with no typos or extra spaces.

   • Webhook validity: Confirm that the Webhook URL used for testing is correct and that the bot has been properly added to the target group chat.

1. Responsible members

This is the most critical notification target. The system determines the specific responsible member through intelligent analysis.

• Dynamic responsible members (default behavior)

  • Logic: During each inspection cycle, AI Assistant analyzes the specific resources that have issues (such as a table or a task) in real time and automatically @-mentions the owner of that resource.

  • Advantages: No pre-registration is required. The process is intelligent, automated, and precisely targeted. If no exception is found in the current cycle, no one is disturbed.

  • Applicable scenario: The majority of routine alert scenarios.

• Fixed responsible members (fallback)

  • Logic: You can specify one or more fixed members in an inspection task through AI Assistant. Regardless of which inspection cycle or which resource has an issue, the system @-mentions these fixed members.

  • Applicable scenario: Serves as the ultimate fallback for alerts, ensuring that someone always receives the notification — for example, the team leader or the group owner.

2. On-duty members

When you configure a scheduled task, you can instruct AI Assistant to use shift schedules as the notification target. The system then introduces the shift rotation mechanism.

• Logic: AI Assistant automatically reads and associates the native shift schedules that you maintain in DataWorks Operation Center, and retrieves the primary on-duty member and backup on-duty member for the current day to @-mention them.

• Advantage: The notification target rotates automatically with the shift schedule, eliminating the need for repetitive configuration on the AI Assistant side.

• Display: In the alert report, the responsible member and the on-duty member are listed on separate lines with clear labels.

3. Creator

When the monitored resource object has no responsible member, DataWorks designates the creator as the notification target as a fallback strategy. The following example uses Flink:

• For Flink job monitoring: When no responsible member mapping is registered for a job, AI Assistant automatically queries the creator of the job to @-mention, and the report is annotated with "(by creator)".

• Priority: ① Responsible member mapping > ② Job creator > ③ Default fallback member. You must configure the relevant stakeholders in account mapping to ensure that AI Assistant Service can accurately @-mention the correct person.

• When the creator cannot be retrieved (for example, due to lack of read permission on the job), the notification falls back to the default fallback member or plain-text mention, annotated with "creator not found".

  Note: Flink monitoring and the automatic @-mention by creator capability require that you first enable Flink Expert Suite.

Platform-specific notes

DingTalk

• You must provide the Webhook URL of the group to enable @-mention notifications.

• When a bot is added to different groups, each group generates its own independent Webhook URL.

• When you configure a scheduled task, you must manually enter the Webhook URL of the target group. The system cannot obtain it automatically.

Lark

• The app bot can send @-mention messages to a specified group by group ID without a Webhook URL.

• After you specify a group, the bot can directly @-mention group members and trigger notifications.

WeCom

WeCom has two types of bots with completely different capabilities:

• Chat bot: Used for interactive conversations and supports two connection modes.

  • Long connection mode: Can proactively send @-mention messages to a specified group and trigger notifications without a Webhook URL.

  • URL callback mode: Cannot proactively send @-mention messages to a specified group.

  • Neither mode has Webhook capabilities.

• Message push bot (Webhook-dedicated): Pushes messages in one direction through a Webhook URL and supports @-mentions.

  • If you need to send @-mention notifications through a Webhook, create this type of bot separately in the group.

Configuration recommendations

• Q: Does a member need to be configured in every channel?

  A: Yes. Account mapping is maintained per channel. Enter a DingTalk user ID for the DingTalk channel, an Open ID or phone number for the Lark channel, and a WeCom account for the WeCom channel.

• Q: If I change a member's phone number, does the mapping update automatically?

  A: No. Both the phone number and the channel @ identifier must be manually registered in the mapping. If a member's contact information changes, you must manually edit the corresponding mapping. To reduce this maintenance overhead, we recommend that you fill in the channel @ identifier first.