Actions36
- Document Actions
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node operation retrieves a specific project task by its ID from the awork API. It is useful for workflows that need to fetch detailed information about a particular task within a project, such as task status, assignees, or custom fields. For example, it can be used to automate task tracking, reporting, or integration with other project management tools.
Use Case Examples
- Retrieve task details by providing the task ID to monitor progress or update other systems.
- Fetch a task's information to trigger notifications or conditional workflow steps based on task status.
Properties
| Name | Meaning |
|---|---|
| Task ID | The ID of the task to retrieve, used to specify which project task to fetch. |
| Request Options | Additional request settings such as batching, SSL certificate validation, proxy configuration, and timeout settings to control how the API request is made. |
Output
JSON
id- The unique identifier of the retrieved task.name- The name or title of the task.status- The current status of the task.assignees- List of users assigned to the task.dueDate- The due date of the task, if set.customFields- Custom fields associated with the task, if any.
Dependencies
- Requires an API key credential for authenticating with the awork API.
Troubleshooting
- Ensure the Task ID is correct and exists in the awork system to avoid 'task not found' errors.
- Check network connectivity and proxy settings if requests time out or fail to connect.
- If SSL certificate validation fails, enable the 'Ignore SSL Issues' option cautiously to bypass certificate errors.
- Verify that the API key credential is valid and has sufficient permissions to access project tasks.