Overview
This node acts as a trigger for workflows based on events occurring in the Eduzz platform. It listens for specific Eduzz events via webhooks and starts the workflow when those events happen. This is useful for automating processes that depend on real-time updates from Eduzz, such as order completions, subscription changes, or payment notifications.
Practical examples include:
- Automatically processing orders when a purchase event occurs.
- Sending notifications or updating CRM systems when a subscription event happens.
- Logging or analyzing sales data triggered by payment events.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "Access Token" to connect securely to Eduzz API. |
| Test Webhooks will be automatically fired with sample data. | Informational notice indicating that test webhooks are sent automatically with sample data. |
| Application Name or ID | Select or specify the Eduzz application (by name or ID) to monitor for events. |
| Event Name or ID | Select or specify the particular event (by name or ID) within the chosen application that triggers the webhook. |
Output
The node outputs JSON data representing the event payload received from Eduzz. The structure corresponds directly to the event data sent by Eduzz's webhook, containing details about the event type and associated information.
If the incoming webhook payload is empty or a "ping" event (used for testing connectivity), the node outputs an empty object, effectively not triggering downstream actions.
No binary data output is produced by this node.
Dependencies
- Requires an active Eduzz account with API access.
- Needs an API key credential (access token) configured in n8n to authenticate requests.
- Relies on Eduzz's webhook infrastructure to send event data.
- The node dynamically loads available applications and events from Eduzz via API calls to populate dropdown options.
Troubleshooting
- Webhook URL on localhost: The node throws an error if the webhook URL contains "localhost" because Eduzz cannot reach local addresses. Use a publicly accessible URL or tunneling service.
- Webhook creation errors: Errors during webhook creation or deletion typically indicate issues with API credentials or network connectivity. Verify the API token and ensure the Eduzz API is reachable.
- Empty or ping events: Receiving empty payloads or "ping" events results in no workflow execution. This is expected behavior for webhook validation.
- Test webhook firing: When running tests, sample data is automatically sent to the webhook. If no data appears, check that the webhook was created successfully and the correct event/application is selected.
Links and References
- Eduzz API Documentation (for detailed API and webhook info)
- n8n Expressions Documentation (for using expressions in property fields)