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 Many operation, it fetches a list of payment records from the system.
This node is useful in scenarios where users want to automate the retrieval of multiple payment entries for reporting, reconciliation, or further processing within their workflows. For example, a finance team could use this node to pull all payments made within a specific date range or filter payments by project or category to generate customized financial reports.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of the results to retrieve (pagination). Defaults to "1". |
| Additional Fields | A collection of optional filters to refine the payment list: |
| - Search | Text string to search payments by keyword. |
| - From Date | Start date to filter payments from (inclusive). |
| - To Date | End date to filter payments up to (inclusive). |
| - Category ID | Filter payments by a specific category identifier. |
| - Project ID | Filter payments associated with a specific project identifier. |
Output
The node outputs JSON data representing an array of payment objects retrieved from the Cloodo Worksuite API. Each payment object typically contains details such as payment amount, date, category, project association, and other relevant metadata.
If the node supports binary data output (not indicated explicitly here), it would represent attachments or documents related to payments, but based on the provided code and properties, the output is primarily structured JSON data.
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. - The node expects JSON responses and sends requests with appropriate headers (
Accept: application/json,Content-Type: application/json).
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect pagination values may result in empty or incomplete data sets.
- Using invalid date formats in "From Date" or "To Date" fields can lead to request errors.
- Filtering by non-existent category or project IDs will return no results.
Error Messages:
- Authentication errors typically indicate issues with the API key/token; verify credentials are correctly set.
- HTTP 400 errors may occur if query parameters are malformed; ensure dates and IDs follow expected formats.
- Network or timeout errors suggest connectivity problems with the Cloodo API endpoint.
Links and References
- Cloodo Worksuite API Documentation (Assumed URL based on base URL, please verify actual docs)
- n8n Documentation on Creating Custom Nodes