Overview
The Toolzz Trigger node is designed to receive webhook events from the Toolzz platform. It allows you to trigger n8n workflows based on specific events occurring in your Toolzz environment, such as user creation, course completion, or product redemption. This node is particularly useful for automating processes that should react instantly to changes or actions within Toolzz, such as updating CRM records when a new user registers, sending notifications upon course completions, or integrating with other systems when products are redeemed.
Practical examples:
- Automatically send a welcome email when a new user is created in Toolzz.
- Update an external database when a course is completed.
- Notify a Slack channel when a certificate is issued.
Properties
| Name | Type | Meaning |
|---|---|---|
| AccessToken | String | The API access token used to authenticate requests to the Toolzz API. Required for all operations. |
| Ambiente | Options | Selects the environment (Production or Development) of the Toolzz API to connect to. Determines the base URL for API requests. |
| Trigger On Name or ID | MultiOptions | Specifies which event(s) from Toolzz will trigger this workflow. You can select from a list of predefined events or specify an event ID using an expression. At least one is required. |
Output
The node outputs the data received from the Toolzz webhook as a JSON object. The structure of the output depends on the event sent by Toolzz, but it is always passed through as-is under the json field of the n8n item.
Example output:
{
"json": {
// ...all fields provided by the Toolzz webhook payload
}
}
- No binary data is produced by this node.
Dependencies
- External Service: Requires access to the Toolzz API.
- API Key: A valid Toolzz API access token must be provided via the "AccessToken" property.
- n8n Configuration: The node must be accessible from the internet if Toolzz needs to reach your n8n instance (for production use).
Troubleshooting
Common issues:
- Invalid Access Token: If the access token is missing or incorrect, webhook registration or event delivery will fail. Ensure the token is correct and has sufficient permissions.
- Webhook Not Triggering: Make sure your n8n instance is publicly accessible and the webhook path (
/webhooks) is reachable by Toolzz. - Event Not Selected: If no events are selected in "Trigger On Name or ID", the node will not register any webhooks and thus won't trigger.
- Duplicate Webhook Registration: If you change the trigger events or environment, old webhooks may persist. Use the node's delete functionality or manually remove unused webhooks from Toolzz.
Error messages:
- 401 Unauthorized / 403 Forbidden: Indicates authentication issues. Check your access token.
- Network errors: Suggest connectivity issues between n8n and Toolzz. Verify network/firewall settings.