Overview
This node acts as a trigger for workflows based on events occurring in the Max messenger platform. It listens for various types of Max messenger events such as messages received, message edits, user joins or leaves, bot interactions, and more. When one of the selected events occurs, the node activates the workflow, allowing automation to respond immediately.
Common scenarios include:
- Automating responses when a new message is received in a direct chat or group.
- Tracking when users join or leave chats to update membership records.
- Reacting to button clicks within messages to handle interactive elements.
- Monitoring changes like chat title updates or message deletions for audit or notification purposes.
Practical example:
- A customer support workflow that triggers whenever a user sends a direct message, enabling an automated reply or ticket creation.
- A moderation workflow that triggers when a user is removed from a chat, logging the event or notifying admins.
Properties
| Name | Meaning |
|---|---|
| Events | The Max messenger events that should trigger the workflow. Options include: |
| - Bot Added To Chat | |
| - Bot Removed From Chat | |
| - Bot Started | |
| - Button Clicked | |
| - Chat Title Changed | |
| - Message Deleted | |
| - Message Edited | |
| - Message Received (Chat) | |
| - Message Received (Direct) | |
| - User Joined Chat | |
| - User Left Chat | |
| Additional Fields | Optional restrictions to limit triggering: |
| - Restrict to Chat IDs | Comma-separated list of chat IDs to restrict the trigger to specific chats only. |
| - Restrict to User IDs | Comma-separated list of user IDs to restrict the trigger to specific users only. |
Output
The node outputs JSON data representing the event payload received from Max messenger. This includes detailed information about the event type, involved users, messages, chat details, and any other relevant metadata depending on the event triggered.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Max messenger platform.
- Uses internal webhook management and event processing classes to handle webhook registration and incoming event parsing.
- The node must be configured with a publicly accessible webhook URL to receive events from Max messenger.
Troubleshooting
- Webhook not triggering: Ensure the webhook URL is correctly registered in Max messenger and publicly accessible. Check that the correct events are selected.
- Authentication errors: Verify that the provided API key credential is valid and has necessary permissions.
- Event filtering issues: If restricting by chat or user IDs, confirm the IDs are accurate and formatted correctly (comma-separated).
- Unexpected payloads: The node expects Max messenger event formats; if the platform changes its API, the node may require updates.
Links and References
- Max Messenger official API documentation (refer to the platform's developer resources for webhook setup and event types)
- n8n webhook and trigger node development guides for understanding webhook lifecycle and event handling