Check dependencies before completing Awork tasks (workaround)

by Gregor · 209 views · created 2025-05-23 · Project Management

What this workflow does

This workflow has 25 nodes and runs when an HTTP POST request hits its webhook URL. It uses only n8n's built-in nodes. It also calls api.awork.com over HTTP.

How it runs

Trigger: When an HTTP POST request hits its webhook URL.

1. Workflow config (Edit Fields (Set)): sets 6 fields: finishedStateLabels, useDependencies, useTreeStructure…
2. Fetch task changes (Edit Fields (Set)): sets or maps fields
3. Split Out: splits a list into separate items
4. Filter: keeps only the items that match a condition
5. Check if task done (If): checks a condition and branches into true / false
6. Check if dependencies enabled (If): checks a condition and branches into true / false
7. Load dependencies for task (HTTP Request): calls an HTTP API
8. Check if tree structure enabled (If): checks a condition and branches into true / false
9. Aggregate: combines items into one
10. Check subtasks (If): checks a condition and branches into true / false

…plus 14 more steps. See the full node list below.

HTTP calls to: api.awork.com

Before you upgrade to n8n 3.0

Nodes used (8)

• HTTP Requestn8n-nodes-base.httpRequest
• Aggregaten8n-nodes-base.aggregate
• Edit Fields (Set)n8n-nodes-base.set
• Split Outn8n-nodes-base.splitOut
• Filtern8n-nodes-base.filter
• Ifn8n-nodes-base.if
• Webhookn8n-nodes-base.webhook
• Coden8n-nodes-base.code

From the author

Awork currently does not support a check for open subtasks or open dependencies when setting a task status to done. This workflow offers you a simple workaround to add this functionality to Awork and notifies users when triggered. Multiple configuration…

View the original on n8n.io → Check your own copy