Overview
This n8n custom node, Woovi, automates interactions with the Woovi workflow API. Specifically, it allows users to create a new charge by sending a POST request to the /charge endpoint of the Woovi API. This node is useful in scenarios where you need to programmatically generate payment charges within automated workflows, such as invoicing systems, e-commerce order processing, or financial reconciliation pipelines.
Practical examples:
- Automatically generating a payment charge when a new order is received.
- Creating unique transaction records for each customer purchase.
- Integrating Woovi payments into broader business automation flows.
Properties
| Name | Type | Meaning |
|---|---|---|
| Value | Number | The amount to be charged, specified in cents. |
| CorrelationID | String | A unique identifier for the charge transaction. |
Output
The node returns the JSON response from the Woovi API's /charge endpoint. The structure of this output depends on the API's response, but typically includes details about the created charge (such as its ID, status, and other metadata). The output is always in JSON format; binary data is not produced by this node.
Dependencies
- External Service: Requires access to the Woovi API.
- API Key: You must configure valid Woovi API credentials in n8n under the credential type
wooviApi. - n8n Configuration: No additional environment variables are required beyond standard credential setup.
Troubleshooting
Common Issues:
- Invalid Credentials: If the Woovi API credentials are missing or incorrect, the node will fail to authenticate.
- Missing Required Fields: Both "Value" and "CorrelationID" must be provided; omitting them may result in API errors.
- API Errors: Any error returned by the Woovi API (e.g., invalid parameters, insufficient permissions) will cause the node to throw an error.
Error Messages:
NodeApiError: This error wraps any issues encountered during the API request. Check the error message for details from the Woovi API, such as authentication failures or validation errors.
How to resolve:
- Double-check your Woovi API credentials in n8n.
- Ensure all required input properties are filled out correctly.
- Review the error message for specific guidance from the Woovi API.