Actions27
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
The node integrates with the awork API to automate workflow tasks related to project management. Specifically, for the "Project Task" resource and the "Change Status" operation, it allows users to update the status of a given task within a project. This is useful in scenarios where task progress needs to be tracked or updated programmatically, such as moving a task from "In Progress" to "Completed" based on external triggers or automated workflows.
Practical examples include:
- Automatically marking a task as completed when a related event occurs.
- Updating task statuses in bulk based on changes in other systems.
- Integrating task status updates into broader project management automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task whose status you want to change. This is required to specify which task to update. |
| Status ID | The identifier of the new status to assign to the task. This determines the updated state of the task (e.g., "To Do", "In Progress", "Done"). |
Output
The node outputs JSON data representing the updated task after the status change. This typically includes the task's details such as its ID, updated status, timestamps, and possibly other metadata returned by the awork API.
If the node supports binary data output (not indicated here), it would represent any file attachments or media related to the task, but this operation primarily deals with JSON task data.
Dependencies
- Requires an API key credential for authenticating with the awork API.
- The node configuration must include this API key to authorize requests.
- Network access to
https://api.awork.comis necessary.
Troubleshooting
- Invalid Task ID: If the provided Task ID does not exist or is malformed, the API will return an error. Verify that the Task ID is correct and corresponds to an existing task.
- Invalid Status ID: Providing a Status ID that does not exist or is not valid for the task's project may cause errors. Ensure the Status ID is valid and applicable.
- Authentication Errors: Missing or incorrect API credentials will result in authorization failures. Confirm that the API key is correctly configured.
- API Rate Limits: Excessive requests might trigger rate limiting. Implement retries or backoff strategies if needed.
- Network Issues: Connectivity problems can prevent successful API calls. Check network settings and firewall rules.
Links and References
- awork API Documentation — Official API docs for detailed information on endpoints and data models.
- n8n Documentation — For general guidance on using n8n nodes and managing credentials.