The NotifyMessage component primarily provides functionality for processing event message notifications.
Feature description
Action | Description | Scenarios |
notifyByMessageCenter | Message Center event notification, with message type "Security Message - Cloud Security Information Notification". | Provides notifications for three scenarios: security event generation, security alert generation, and security event updates. The notification method uses the notification settings configured in Alibaba Cloud Message Center. |
notifyByCustom | Custom event notification. | Custom message sending, supporting email and DingTalk group. |
Configuration example
This topic provides parameter configuration examples for each action of the NotifyMessage component. You can import them as test playbooks. Through the visualization flow editor, you can more intuitively understand and test the configuration parameters of each action, easily mastering the functional logic and usage of the component. For the procedure, see Playbook import.
First save the example data as a JSON file.
Resource instance configuration
To use the NotifyMessage log component, you need to first set up email-related information. Follow these steps:
Click the component, and in the Basic Information Configuration tab, click Instance Configuration.
On the Resource Instance Configuration page, click the Add button. Complete the configuration as follows:
Parameter | Description |
assetname | You can customize the resource name according to your business needs. |
emailSendServer | Email sending server, optional.
|
emailUsername | Sender email address. Important
|
emailPassword | Sender email password. Important If authorization verification is enabled, this should be the authorization code. Authorization codes have expiration times. Be sure to replace with a new authorization code before expiration, otherwise email sending will fail due to authentication failure. |
notifyByMessageCenter
Message Center event notification, with message type "Security Message - Security Center Notification".
Parameter description
Parameter | Description |
Notification method | Optional, supports multiple selections.
For example: If the component is set to internal message and email, and the Message Center is set to email and robot, then the actual notification method will be email. |
Notification template | Currently supports three templates: event generation, alert generation, and event update. Note The notification template contains variable parameters that need to be configured and will be replaced with actual values when sent. |
Parameters setting | Configure actual values according to the variables set in the notification template. Supports setting constants or output parameters from preceding nodes, such as ${event._tenant_id}. |
NotifyByCustom action
Custom message sending, supporting email and DingTalk group
Email-related parameters
Parameter | Description |
Sender | Sender email, needs to be configured in the resource instance. |
Recipient | Recipient email. |
Subject | Email subject. |
Body | Email body. |
DingTalk-related parameters
Parameter | Description |
Webhook | The Webhook address to send to, which can be managed in the Message Center. |
Message template | The template for the message. |