Automation Recipes

Custom triggers and actions that plug straight into your monday.com workflow builder. New recipes added regularly — driven by the community.

Triggers

— start automations when something happens

When a column matches any of these values

OR Status Trigger

Fire one automation when a status matches any of up to 3 values. No more duplicate automations.

Use Cases

  • Fire when a task is 'Blocked', 'On Hold', or 'Cancelled' — one automation instead of three
  • Capture all negative sales outcomes ('Lost', 'Disqualified', 'Churned') in a single workflow
  • Group urgent support statuses ('Urgent', 'Critical', 'P1') for a single escalation path

Example

A project manager needs to be notified when tasks hit any problem state. Instead of creating separate automations for 'Blocked', 'On Hold', and 'Needs Review', set up one OR Status Trigger that fires for all three and sends a single Slack notification.

When a numeric formula column goes above or below a number

Formula Column Threshold Trigger

Watch any formula column and trigger when the calculated value crosses a threshold you set.

Use Cases

  • Alert finance when a project's calculated spend exceeds 80% of budget
  • Flag sales reps when their monthly total drops below 50% of quota
  • Trigger reorder workflows when inventory formula drops below minimum stock levels

Example

Your board has a formula column calculating total spend as a percentage of budget. Set the threshold to 80 — when any project crosses that line, automatically change its status to 'At Risk' and notify the finance team.

When a formula column's calculated value changes

Formula Column Change Trigger

React to any change in a calculated field — scores, ratings, totals, anything.

Use Cases

  • Log changes to a calculated risk score on an audit board for compliance tracking
  • Notify account managers instantly when a customer tier recalculates from spend data
  • Keep a master dashboard synced whenever a project health formula updates

Example

A customer health score is calculated from usage data, support tickets, and renewal date. Whenever the formula result changes, the trigger fires and creates a log entry on a separate audit board — building an automatic history of account health over time.

When ALL subitems reach a specific status

All Subitems Reach a Status Trigger

Works with any custom status label, not just 'Done'. Fire on the parent item when every subitem hits your target.

Use Cases

  • Auto-approve an expense report when every line item reaches 'Approved'
  • Mark a sprint as complete when all stories reach 'Accepted' (not just 'Done')
  • Release a product batch when all QA check subitems reach 'Passed'

Example

A content publishing board has parent items for each blog post, with subitems for 'Draft', 'Edit', 'SEO Review', and 'Images'. When ALL subitems reach 'Published', the parent automatically moves to 'Ready to Go Live' — no manual checking required.

Actions

— do something when a trigger fires

Roll up subitem timelines to the parent item

Sync Parent Dates from Subitem Timelines

Automatically sync timeline, start date, and end date columns on the parent from all subitem date ranges.

Use Cases

  • Keep project Gantt bars accurate as phase subitems shift dates
  • Auto-calculate sprint start and end dates from story timelines
  • Sync event planning timelines from individual task subitems

Example

A project board has parent items for each deliverable with phase subitems. When a subitem's timeline shifts (e.g., design takes a week longer), the parent's Gantt bar, start date, and end date all update automatically — no manual adjustment needed.

When a status changes here, update the matching item in a connected board

Update Status in Connected Board

Keep statuses in sync across connected boards without manual updates.

Use Cases

  • Automatically start onboarding when a deal moves to 'Closed Won' on the sales board
  • Push 'Ready for QA' status from Development to the QA team's board
  • Update delivery tracking when a request is approved on the intake board

Example

Your Sales board is connected to a Client Onboarding board via a Connect Boards column. When a deal's status changes to 'Closed Won', the linked onboarding item automatically updates to 'Ready to Start' — the onboarding team sees it instantly without anyone switching boards.

Keep a status in sync between this board and a connected board in both directions

Sync Status Bidirectionally

Two-way status sync with built-in loop prevention. Both boards always reflect the same state.

Use Cases

  • Keep Sales and Operations boards in sync when either team updates a shared status
  • Sync project status between HQ and regional office boards regardless of who updates
  • Bridge Development and Product boards where both teams update feature progress

Example

Marketing and Engineering both track campaigns on separate boards. Marketing marks content as 'Ready', Engineering marks it 'Implemented', and either side can update to 'Live'. Changes propagate in both directions automatically — with built-in loop prevention so automations don't cascade infinitely.

Read a mirror column and write its value to a real column

Copy Mirror Column Value to Editable Column

Unlock mirror column data for formulas, filters, and automations by copying it to an editable column.

Use Cases

  • Use a mirrored customer spend value in local formulas to calculate commissions
  • Copy a mirrored project status into a filterable column for reliable board views
  • Make mirrored deadlines available as automation triggers for reminders

Example

Your board mirrors a customer's total annual spend from the CRM board. That mirror column is read-only — you can't use it in formulas. This action copies the value to a regular Numbers column, so you can now calculate commission rates, discount tiers, and account scoring using that data.

Got a recipe idea?

Community Cookbook is driven by the people who use it. If monday.com can't do something you need, tell us — we'll build it. The recipe list keeps growing but the price never goes up.