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 historical data about a specific task. It is designed to fetch the history or audit trail of changes and events related to a given task within the Cloodo project management environment. This functionality is useful for tracking task progress, reviewing past updates, or auditing changes made over time.
Common scenarios include:
- Project managers wanting to review all modifications made to a task.
- Auditors needing a detailed log of task activities.
- Team members tracking the evolution of a task to understand its current state.
Example: A user inputs a Task ID to get a chronological list of all changes made to that task, such as status updates, comments, or assignment changes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the task whose history you want to retrieve. This is a required string input where you enter the Task ID. |
Output
The node outputs JSON data containing the history details of the specified task. This typically includes an array of records representing individual historical events or changes associated with the task, such as timestamps, user actions, previous and new values, and possibly comments or notes related to each change.
If the node supports binary data output (not indicated in the provided code), it would represent attachments or files related to the task history, but this is not evident here.
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
- Missing or invalid Task ID: Ensure the Task ID is correctly entered; otherwise, the API will return an error or no data.
- Authentication errors: Verify that the API key or token credential is valid and has sufficient permissions.
- Network issues: Check connectivity to the Cloodo API endpoint.
- API rate limits or downtime: If requests fail repeatedly, confirm if the API service is operational and not throttling requests.
Common error messages might include:
- "Task not found" — indicates the provided Task ID does not exist.
- "Unauthorized" — indicates invalid or missing API credentials.
- "Bad Request" — likely due to malformed input parameters.
Resolving these usually involves verifying input correctness, credential validity, and network access.
Links and References
- Cloodo CRM API Documentation (assumed base URL, check official docs for exact references)
- n8n documentation on creating custom nodes