Actions27
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node integrates with the awork API to automate task management within projects. Specifically, the "Add Tag" operation for the "Project Task" resource allows users to add a tag label to an existing project task by specifying the task's ID and the tag name. This is useful for categorizing tasks, improving searchability, or triggering workflow automations based on tags.
Practical examples include:
- Adding priority or status tags (e.g., "urgent", "in-review") to tasks dynamically.
- Organizing tasks by feature or team using custom tags.
- Enhancing reporting by tagging tasks with relevant keywords.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the project task to which the tag will be added. This is required. |
| Tag Name | The name of the tag to add to the specified task. |
Output
The node outputs JSON data representing the updated task after the tag has been added. This typically includes the task's details along with its current tags, reflecting the newly added tag.
If the node supports binary data output, it would generally relate to attachments or files associated with the task, but this operation focuses on metadata (tags) only, so no binary output is expected.
Dependencies
- Requires an active connection to the awork API via an API key credential.
- The node must be configured with valid authentication credentials that allow modifying project tasks.
- 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 indicating the task was not found. Verify the Task ID is correct.
- Missing or Invalid Tag Name: Ensure the tag name is provided and conforms to any naming rules enforced by awork.
- Authentication Errors: If the API key is missing, expired, or lacks permissions, the node will fail with an authentication error. Check the API credentials configuration.
- API Rate Limits: Excessive requests may trigger rate limiting; consider adding delays or retries.
- Network Issues: Connectivity problems to the awork API endpoint will cause failures; verify network settings.