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 other system events.
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 in Mindz. This identifies the webhook configuration. |
| Topics | The list of event types to listen for. Multiple events can be selected. Examples include "Account Accepted", "Course Created", "Payment Completed", "User Login", etc. Selecting "*" means all topics (though it is internally treated as empty). |
| Additional Fields | Optional extra settings for the webhook: - Active: Whether the webhook is active (true/false). - OAuth2 Application ID: Numeric ID of the OAuth2 app 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 object with all details sent by Mindz for the triggered topic.
If the incoming webhook event's topic matches one of the selected topics, the node returns the event data as an array with a single JSON object. If the topic does not match, no output is produced.
No binary data output is involved.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for Mindz.
- The node uses a secret generated from credential URLs to verify webhook signatures for security.
- Requires network access to receive HTTP POST requests at the configured webhook URL.
- Uses internal utility functions to make authenticated API requests to Mindz for webhook management (create, check existence, delete).
Troubleshooting
- Invalid signature error (HTTP 403): Occurs if the webhook request signature does not match the expected HMAC hash. Ensure the credentials are correctly set up and the webhook secret is consistent between Mindz and n8n.
- Webhook creation failure: Could happen if the API credentials are invalid or lack permissions. Verify the OAuth2 token and application ID.
- No trigger firing: Confirm that the selected topics match the actual events being sent by Mindz and that the webhook URL is correctly registered.
- Multiple user/course restrictions: When restricting by user or course IDs, ensure IDs are comma-separated without spaces and correspond to valid entities in Mindz.
Links and References
- Mindz API documentation (for webhook event types and payloads) — Mindz API Docs (replace with actual URL)
- n8n OAuth2 credential setup guide — n8n OAuth2 Docs
- General webhook security best practices — Webhook Security