Overview
The Woovi Trigger node listens for specific Woovi events via a webhook. It is designed to handle incoming webhook POST requests from Woovi, filtering events based on the selected event type. This node is useful for automating workflows that depend on real-time notifications from Woovi, such as payment status updates or transaction events. For example, it can trigger workflows when a new charge is created, a payment is confirmed, or a transaction refund is received.
Use Case Examples
- Trigger a workflow when a new charge is created to update a database or notify a user.
- Start a process when a payment is confirmed to fulfill an order automatically.
Properties
| Name | Meaning |
|---|---|
| Event Names or Name or ID | The specific Woovi event to listen for. Users can select from a predefined list of events or specify event IDs using expressions. |
Output
JSON
body- The full payload of the webhook event from Woovi.
Dependencies
- Requires a webhook endpoint to receive POST requests from Woovi.
Troubleshooting
- If the webhook receives an event type not selected in the node, it responds with status 422 and a message 'event type not accepted'. Ensure the correct event is selected in the node settings.
- Ensure the webhook URL is correctly configured in Woovi to send events to this node.
- Check that the webhook is publicly accessible and not blocked by firewalls or network restrictions.
Links
- n8n Expressions Documentation - Documentation on how to use expressions to specify event IDs dynamically.