Overview
This node acts as a trigger for workflows based on events occurring in the MsgCore messaging platform. It listens for specific message-related events such as receiving messages, sending messages successfully or failing to send, button clicks, and reactions added or removed from messages within a specified MsgCore project.
Common scenarios where this node is beneficial include:
- Automating responses or processing when new messages arrive.
- Tracking message delivery status to update logs or notify users.
- Reacting to user interactions like button clicks or reactions to messages.
- Integrating MsgCore messaging events into broader automation workflows.
For example, you could use this node to start a workflow that sends an alert whenever a message fails to send or to log every reaction added to messages in a project.
Properties
| Name | Meaning |
|---|---|
| Project ID | The MsgCore project ID to monitor for messages. |
| Events | The events to subscribe to. Options include: - Message Received - Message Sent - Message Failed - Button Clicked - Reaction Added - Reaction Removed |
| Webhook Name | Name to identify this webhook in the MsgCore dashboard. |
Output
The node outputs JSON data representing the event payload received from MsgCore. This includes detailed information about the triggered event, such as message content, event type, timestamps, and any associated metadata depending on the event type.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the MsgCore API.
- Needs n8n to be accessible via a public URL (cannot run on localhost without tunneling) because MsgCore must call back to the webhook URL.
- Uses MsgCore's REST API to create, check, and delete webhooks dynamically.
Troubleshooting
- Webhook creation failure: If the webhook cannot be created, ensure the provided Project ID is correct and the API key has sufficient permissions. Also, verify that the webhook URL is publicly accessible and not localhost.
- Invalid webhook signature error: This occurs if the incoming webhook request does not have a valid signature header or timestamp, or if the signature verification fails. Check that the webhook secret is correctly stored and that MsgCore is sending requests properly.
- Missing Project ID: The node requires a Project ID; missing this will cause errors.
- 404 errors on webhook check/delete: These indicate the webhook no longer exists on MsgCore and the node clears its stored webhook data accordingly.
Links and References
- MsgCore API Documentation (hypothetical link)
- n8n Webhook documentation: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/