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 data related to various CRM resources. Specifically, for the "Engagement" resource with the "Get" operation, it fetches detailed information about a single engagement record identified by its ID. This is useful in scenarios where you want to pull up-to-date engagement details from your CRM system into an automation workflow, such as syncing engagement data with other tools, generating reports, or triggering follow-up actions based on engagement status.
Practical example:
You have a workflow that triggers when a new engagement is created or updated in Cloodo CRM. Using this node configured to "Get Engagement," you can retrieve all relevant details of that engagement by its ID and then use that data to update a project management tool or send notifications.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the engagement record to retrieve. This string property specifies which engagement's details the node will fetch. |
Output
The node outputs JSON data representing the engagement record retrieved from the Cloodo CRM API. The structure typically includes all fields associated with an engagement, such as engagement metadata, status, related client info, dates, and any custom fields defined in the CRM.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the engagement, but this is not evident from the provided code.
Dependencies
- Requires an active connection to the Cloodo CRM API.
- Needs an API authentication token or key credential configured in n8n to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/. - The node expects JSON responses and sends JSON content-type headers.
Troubleshooting
Common issues:
- Invalid or missing ID: If the ID property is empty or incorrect, the API call will fail or return no data.
- Authentication errors: Missing or invalid API credentials will cause authorization failures.
- Network issues: Connectivity problems to the Cloodo API endpoint will prevent data retrieval.
Error messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly set up and valid.
- "Not Found" or similar: Verify that the provided engagement ID exists in the CRM.
- "Bad Request": Ensure the ID format matches what the API expects (usually a non-empty string).
Links and References
- Cloodo CRM API Documentation (Assumed base URL; consult official docs for full API reference)
- n8n documentation on creating custom nodes