Check dependencies before completing Awork tasks (Workaround)

Nodes

3b9f1b78-6b80-4575-aa6c-9669870003891c04dd23-ae91-4772-b6db-e7ce81fc2f71083a55c9-df56-4154-959f-52737890cad09dd572aa-e531-4ffe-a66c-58ac7003ac5d+1

Categories

Tags

Created by

GrGregor

Last edited 39 days ago

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 options available.

How it works

  • Triggered via Awork Webhook call on status change of tasks
  • If task is marked as done, subtasks and/or dependent tasks are checked for their status
  • If unfinished tasks are found, a status rollback to previous status is performed and user gets notified

Set up steps

  • Add webhook call to Awork
  • Configure Awork API credentials
  • Set up workflow configuration via setup node, e.g. user notification text, restrict to subtasks/dependency checks etc.

New to n8n?

Need help building new n8n workflows? Process automation for you or your company will save you time and money, and it's completely free!