Automations for Dependent Tasks

Platform discussions
,
1

Hello, is there a way to use if only logic for Dependent task automations?

Here’s what I need….
Task B is Dependent on Task A

When Task A status is changed to done, update status of Task B to ready to start.

I have the automation set up to accomplish this. However, in some cases, Task B would already be marked done, or marked N/A if it doesn’t apply. However, when this automation runs, it removes where it was already marked as N/A or Done and moves it back to Ready to Start.

This can also cause problems if you do finish Task A, and for some reason have to go back and update the status, then it will re-trigger automations as well.

I need a way to be able to add if only the status is showing as not started. The automation is premade and doesn’t allow customization (unless I am totally missing something), and you can’t set up dependent column automations from scratch.

Any suggestions?

2

You’re not missing anything — the built‑in “Dependencies” recipes are pretty rigid and don’t support an “only if status is X” condition. They’ll always fire when the trigger happens, regardless of the current status of the dependent item.

To get the behavior you want (update B only if it’s still “Not Started”), you’ll need to stop relying on the premade dependency automation for status changes and instead:

  1. Use a regular “When status changes” automation, and

  2. Add a condition that checks the current status of the dependent item before updating it.

Since you can’t build custom recipes directly on the Dependencies column, the usual pattern is:

1. Link A and B with a Connect Boards / Mirror (or use your existing structure)

If A and B are on the same board:

  • Use a Connect boards column (or use the existing dependency link if one is already there), and

  • Add a Mirror column to bring Task B’s Status into Task A (or vice versa), so the automation has something it can “see” and check.

If they’re on separate boards, the same idea applies: connect and mirror the status.

2. Build a conditional automation

Use a custom automation something like:

When Status (of Task A) changes to Done
and only if Mirrored Status of Task B is Not Started
then change Status (of Task B) to Ready to Start

In monday’s builder, that’s typically:

  • Trigger:
    When status changes to Done

  • Condition:
    and only if {Mirrored Status of Task B} is Not Started

  • Action:
    change status of {Task B} to Ready to Start

This way:

  • If Task B is already Done or N/A, the condition fails and the automation does nothing.

  • If you change Task A’s status multiple times, it only updates Task B when B is still Not Started.

3. Disable / limit the premade Dependencies recipe

If you still have the original dependency automation enabled (the one that always sets B to Ready to Start when A is done), turn it off or adjust your setup so it’s no longer responsible for the status change. Otherwise it will keep overriding N/A / Done.