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 system to create a new Engagement record. An Engagement typically represents an interaction or activity related to a client or lead, such as meetings, calls, or tasks that track communication and progress.
Common scenarios for using this node include:
- Automatically logging a new engagement when a sales call is completed.
- Creating follow-up tasks or notes linked to a specific user or client.
- Tracking the status and priority of ongoing engagements within a CRM workflow.
For example, after a customer support call, you could use this node to create an engagement with details about the call subject, assigned user, status, priority, and any additional notes.
Properties
| Name | Meaning |
|---|---|
| Subject | The title or brief description of the engagement. |
| User ID | Identifier of the user responsible or associated with this engagement. |
| Status | Current state of the engagement (e.g., open, closed, pending). |
| Priority | Importance level of the engagement (e.g., low, medium, high). |
| Additional Fields | Optional extra data fields; currently supports: |
| - Note | A detailed description or comment related to the engagement. |
Output
The node outputs JSON data representing the newly created Engagement object as returned by the Cloodo CRM API. This typically includes all properties of the engagement such as its unique ID, subject, user association, status, priority, timestamps, and any notes added.
No binary data output is involved in this operation.
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
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Validation errors: Missing required fields like Subject or User ID may cause the API to reject the request. Verify all mandatory inputs are provided.
- Network issues: Check connectivity to the Cloodo CRM endpoint and firewall settings.
- Unexpected API responses: Confirm that the API version and endpoint URLs have not changed.
Links and References
- Cloodo CRM API Documentation (assumed base URL, check official docs for details)
- n8n documentation on creating custom nodes