Actions36
- Document Actions
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node interacts with the awork API to change the status of a specific project task. It is useful in workflow automation scenarios where task statuses need to be updated programmatically, such as moving a task from 'In Progress' to 'Completed' based on certain triggers or conditions. For example, after a task's associated work is done, this node can automatically update its status to reflect completion, helping keep project management up to date without manual intervention.
Use Case Examples
- Automatically update task status to 'Completed' when a related event occurs.
- Batch update multiple tasks' statuses to 'In Review' during a project phase transition.
Properties
| Name | Meaning |
|---|---|
| Task ID | The ID of the task to retrieve and update its status. |
| Status ID | The ID of the new status to assign to the task. |
| Request Options | Settings to control request behavior such as batching, SSL certificate validation, proxy usage, and timeout duration. |
Output
JSON
taskId- The ID of the task whose status was changed.statusId- The new status ID assigned to the task.response- The full response from the awork API after changing the task status.
Dependencies
- Requires an API key credential for authenticating with the awork API.
Troubleshooting
- Ensure the Task ID and Status ID are valid and exist in the awork system to avoid errors.
- Check network connectivity and proxy settings if requests fail or time out.
- If SSL certificate validation errors occur, consider enabling the 'Ignore SSL Issues' option cautiously.
- Batching settings should be configured properly to avoid overwhelming the API or hitting rate limits.
Links
- awork API Documentation - Official API documentation for awork, useful for understanding available endpoints and request formats.