Overview
This node acts as a trigger for workflows based on events from the Mindz platform. It listens to specific webhook events defined by the user and starts the workflow when those events occur. This is useful for automating processes that depend on real-time updates from Mindz, such as reacting to user account changes, course activities, payments, subscriptions, and more.
Practical examples include:
- Starting a workflow when a new user is created or deleted.
- Triggering actions when a payment is completed or refunded.
- Automating notifications or data processing when courses or community topics are updated.
- Responding to subscription status changes like cancellations or suspensions.
Properties
| Name | Meaning |
|---|---|
| Webhook Name | The name assigned to the webhook for identification purposes. |
| Topics | The list of event types to listen for. Multiple can be selected. Events include various triggers such as "Account Accepted", "Course Created", "Payment Completed", "User Login", and many others representing different Mindz platform activities. |
| Additional Fields | Optional extra settings: • Active: Whether the webhook is active (true/false). • OAuth2 Application ID: Numeric ID of the OAuth2 application to use. • Restrict to User IDs: Comma-separated user IDs to limit the trigger. • Restrict to Course IDs: Comma-separated course IDs to limit the trigger. |
Output
The node outputs JSON data representing the event payload received from the Mindz webhook. The output contains the full event details as provided by Mindz, including the topic and associated data fields relevant to the triggered event.
If the incoming webhook's event topic matches one of the selected topics, the node returns the event data in the json output field, allowing subsequent nodes to process it.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials to interact with the Mindz API.
- The node uses a secret generated from credential URLs to verify webhook signatures for security.
- The node depends on the Mindz platform's webhook infrastructure to send event notifications.
Troubleshooting
- Invalid signature error (HTTP 403): This occurs if the webhook request's signature does not match the expected HMAC hash. Ensure that the credentials are correctly set up and that the webhook URL has not changed.
- Webhook creation failure: If the node cannot create or find the webhook on Mindz, check the API credentials and network connectivity.
- No events triggering: Verify that the correct topics are selected and that the Mindz platform is sending events to the webhook URL.
- Restricted triggers not firing: If using user or course ID restrictions, ensure the IDs are correctly formatted and correspond to existing entities.
Links and References
- Mindz Platform Documentation (replace with actual URL)
- OAuth2 Authentication setup guides
- n8n Webhook Trigger Node documentation