Actions62
- Client Actions
- ClientDetail Actions
- Engagement Actions
- Estimate Actions
- Lead Actions
- Lead Agent Actions
- Lead Category Actions
- Lead Source Actions
- Lead Status Actions
- Proposal Actions
- Project Actions
- Task Actions
- Note Actions
Overview
The node integrates with the Cloodo CRM API to retrieve payment information related to projects. Specifically, the "Project Payment" operation fetches payment data for projects, supporting pagination and filtering by date ranges. This node is useful in scenarios where users want to automate financial tracking or reporting of project payments within their workflows.
Practical examples include:
- Automatically retrieving recent payments made on projects to update accounting systems.
- Generating reports on project cash flow filtered by specific date ranges.
- Integrating project payment data into dashboards or notifications.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the project for which to retrieve payment information. |
| Page | The page number of results to retrieve (for paginated responses). Defaults to 1. |
| Additional Fields | Optional filters and limits for the query: |
| - Limit | Number of records per page. Options: 10, 25, 50. |
| - From Date | Start date filter for payments (format as string, e.g., "YYYY-MM-DD"). |
| - To Date | End date filter for payments (format as string, e.g., "YYYY-MM-DD"). |
Output
The node outputs JSON data containing the payment details retrieved from the Cloodo API for the specified project. The structure typically includes an array of payment records, each with fields such as payment amount, date, status, and related metadata.
If binary data were involved (e.g., invoices as files), it would be included in a binary property, but this node focuses on JSON payment data only.
Dependencies
- Requires an active connection to the Cloodo CRM API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/.
Troubleshooting
Common Issues:
- Invalid or missing project ID will result in no data or errors.
- Incorrect date formats in "From Date" or "To Date" may cause API request failures.
- Pagination parameters out of range might return empty results.
Error Messages:
- Authentication errors indicate invalid or expired API credentials; reconfigure the API key.
- "Not Found" errors suggest the project ID does not exist or user lacks permission.
- Rate limiting errors require waiting before retrying or adjusting request frequency.
Links and References
- Cloodo CRM API Documentation (assumed official docs)
- n8n documentation on HTTP Request Node for understanding API integrations