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
This node integrates with the Cloodo CRM API to retrieve various types of data related to business and client management. Specifically, for the ClientDetail resource with the Get Invoices operation, it fetches invoice information associated with a particular client detail record identified by an ID.
Typical use cases include:
- Retrieving all invoices linked to a specific client detail for financial review.
- Automating invoice tracking and reporting within workflows.
- Integrating invoice data into other systems such as accounting or ERP platforms.
For example, a user might input a client detail ID to get all invoices issued to that client, enabling automated follow-up on payments or generating financial summaries.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the client detail record for which invoices are to be retrieved. This is a required string input. |
Output
The node outputs JSON data containing the invoices related to the specified client detail ID. The structure typically includes invoice details such as invoice number, date, amount, status, and other relevant metadata as provided by the Cloodo API.
If the node supports binary data output (not explicitly shown in the code), it would likely represent attachments or invoice documents; however, this is not indicated in the provided source.
Dependencies
- Requires an active connection to the Cloodo CRM 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 network access to the Cloodo API endpoint must be ensured.
Troubleshooting
- Missing or invalid ID: If the ID property is empty or incorrect, the API call will fail or return no data. Ensure the correct client detail ID is provided.
- Authentication errors: If the API key or token is missing or invalid, the node will throw authorization errors. Verify credential configuration.
- Network issues: Timeouts or connectivity problems can cause failures. Check network settings and API availability.
- API changes: If the Cloodo API changes its endpoints or response formats, the node may stop working correctly until updated.
Links and References
- Cloodo CRM API Documentation (assumed base URL, check official docs for detailed API reference)
- n8n documentation on creating custom nodes