Actions26
- Milestone Actions
- Project Actions
- Project Admin Actions
- Task Actions
- Time Log Actions
Overview
The node interacts with the Cloodo Worksuite API to retrieve data related to various project management resources, including tasks. Specifically, for the "Task" resource and the "Get History Task" operation, it fetches the historical data or activity log of a particular task identified by its ID. This is useful for tracking changes, updates, or progress on a task over time.
Common scenarios include:
- Auditing task changes to understand who made what modifications and when.
- Displaying a timeline of task activities in dashboards or reports.
- Synchronizing task history with other systems for comprehensive project tracking.
Example: A project manager wants to review all updates made to a specific task to ensure compliance with project timelines and quality standards.
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 historical records of the specified task. This typically includes details such as timestamps of changes, descriptions of actions performed, user information who made the changes, and possibly status updates or comments related to the task's lifecycle.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the task history, but based on the provided code and properties, the output is JSON-only.
Dependencies
- Requires an active connection to the Cloodo Worksuite API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4. - Proper network access to the API endpoint must be ensured.
Troubleshooting
- Missing or invalid Task ID: If the ID property is empty or incorrect, the API will likely return an error indicating that the task was not found. Ensure the correct Task ID is provided.
- Authentication errors: If the API key or token is missing or invalid, the node will fail to authenticate. Verify that the API credentials are correctly set up.
- Network issues: Timeouts or connectivity problems can prevent data retrieval. Check network settings and API availability.
- API rate limits: Excessive requests might lead to throttling; consider implementing retries or backoff strategies if supported.
Links and References
- Cloodo Worksuite API Documentation (Assumed URL based on base URL)
- General n8n documentation on Creating Custom Nodes