Mindz Trigger icon

Mindz Trigger

Starts the workflow on a Mindz event
Join our community

Overview

This node acts as a trigger that starts an n8n workflow when specific events occur in the Mindz platform. It listens for webhook events related to various topics such as user actions, course updates, payments, subscriptions, and more. When one of the selected event topics is received via a webhook, the node triggers the workflow with the event data.

Common scenarios where this node is beneficial include:

  • Automating follow-up actions when a user enrolls in a course or completes an exam.
  • Syncing external systems when payments are completed, refunded, or cancelled.
  • Managing notifications or workflows based on community activity like new topics or responses.
  • Reacting to subscription lifecycle events such as creation, suspension, or cancellation.

Practical example:

  • Trigger a workflow to send a welcome email when a new user is created.
  • Start a process to update CRM records when a payment is marked as completed.
  • Automatically archive or notify moderators when a community topic is deleted.

Properties

Name Meaning
Webhook Name The name assigned to the webhook. This identifies the webhook within the Mindz system.
Topics The list of event topics to listen for. Multiple can be selected. Examples include "Account Accepted", "Course Created", "Payment Completed", "User Login", etc. Selecting "*" means all topics (though internally it clears the list).
Additional Fields Optional extra settings:
• Active: Whether the webhook is active (boolean).
• OAuth2 Application ID: Numeric ID of the OAuth2 application to use.
• Restrict to User IDs: Comma-separated user IDs to limit triggering.
• Restrict to Course IDs: Comma-separated course IDs to limit triggering.

Output

The node outputs JSON data representing the event payload received from the Mindz webhook. The structure of the JSON corresponds directly to the event data sent by Mindz for the selected topic(s).

  • The output contains a single item per webhook call.
  • The json field includes all event details as provided by Mindz.
  • No binary data output is produced by this node.

Example output JSON snippet (simplified):

{
  "topic": "User/create",
  "data": {
    "userId": 123,
    "name": "John Doe",
    "email": "john@example.com"
  },
  "timestamp": "2024-06-01T12:00:00Z"
}

Dependencies

  • Requires an API authentication token configured via OAuth2 credentials to connect securely to the Mindz platform.
  • The node uses a cryptographic HMAC SHA256 signature verification to validate incoming webhook requests using a secret derived from credential URLs.
  • The webhook URL must be publicly accessible for Mindz to send events.
  • No additional external dependencies beyond the Mindz API and OAuth2 credentials.

Troubleshooting

  • Invalid signature error (HTTP 403): Occurs if the webhook request's signature does not match the expected HMAC hash. Ensure the correct OAuth2 credentials are set up and that the webhook URL has not changed.
  • Webhook not triggering: Verify that the webhook is active and that the selected topics match the events being sent by Mindz. Also confirm that any user or course ID restrictions are correctly configured.
  • No credentials returned: The node requires valid OAuth2 credentials; ensure these are properly configured in n8n.
  • Multiple topics selection: If "*" is selected, the node internally treats it as no filter (all topics). Make sure this behavior aligns with your intended use.

Links and References

Discussion