OR Status Trigger: Fire One Automation for Multiple Status Values

If you've ever built automations in monday.com, you've hit this wall: the native status trigger only fires when a column matches one specific value.

Want to fire the same automation when a task is "Blocked", "On Hold", or "Cancelled"? That's three separate automations doing the exact same thing. Three to maintain. Three to update when the downstream action changes. Three chances for something to fall out of sync.

The Problem

Here's a common scenario. You have a project board with a Status column. You want to send a Slack notification whenever a task hits a problem state — "Blocked", "On Hold", or "Cancelled".

With native monday.com, you'd need:

• Automation 1: When status changes to "Blocked" → send notification
• Automation 2: When status changes to "On Hold" → send notification
• Automation 3: When status changes to "Cancelled" → send notification

That's manageable for three values. But what about boards with five or six problem states? Or boards where different teams define their own status labels? It gets messy fast.

The Solution: OR Status Trigger

Community Cookbook's OR Status Trigger lets you define up to 3 status values and fires if the column matches any of them.

The recipe sentence:

"When a column matches any of these values"

One automation. One set of downstream actions. Zero duplication.

How to Use It

1. Install Community Cookbook from the monday.com marketplace
2. Create a new automation on your board
3. Select the OR Status Trigger as your trigger
4. Choose your Status column
5. Set up to 3 values to watch for
6. Add your actions (notifications, status changes, item creation — anything)

Real-World Use Cases

Project Management

Fire when a task is either "Blocked", "On Hold", or "Needs Review" — all situations where a project manager needs to step in.

Sales Pipeline

Trigger when a deal moves to "Lost", "Disqualified", or "Churned" — capturing all negative outcomes in one automation that logs the loss and notifies the sales lead.

HR Onboarding

React when a new hire's onboarding task is "Waiting on IT", "Waiting on HR", or "Waiting on Manager" — all blockers that need escalation.

Support Tickets

Group "Urgent", "Critical", and "P1" statuses together so high-priority tickets always trigger the same escalation workflow regardless of which label was used.

Why This Matters

It's not just about saving time setting up automations. It's about reducing maintenance overhead. When you need to change the notification message or add a new downstream action, you update one automation instead of three. That's fewer places for things to break and fewer things to remember when your workflow evolves.

Frequently Asked Questions

How many status values can I match with the OR Status Trigger?+

Does this work with any status column in monday.com?+

Can I combine this trigger with native monday.com actions?+

What's the difference between this and creating multiple native automations?+