Actions12
Overview
The node "Cloodo Finance" integrates with the Cloodo Worksuite API to retrieve financial data related to invoices, payments, and recurring transactions. Specifically, for the Payment - Get operation, it fetches detailed information about a single payment by its unique identifier (ID). This is useful in scenarios where you need to access or verify payment details such as status, amount, date, or associated invoice within automated workflows.
Practical examples include:
- Automatically retrieving payment details after a transaction completes.
- Validating payment information before triggering downstream processes like accounting entries or notifications.
- Synchronizing payment data from Cloodo Worksuite into other systems.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the payment to retrieve. You must provide this ID to fetch the specific payment's details. |
Output
The node outputs JSON data representing the payment object retrieved from the Cloodo Worksuite API. This typically includes fields such as payment ID, amount, date, status, payer information, and any metadata associated with the payment.
If the node supports binary data output (not indicated here), it would represent attachments or documents related to the payment, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an active connection to the Cloodo Worksuite API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4. - Proper network access to the API endpoint is necessary.
Troubleshooting
- Missing or invalid ID: If the ID property is empty or incorrect, the API will likely return an error indicating that the payment was not found. Ensure the correct payment ID is provided.
- Authentication errors: If the API key or token is missing, expired, or invalid, the node will fail to authenticate. Verify the credential configuration.
- Network issues: Timeouts or connectivity problems can cause failures. Check network settings and API availability.
- API changes: If the Cloodo Worksuite API changes its endpoints or response format, the node may stop working correctly until updated.
Links and References
- Cloodo Worksuite API Documentation (Assumed base URL; consult official docs for detailed API reference)
- n8n documentation on creating custom nodes for further customization guidance