awork icon

awork

Automate your workflows with the awork API

Actions27

Overview

This node integrates with the awork API to retrieve all project statuses. It is useful for workflows that need to list or process the various statuses defined within projects, such as tracking progress stages or filtering tasks by status. For example, a project manager could use this node to fetch all possible project statuses and then automate notifications or reporting based on those statuses.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit (true returns all, false limits results).
Filter By Filter the results by specific criteria using a query string (e.g., duration gt 5). See filtering docs.
Order By Order the results by a specific field and direction (e.g., FirstName asc). See ordering docs.

Output

The node outputs JSON data containing an array of project statuses. Each item in the array represents a single project status with its associated fields as returned by the awork API. The output does not include binary data.

Example structure of one project status item (fields may vary):

{
  "id": "string",
  "name": "string",
  "color": "string",
  "order": 0,
  "archived": false
}

Dependencies

  • Requires an API key credential for authenticating with the awork API.
  • The node uses the base URL https://api.awork.com.
  • No additional external dependencies are required beyond the API access.

Troubleshooting

  • Common issues:

    • Authentication errors if the API key is missing or invalid.
    • Filtering or ordering syntax errors if the filter/order strings do not conform to the awork API specification.
    • Pagination issues if Return All is set to false but the limit is too low to retrieve expected data.

  • Error messages:

    • Unauthorized or 401 errors indicate problems with the API key; verify credentials.
    • 400 Bad Request errors often relate to malformed filter or order parameters; check the syntax against the awork API documentation.
    • Network or timeout errors suggest connectivity issues; ensure the n8n instance can reach the awork API endpoint.

Links and References

Discussion