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 a Task resource. It allows users to modify existing tasks by specifying the task ID and updating various fields such as assigned members, board column, and status. This is useful in project management workflows where task details need to be dynamically updated based on progress or changes in assignment.
Practical examples include:
- Updating the status of a task from "in progress" to "completed".
- Changing the board column of a task to reflect its new stage in a Kanban workflow.
- Assigning or reassigning team members to a task by updating member IDs.
Properties
Name | Meaning |
---|---|
ID | The unique identifier of the task to update. |
Additional Fields | A collection of optional fields that can be updated for the task: |
- Member IDs | JSON array of user IDs to assign to the task (e.g., [123,456] ). |
- Board Column IDs | String representing the ID of the board column to which the task belongs. |
- Status | String indicating the current status of the task (e.g., "completed"). |
Output
The node outputs JSON data representing the updated task object returned by the Cloodo API after the update operation. This typically includes the task's current state with all updated fields reflected.
If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON.
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/
. - The node expects JSON content type for requests and responses.
Troubleshooting
- Invalid ID: If the provided task ID does not exist or is malformed, the API will likely return an error. Ensure the ID is correct and corresponds to an existing task.
- Authentication errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key/token is correctly set up in n8n credentials.
- Malformed JSON in Member IDs: The "Member IDs" field expects a valid JSON array string. Invalid JSON syntax will cause parsing errors. Use proper JSON formatting like
[123,456]
. - Invalid field values: Providing unsupported status values or incorrect board column IDs may result in API errors. Confirm valid options with the Cloodo CRM documentation or UI.
- Network issues: Connectivity problems to the API endpoint will prevent updates. Check network access and API availability.
Links and References
- Cloodo CRM API Documentation (Assumed, please verify actual docs)
- n8n Documentation on Creating Custom Nodes
- JSON format guidelines for input fields: https://www.json.org/json-en.html