When Receiving WeChat Message Event Push
During interactions between WeChat users and official accounts, certain user actions trigger the WeChat server to push events to the server address configured by the developer in the Developer Center, enabling the developer to receive this information. Currently supported message and event pushes on the WeChat Official Account Platform include:
- Official Account: Standard Messages and Event Pushes
- Mini Program: Customer Service Messages and Events and Delivery Information Management Service Message Push
You can configure the workflow to trigger upon receiving a WeChat message event push and use the received information to process your business data.
Configuration Item Description
Enabled
Whether this trigger method is enabled. If disabled, it cannot receive WeChat Work message event push and trigger the workflow anymore.
Push URL
The interface URL for receiving WeChat messages and events. This URL must be configured in the Official Account Management Backend:
- Mini Program: Go to "Development - Development Management - Message Push" settings
- Official Account: Go to "Settings and Development - Basic Configuration - Server Configuration" settings
Message Encryption and Decryption Method
Message encryption and decryption type, defaulting to secure mode.
- Plaintext Mode: Does not use message body encryption and decryption, with a lower security level.
- Compatibility Mode: In this mode, plaintext and ciphertext coexist, facilitating debugging and maintenance for developers.
- Secure Mode (Recommended): In secure mode, message packets are pure ciphertext, requiring developers to perform encryption and decryption, with a high security level.
AppID
The appid of the Official Account or Mini Program.
Token
The Token is used to generate signatures and can be manually entered or randomly generated. This Token will be compared with the Token contained in the interface URL to verify security. It must be configured in the server settings of the Official Account Management Backend, along with the push URL.
EncodingAESKey
The EncodingAESKey can be manually entered or randomly generated, and will be used as the encryption and decryption key for message bodies. It must be configured in the server settings of the Official Account Management Backend, along with the push URL.
Usage Example
Refer to Tutorial: Setting Up a Workflow for Processing WeChat Message Push