Actions27
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node integrates with the awork API to retrieve task statuses associated with a specific project. It is useful for workflow automation scenarios where you need to monitor or process the current statuses of tasks within a project, such as reporting progress, triggering actions based on status changes, or syncing task states with other systems.
Practical examples include:
- Fetching all task statuses of a project to generate a status summary report.
- Automatically updating dashboards or notifications when task statuses change.
- Filtering and ordering task statuses to prioritize work or analyze workflow efficiency.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project whose task statuses you want to retrieve. |
| Return All | Whether to return all task statuses or limit the number of results returned. |
| Filter By | A filter expression to narrow down the results by specific criteria (e.g., filtering by duration). |
| Order By | Specifies the field and direction to order the results (e.g., ordering by first name ascending). |
Output
The node outputs JSON data containing an array of task status objects related to the specified project. Each object typically includes details about a task status such as its ID, name, color, and possibly metadata like creation date or order in the workflow.
If binary data were involved (not indicated here), it would represent file attachments or similar content, but this node focuses on JSON task status information only.
Dependencies
- Requires an API key credential for authenticating with the awork API.
- Needs network access to
https://api.awork.com. - No additional external dependencies beyond the awork API and n8n's HTTP request capabilities.
Troubleshooting
Common issues:
- Invalid or missing Project ID will cause the API call to fail or return no data.
- Incorrect API credentials or expired tokens will result in authentication errors.
- Improperly formatted filter or order expressions may lead to API errors or empty results.
Error messages:
- Authentication errors: Check that the API key credential is correctly configured and valid.
- "Project not found" or similar: Verify the Project ID is correct and accessible by the authenticated user.
- Filter/order syntax errors: Refer to the awork API filtering and ordering documentation to ensure correct syntax.