Message Push System

Imagine the joy of receiving a notification on your phone as soon as a user places an order.

This is a powerful message push plugin that supports multiple push channels and can monitor various events in the system in real-time, such as User Order, User Registration, User Login, etc., and push notifications through different channels like DingTalk, WeChat, etc.

• Demo URL: https://bs.woocl.com
• Admin URL: https://bs.woocl.com/admin
• Admin Account: [email protected]
• Password: [email protected]

Effects:

When configured with DingTalk, the phone will receive notifications when a user places an order: 

When configured with WxPusher, the phone will receive notifications when a user logs in: 

Interface Screenshot:

Features

• Supports multiple push channels:
  • HTTP Webhook
  • WxPusher Push
  • DingTalk Robot
• Flexible event triggering mechanism
• Sensitive data filtering
• Supports multiple languages (Simplified Chinese, Traditional Chinese, English)
• Real-time testing function

Installation Requirements

• BeikeShop v1.5.0 or higher
• PHP 7.4 or higher

Installation Steps

1. Download the plugin zip package
2. In the BeikeShop admin interface, go to "Plugin Management"
3. Click "Upload Plugin" and select the downloaded zip package
4. After installation, click "Enable" to use

Configuration Instructions

Basic Configuration

1. In the admin interface, go to "Settings" -> "Message Push System":
2. Click the "Add Message Push" button
3. Fill in the basic information:
   • Name: Specify a name for this push configuration
   • Message Channel: Select the push method
   • Trigger Event: Select the system event to be pushed
   • Sensitive Data Filtering: Enable to automatically desensitize sensitive information

Channel Configuration

HTTP Webhook

• Webhook URL: The URL address to receive messages
• Request Method: Supports POST, GET

WxPusher Push

1. Register a WxPusher account
2. Create an application to get AppToken
3. Follow the WxPusher official account in WeChat to get UID
4. Configuration:
   • AppToken: The application's Token
   • UID: The user ID to receive messages

DingTalk Robot

1. Add a custom robot in the DingTalk group
2. Configure security settings (recommended to use IP address range)
3. Get the access_token from the Webhook address
4. Configuration:
   • Token: The robot's access Token

Trigger Event Description

Sensitive Data Processing

When sensitive data filtering is enabled, the system will automatically desensitize the following types of data:

• Email address: Shows the first 3 characters and the domain, e.g., exa***@example.com
• Phone number: Shows the first 3 digits and the last 4 digits, e.g., 138****8000
• Address information: Retains province, city, and district information, with detailed addresses replaced by *
• Password information: Retains the first and last character, e.g., c***6

Testing Function

Each push configuration provides a testing function, which allows you to:

1. Find the configuration you want to test in the list
2. Click the "Test" button
3. Confirm to send a test message
4. Check whether the target channel receives the test message

FAQ

1. No messages received after saving the configuration?

   • Check if the channel configuration is correct
   • Confirm if the trigger event has occurred
   • Check the system logs for detailed error information

2. DingTalk robot message sending failed?

   • Check if the Token is correct
   • Confirm if the IP address is in the whitelist
   • Check the message sending frequency limit of the DingTalk robot

Notes

This plugin relies on the message push functionalities of DingTalk, WxPusher, and other projects. If there are adjustments in these projects' functionalities (such as interface changes, changes in message push rules, or discontinuation of support for certain push protocols) or other unforeseen circumstances (including but not limited to these projects ceasing operations or experiencing technical failures), it may cause the message push functionality of this plugin to not work properly. In such cases, we will attempt to adjust the plugin within a reasonable time after becoming aware of the relevant situation to restore the push functionality, but we cannot guarantee that the functionality can be fully restored in a timely manner or that the adjusted effects will fully meet expectations.

During the use of the plugin, users should closely monitor the official notifications of related projects like DingTalk and WxPusher. If push anomalies are found, please first refer to the update information of these official projects to determine whether it is related to the plugin's dependencies. At the same time, it is recommended that users take appropriate emergency measures when using this plugin in important business scenarios, such as preparing alternative notification methods, to avoid serious losses caused by message push failures.

Disclaimer

We do not assume any direct or indirect responsibility for the inability of this plugin to push messages as expected due to external factors mentioned above, including but not limited to business interruption losses, opportunity losses, etc. The development of this plugin aims to provide convenient functions based on existing open-source projects and legal technical frameworks, but given the complexity and uncertainty of the external technical environment, it is impossible to completely eliminate the potential risks associated with such dependencies. Users assume all related risks and responsibilities when using this plugin and agree to all the contents of this disclaimer.

It is also important to note that when using the functionalities of these projects, users must comply with relevant service agreements, privacy policies, and other regulations.

Change Log

v1.0.1 (2024-12-25)

• Initial version release
• Supports HTTP Webhook, WxPusher, DingTalk robot channels
• Basic event triggering functionality
• Sensitive data filtering
• Supports multiple languages

v1.0.2 (2024-12-28)

• Adjusted the directory structure of the plugin package

TODO:

• WxPusher channel does not require configuration; users can scan the code to bind and use directly.