Actions27
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node integrates with the awork API to retrieve task lists associated with a specific project. It is designed to fetch collections of task lists within a given project, which can be useful for project management automation, reporting, or synchronization with other tools.
Common scenarios include:
- Automatically retrieving all task lists of a project to display or process them in downstream workflows.
- Filtering and ordering task lists based on criteria such as creation date or name.
- Fetching either all task lists or limiting the number of results for performance optimization.
For example, a user might use this node to get all task lists of a project before creating tasks within those lists or generating status reports.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project whose task lists you want to retrieve. |
| Return All | Whether to return all task lists or limit the output to a certain number (if false, a limit applies). |
| Filter By | A filter expression to narrow down the task lists returned, e.g., filtering by duration or other fields. See awork filtering for syntax details. |
| Order By | Defines the sorting order of the returned task lists, e.g., by name ascending or creation date descending. See awork ordering for syntax details. |
Output
The node outputs JSON data representing the task lists retrieved from the specified project. Each item in the output corresponds to a task list object containing its properties as defined by the awork API.
If binary data were involved (e.g., attachments), it would be summarized here, but this operation deals only with JSON task list data.
Dependencies
- Requires an API key credential for authenticating with the awork API.
- The node uses the base URL
https://api.awork.comand expects JSON responses. - No additional external dependencies are indicated beyond the awork API access.
Troubleshooting
- Invalid Project ID: If the provided project ID does not exist or is incorrect, the API will likely return an error or empty result. Verify the project ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is properly configured.
- Filter or Order Syntax Errors: Incorrect filter or order expressions may cause the API to reject the request. Refer to the awork API documentation for correct syntax.
- Rate Limits: Excessive requests may hit API rate limits; consider enabling "Return All" cautiously or implement pagination if supported.