Monday.com Status Changes Not Fully Working

What are you trying to achieve?

I am creating an equipment checkout form in Monday.com.

It’s supposed to work like this:
My Make.com scenario watches for every new “Created” item on a specific Monday.com board, pulling each request’s gear name, start/end datetime, and status. As soon as a new reservation appears, it queries all other items still marked “Requested” for that same gear, then loops through them: parsing both their start and end strings into date objects and checking whether the new request’s start is before an existing reservation’s end and its end is after that reservation’s start. If any overlap is detected, a flag is set. Finally, a conditional step updates the new item—setting its status to Unavailable when conflicts exist or Reserved when there are none. This automated flow enforces that no two bookings can overlap, all without any manual intervention.

Steps taken so far

I feel a simple router and filter should identify the conflicts, mark them as Unavailable in Monday, and then change the status of the remaining new items to Reserved for non-conflicts. But it’s only identifying the conflicts and changing their status.

I don’t exactly know what I’m doing.

1 Like

Hi,

Can you share screenshots or blueprints of your scenario?

Hi @CIC-notrab
A good way to handle this is to set up the ‘first route’ to check for conflicts and mark the item as ‘Unavailable’ if there’s an overlap. Then, use a ‘fallback route’ (without filters) that will run ‘only if the first route doesn’t match’ — this one can mark the item as ‘Reserved’. That way, only non-conflicting requests get marked as Reserved automatically.

Best regards,
Msquare Automation
Platinum Partner of Make
@Msquare_Automation

1 Like