Overview
The Woovi Trigger node is designed to handle incoming webhook events from the Woovi platform within n8n workflows. It allows users to listen for specific events occurring in their Woovi account (such as payment updates or notifications) and trigger automated workflows in response. This node is particularly useful for automating processes based on real-time events, such as updating records, sending notifications, or integrating with other systems when certain actions occur in Woovi.
Practical examples:
- Automatically update a CRM when a new payment is received in Woovi.
- Send a Slack notification when a refund event occurs.
- Start an order fulfillment workflow when a payment is confirmed.
Properties
| Name | Type | Meaning |
|---|---|---|
| Event Names or Name or ID | options | The event(s) to listen to from Woovi. You can select from a list of available events or specify event IDs using an expression. This determines which Woovi events will trigger the workflow. |
Output
The node outputs the body of the incoming webhook request from Woovi as JSON. The structure of this output depends on the specific event sent by Woovi, but generally, it will include all data fields provided by Woovi for the triggered event.
Example output:
{
"event": "payment.created",
"data": {
"id": "12345",
"amount": 1000,
"currency": "BRL",
// ...other event-specific fields
}
}
Note: The actual fields depend on the event type configured in Woovi.
If Woovi sends binary data, it will not be processed by this node; only JSON payloads are handled.
Dependencies
- External Service: Requires access to the Woovi API.
- API Key: Needs valid Woovi API credentials configured in n8n under the credential type
wooviApi. - n8n Configuration: No special environment variables required beyond standard credential setup.
Troubleshooting
Common issues:
- Webhook not triggering: Ensure that the correct event(s) are selected and that the webhook is properly registered in your Woovi account.
- Authentication errors: Double-check that the Woovi API credentials are correctly set up in n8n.
- "NodeApiError" messages: These indicate issues with API requests to Woovi, such as network problems, invalid credentials, or incorrect endpoint usage. Review the error details and verify your configuration.
How to resolve:
- Re-authenticate or update your Woovi API credentials if you encounter authentication errors.
- Check the event selection and ensure the webhook URL is accessible from Woovi's servers.
- Consult the n8n logs for detailed error information.