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 operations. Specifically, for the ClientDetail resource and the Get Payments operation, it fetches payment information associated with a particular client detail record. This is useful in scenarios where you want to automate financial tracking, reporting, or reconciliation by programmatically accessing payment data linked to clients.
Practical examples include:
- Automatically retrieving payment histories for clients to update accounting systems.
- Generating reports on client payments within workflows.
- Triggering follow-up actions based on payment status or amounts.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the client detail record for which to retrieve payment information. |
Note: The provided properties JSON only defines an "ID" property relevant to multiple operations including getting payments under the ClientDetail resource.
Output
The node outputs JSON data containing the payment details retrieved from the Cloodo CRM API for the specified client detail ID. The structure typically includes fields such as payment amount, date, status, and possibly related invoice or project references depending on the API response.
If binary data were involved (e.g., attachments), it would be included in a separate binary output field, but this node focuses on JSON payment data.
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/.
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 setup in n8n.
- Network issues: Connectivity problems can cause request failures. Check network access to the Cloodo API endpoint.
- API changes: If the Cloodo API changes its endpoints or response formats, the node may need updating.
Links and References
- Cloodo CRM API Documentation (assumed base URL; consult official docs for detailed API reference)