awork icon

awork

Automate your workflows with the awork API

Actions26

Overview

The Get Tasks of Project operation for the Project Task resource retrieves a list of tasks associated with a specific project from the awork API. This node is useful in scenarios where you need to automate workflows that involve tracking, listing, or processing tasks within a particular project. For example, you might use this node to:

  • Generate reports of all tasks for a given project.
  • Trigger notifications or follow-up actions based on the status of project tasks.
  • Integrate project task data into other systems for further analysis or automation.

Properties

Below are the input properties supported by this operation:

Display Name Type Meaning
Project ID String The unique identifier of the project whose tasks you want to retrieve. (Required)
Return All Boolean Whether to return all results (true) or limit the number of returned items (false).
Filter By String Criteria to filter the results, e.g., duration gt 5. See awork filtering documentation for details.
Order By String Field and direction to order the results, e.g., FirstName asc. See awork ordering documentation for details.

Output

The output will be a JSON array where each item represents a task belonging to the specified project. Each task object typically contains fields such as:

{
  "id": "string",
  "name": "string",
  "status": "string",
  "assignee": "object",
  "dueDate": "string",
  ...
}

Note: The exact structure of each task object depends on the awork API response. Additional fields may be present.

Dependencies

  • External Service: Requires access to the awork API.
  • API Key/Credentials: You must configure n8n with valid aworkApi credentials.
  • n8n Configuration: No additional configuration required beyond setting up credentials.

Troubleshooting

Common Issues:

  • Invalid Project ID: If the provided Project ID does not exist or is incorrect, the node may return an error or an empty result set.
  • Authentication Errors: Missing or invalid API credentials will result in authentication errors.
  • Filter/Order Syntax Errors: Incorrect syntax in the "Filter By" or "Order By" fields can cause API errors. Refer to the awork filtering and ordering documentation for correct usage.

Error Messages & Resolutions:

  • "401 Unauthorized": Check your awork API credentials in n8n.
  • "404 Not Found": Verify the Project ID is correct and exists in awork.
  • "400 Bad Request": Review your filter or order expressions for syntax errors.

Links and References

Discussion