Actions62
- Engagement Actions
- Estimate Actions
- Client Actions
- ClientDetail 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 such as clients, leads, projects, and engagements. Specifically, for the ClientDetail resource with the Get Contacts operation, it fetches contact information associated with a particular client detail record identified by an ID.
Common scenarios where this node is beneficial include:
- Automating retrieval of client contact details for use in marketing campaigns or customer support workflows.
- Synchronizing client contact data from Cloodo CRM into other systems or databases.
- Enriching client records in automation workflows with up-to-date contact information.
Example: A user wants to get all contacts linked to a specific client detail entry to send personalized emails or update a mailing list.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the client detail record whose contacts you want to retrieve. This is a required string input. |
Output
The node outputs JSON data containing the contacts related to the specified client detail ID. The structure typically includes fields representing contact attributes such as name, email, phone number, role, and other relevant contact information as provided by the Cloodo CRM API.
If the node supports binary data output (not explicitly shown here), it would represent attachments or files related to contacts, but based on the provided code and context, the output is primarily JSON-formatted contact 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/. - Proper permissions on the Cloodo CRM account to access client details and their contacts.
Troubleshooting
- Missing or invalid ID: If the ID property is empty or incorrect, the API call will fail or return no data. Ensure the ID corresponds to an existing client detail record.
- Authentication errors: If the API key or token is missing or invalid, the node will throw authorization errors. Verify that the credential is correctly set up in n8n.
- API rate limits or downtime: Temporary failures may occur if the Cloodo API is unavailable or rate-limited. Retry after some time or check API status.
- Unexpected response format: If the API changes its response schema, the node might not parse the output correctly. Check for updates or adjust parsing logic accordingly.
Links and References
- Cloodo CRM API Documentation (base URL reference; actual docs may be available via Cloodo support)
- n8n documentation on creating custom nodes for further customization guidance