Actions12
Overview
The node "Cloodo Finance" integrates with the Cloodo Worksuite API to manage financial data related to invoices, payments, and recurring transactions. Specifically, for the Payment - Update operation, it allows users to update existing payment records by specifying various payment details such as project association, invoice linkage, currency, transaction information, exchange rate, and payment date.
This node is beneficial in scenarios where automated workflows need to keep payment records synchronized with external systems or when updating payment details programmatically after receiving new information (e.g., updated transaction IDs or corrected exchange rates).
Practical example:
A finance team uses this node within an n8n workflow to automatically update payment records whenever a payment confirmation email is received, ensuring that the ERP system reflects the latest payment status and details without manual entry.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the payment record to update. |
| Format Date | The format in which dates should be sent; currently supports "Y-M-D" (e.g., 2022-11-11). |
| Project ID | Identifier of the project associated with the payment. |
| Invoice ID | Identifier of the invoice linked to the payment. |
| Currency ID | Identifier of the currency used in the payment. |
| Transaction ID | Identifier of the transaction related to the payment. |
| Exchange Rate | The exchange rate applied to the payment amount; must be between 0 and 100 with two decimals. |
| Paid On | The date and time when the payment was made. |
Output
The node outputs JSON data representing the updated payment record as returned by the Cloodo Worksuite API. This typically includes all relevant fields of the payment resource, reflecting the changes made during the update operation.
If the node supports binary data output (not indicated explicitly here), it would represent any file attachments or documents related to the payment, but based on the provided code and properties, the output is primarily JSON structured data.
Dependencies
- Requires an active connection to the Cloodo Worksuite API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4. - Proper permissions on the API side to perform update operations on payment resources.
Troubleshooting
Common issues:
- Invalid or missing payment ID (
IDproperty) will cause the update to fail because the target record cannot be identified. - Incorrect or expired API credentials will result in authentication errors.
- Providing an exchange rate outside the allowed range (0 to 100) or with more than two decimal places may cause validation errors.
- Date formatting mismatches if the
Format Dateoption does not align with the expected API format.
- Invalid or missing payment ID (
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Check and update the API key credential in n8n.
- "Payment not found": Verify that the
IDcorresponds to an existing payment record. - "Invalid exchange rate": Ensure the exchange rate is a number between 0 and 100 with up to two decimals.
- "Bad Request" due to date format: Confirm the
Paid Ondate matches the selectedFormat Date.
Links and References
- Cloodo Worksuite API Documentation (assumed URL based on baseURL)
- n8n Documentation on Creating Custom Nodes
- General info on Date Formatting Options (for understanding date format strings)
