Actions27
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node integrates with the awork API to retrieve different types of work associated with project tasks. Specifically, the "Get Types of Work" operation under the "Project Task" resource fetches various categories or classifications of work that can be assigned or tracked within project tasks.
Typical use cases include:
- Automating reporting by extracting all available work types for task categorization.
- Synchronizing work type data with other project management tools.
- Filtering and organizing tasks based on their work type in downstream workflows.
For example, a project manager might use this node to pull all work types to dynamically populate dropdowns in custom forms or dashboards.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. |
| Filter By | Filter the results by specific criteria. For example, filtering work types where duration is greater than 5. See https://developers.awork.com/filtering for syntax details. |
| Order By | Order the results by a specific field and direction, e.g., sorting by name ascending. See https://developers.awork.com/ordering for syntax details. |
Output
The node outputs JSON data containing an array of work type objects. Each object represents a type of work related to project tasks, typically including fields such as ID, name, description, and possibly metadata like creation date or status.
If binary data were involved (not indicated here), it would represent file attachments or similar content, but this operation focuses on JSON data only.
Dependencies
- Requires an API key credential for authenticating with the awork API.
- The node uses the base URL
https://api.awork.comand expects standard JSON headers. - No additional external dependencies are required beyond the configured API authentication.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- Incorrect filter or order syntax causing API errors.
- Network connectivity problems preventing access to the awork API.
Error messages:
- 401 Unauthorized: Check that the API key credential is correctly set and has necessary permissions.
- 400 Bad Request: Verify the syntax of the "Filter By" and "Order By" properties against the awork API documentation.
- Timeout or Network Error: Ensure network connectivity and that the awork API endpoint is reachable.