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 Recurring - Create operation, it allows users to create a new recurring financial record in the system. This is useful for automating the creation of repeated billing or payment schedules, such as monthly subscriptions, installment plans, or regular service charges.
Practical examples include:
- Creating a monthly subscription invoice that recurs automatically.
- Setting up a recurring payment schedule for clients.
- Automating the generation of periodic financial records with specified issue and due dates.
Properties
| Name | Meaning |
|---|---|
| Client ID | The identifier of the client associated with the recurring record. |
| Currency ID | The identifier of the currency used for the recurring transaction. |
| Status | The payment status of the recurring record; options are: "Paid" or "Unpaid". |
| Format Date | The date format to use for issue and due dates; currently supports "Y-M-D" (e.g., 2022-11-11). |
| IssueDate | The date when the recurring record is issued. |
| DueDate | The date by which payment for the recurring record is due. |
| Total | The total amount for the recurring transaction. |
| Exchange Rate | The exchange rate applied to the transaction amount; must be between 0 and 100, precision 2. |
| Calculate Tax | Specifies when tax calculation occurs relative to discounts; options are "After Discount" or "Before Discount". |
Output
The node outputs JSON data representing the newly created recurring financial record as returned by the Cloodo Worksuite API. This typically includes details such as the record's unique ID, client information, currency, status, issue and due dates, total amount, exchange rate, and tax calculation method.
If the node supports binary data output (not indicated here), it would represent attachments or documents related to the recurring record, but this is not evident from the provided code.
Dependencies
- Requires an active connection to the Cloodo Worksuite API.
- Needs an API authentication token or key configured in n8n credentials (referred generically as "an API key credential").
- The base URL for API requests is
https://erp-amz.cloodo.com/v4. - Proper configuration of the node’s credentials within n8n is necessary for successful API communication.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Incorrect or missing required properties (e.g., Client ID, Currency ID, IssueDate) will result in validation errors.
- Invalid date formats or values outside allowed ranges (e.g., exchange rate > 100) may cause request rejections.
Error Messages:
- Authentication errors typically indicate issues with the API key or token; verify credentials in n8n.
- Validation errors on input fields suggest missing or improperly formatted data; ensure all required fields are correctly filled.
- Network or timeout errors may occur if the API endpoint is unreachable; check network connectivity and API availability.
Links and References
- Cloodo Worksuite API Documentation (Assumed based on base URL, please verify actual documentation link)
- n8n Documentation on Creating Custom Nodes