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 data related to various resources such as clients, engagements, leads, projects, and more. Specifically, for the ClientDetail resource with the Get Engagements operation, it fetches engagement records associated with a particular client detail identified by an ID.
Typical use cases include:
- Retrieving all engagements linked to a specific client detail to analyze interactions or activities.
- Automating workflows that require fetching engagement data for reporting or follow-up actions.
- Integrating engagement information into other systems or dashboards for enhanced customer relationship management.
Example: A user wants to get all meetings, calls, or tasks (engagements) related to a particular client detail to prepare for a sales call.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the client detail whose engagements are to be retrieved. This is a required string input. |
Output
The node outputs JSON data representing the engagements associated with the specified client detail ID. Each item in the output typically contains details about an engagement such as its type, status, date, description, and any other metadata 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 engagements, but this is not indicated in the provided code snippet.
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 API side to access client detail engagements.
Troubleshooting
Common issues:
- Invalid or missing ID property will result in no data or errors.
- Authentication failures if the API key or token is incorrect or expired.
- Network connectivity problems preventing access to the Cloodo API endpoint.
- Insufficient permissions to read engagement data for the given client detail.
Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and renew if necessary.
- "Not Found" or empty results: Verify the client detail ID exists and is correct.
- "Request timeout" or "Network error": Ensure network connectivity and API availability.
Links and References
- Cloodo CRM API Documentation (Assumed base URL; check official docs for detailed endpoints)
- n8n documentation on creating custom nodes for further customization guidance