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 update an existing Engagement record. It allows users to modify specific fields of an Engagement, such as linking it to a different project or agent, or changing its status. This is useful in scenarios where engagement details evolve over time and need to be kept current within the CRM system.
Practical examples include:
- Updating the status of an engagement after a milestone is reached.
- Assigning a new agent to an engagement.
- Associating an engagement with a different project.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Engagement to update. |
| Additional Fields | Optional fields to update on the Engagement: |
| - Project ID | Identifier of the project to associate with the Engagement. |
| - Agent ID | Identifier of the agent responsible for the Engagement. |
| - Status | Status identifier to update the Engagement's current state. |
Output
The node outputs JSON data representing the updated Engagement object as returned by the Cloodo CRM API. This typically includes all fields of the Engagement after the update operation, reflecting the new values set.
If the API supports binary data related to Engagements (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON 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
- Invalid ID error: If the provided Engagement ID does not exist or is malformed, the API will return an error. Verify that the ID is correct and corresponds to an existing Engagement.
- Authentication errors: Ensure that the API key or token credential is valid and has sufficient permissions to update Engagement records.
- Field validation errors: When updating fields like Project ID, Agent ID, or Status, ensure these IDs exist and are valid within the CRM system.
- Network issues: Confirm network connectivity to the Cloodo API endpoint and that no firewall or proxy blocks the request.
Links and References
- Cloodo CRM API Documentation (assumed base URL; consult official docs for detailed API reference)