Mirror Column Recipes
Purpose: Move data between Mirror columns and normal, editable columns in both directions.
Problem solved: Mirror column values are read-only and can’t normally be used to update other columns or trigger further automations. These recipes let you “unlock” that data.
Recipes in this group include:
- When a column changes, take the value of the Mirror column and set into this column
- When a person is assigned, take the value of the Mirror column and set into this column
- When status changes to something, take the normal column value and add in Mirror column
- When a column changes, take the normal column’s value and add in Mirror column
- When item is moved to a group, take the value of the Mirror column and set into this column
- When an item is created, take the value of the Mirror column and set into this column
- When a subitem’s Mirror column change, copy this value into subitem column
- When a column changes, copy the value from a Mirror column to a Target Person column
- When an update is created, copy the update to all items in Mirror column
- When Mirror column change, copy its value into this column
- When column changes, copy the Connect Boards column value into normal column
Use Case (Sales & CRM)
A sales team mirrors the “Deal Stage” from a Deals board onto a Client Onboarding board. Since Mirror columns are read-only, the onboarding team can’t trigger a “Welcome Email” automation directly from that mirrored stage. Using the recipe “When status changes to something, take the normal column value and add it into a Mirror column“ (or the reverse copy recipe), the mirrored deal stage is copied into a real Status column on the onboarding board, which then triggers the welcome automation automatically.
Number & Status Mirror Recipes
Purpose: Specifically handle Mirror columns that mirror Number or Status column types, since these need extra setting mapping (matching mirrored statuses/numbers to real column values).
Problem solved: A mirrored Status or Number often can’t be filtered, grouped, or used in further automation the same way a native Status/Number column can. These recipes convert the mirrored value into a real, working column.
Recipes in this group include:
- When email changes, take the value of number mirror column as per this column setting and set it into this number column
- When status changes to something, take the value of number mirror column as per this number column setting and set it into this number column
- When column changes, take the value of number mirror column as per this number column setting and set it into this number column
- When person is assigned, take the value of number mirror column as per this number column setting and set it into this number column
- When email changes, take the value of status mirror column as per this status setting and set it into this status column
- When status changes to something, take the value of status mirror column as per this status setting and set it into this status column
- When a person is assigned, take the value of status mirror column as per this status setting and set it into this status column
Use Case (Manufacturing / Inventory)
A production board mirrors “Stock Quantity” (a Number column) from a Warehouse board. The team wants to trigger a low-stock alert, but native automations can’t read mirrored numbers. Using “When a column changes, take the value of the number mirror column and set it into this number column“, the mirrored stock count is copied into a real Number column, enabling a “Notify Purchasing Team” automation when stock drops below a threshold.
Formula Column Recipes
Purpose: Use the result of a Formula column to update the item name, another column, a Mirror column, or a Person column — something monday.com does not support natively.
Problem solved: Formula columns are calculated automatically but can’t act as an automation trigger or feed data into other columns by default. These recipes solve that limitation.
Recipes in this group include
- When column changes, copy the value from a Formula column to the item name
- When column changes, copy the value from a Formula column to a Person column
- When column changes, get the value of Formula column and put into Mirror column
- When a person is assigned, get the value of Formula column and put it into Mirror column
- When status changes to something, apply a Formula and set the result to target column
- When an item is created, apply a Formula and set the result into a target column
- When a date arrives, apply a Formula and set the result into a target column
- When button clicked, get the calculated value of the Formula column and set the result into a column
- When a column changes, get the calculated value of the Formula column and set the result into a column
- When an item is moved to a group, get the calculated value of the Formula column and set the result into a column
- When a date arrives, get the calculated value of the Formula column and set the result into a column
- When a Formula column changes, apply its value to the target column
- When a column changes, get the value from a selected Formula column at item level and set it in a target subitem column, where the subitem name contains specific text
- When a subitem status changes, take the Subitem Formula column value and add it into a Subitem column
Use Case (Finance / Project Costing)
A finance team uses a Formula column to auto-calculate “Total Project Cost” (Hours × Rate). They want this result to update the item’s Status to “Over Budget” automatically. Since Formula columns can’t trigger actions natively, the recipe “When a column changes, get the calculated value of the Formula column and set the result into a column“ pushes the formula result into a working column, which then drives the Over Budget status update.
Currency Conversion Recipes
Purpose: Automatically convert an amount from one currency to another and store the converted value in a target column.
Problem solved: monday.com doesn’t natively convert currency values between columns. Teams working with international clients, vendors, or multi-currency budgets previously had to calculate conversions manually. This recipe automates it.
Recipe in this group includes:
- When status changes to something (or when a column changes), convert the amount in the Source amount column from the Source currency to the Target currency, and store the converted result in the Target amount column
Use Case (Import/Export & International Vendors)
A procurement board tracks vendor invoices in USD, but the finance team needs everything reported in INR. Using the recipe “Convert the amount in the Source amount column from the Source currency to the Target currency and store it in the Target amount column“, every new invoice entered in USD is automatically converted and stored in INR — no manual calculation needed.
Normal Column-to-Column Copy Recipes
Purpose: Copy a value from one column directly to another column of the same type.
Problem solved: Useful for duplicating data across columns without manual re-entry, especially when restructuring boards or syncing duplicate fields.
Recipe in this group includes:
- When a column changes, copy the value from Column 1 to Column 2 (both columns must be of the same type)
Use Case (HR / Recruitment)
An HR board restructuring requires “Candidate Email” data to also appear in a newly added column for a different view. Instead of manually re-entering data for hundreds of candidates, “When a column changes, copy the value from Column 1 to Column 2“ handles it instantly and keeps both columns in sync going forward.
Board Connect (Cross-Board Matching) Recipes
Purpose: Automatically connect matching items across two different boards based on shared column values.
Problem solved: Manually connecting items across boards is time-consuming and error-prone, especially with large data sets. This recipe finds and links matching records automatically.
Recipe in this group includes:
- When a column changes on Board A, connect the item from Board B with the item from Board A where Column A1 matches Column B1 AND Column A2 matches Column B2 — the matched items are automatically linked in the Connect column of Board A
Use Case (Real Estate)
A “Properties” board and a “Buyers” board need to be linked whenever a Buyer’s preferred location and budget match a Property’s location and price. The recipe “Connect item from Board B with item from Board A where Column A1 matches Column B1 AND Column A2 matches Column B2“ automatically links matching buyers to matching properties without manual searching.
Autogenerated & Item ID Recipes
Purpose: Pull system-generated values (like Autogenerated column values or Item ID) into a usable column, such as a text column.
Problem solved: Autogenerated and Item ID values are normally locked and can’t be referenced elsewhere. These recipes make that data usable in reports, text fields, or other automations.
Recipes in this group include:
- When a column changes, get the value of the Autogenerated column and add it into this column
- When status changes to something, get the value from the Item ID column and add it into a text column
- When a column changes, get the value from the Item ID column and add it into a text column
Use Case (Logistics / Shipment Tracking)
A logistics team needs the system-generated Item ID visible in a Text column so it can be included in customer-facing shipment reports (since Item ID columns can’t be exported or referenced directly). The recipe “When a column changes, get the value from the Item ID column and add it into a text column“ solves this by copying the ID into a usable text field.
Subitem & Parent Item Summary Recipes
Purpose: Pull summary data calculated at the parent-item level (based on subitems) into a usable column.
Problem solved: Parent item “Summary” columns aggregate subitem data automatically, but that summary can’t normally be reused elsewhere. These recipes let you extract and repurpose that summary value.
Recipes in this group include:
- When a subitem is created, take the value of the Summary on Parent Item and set into column
- When a column changes, take the value of the Summary on Parent Item and set it into a column
- When a column changes, take the value of the Summary on Parent Item and set it into a number column
Use Case (Construction / Project Management)
A construction board tracks subitems for each task (labor cost, material cost). The Parent Item automatically calculates a “Total Cost” Summary column from these subitems. The team wants this total available in a regular Number column for reporting dashboards. The recipe “When a column changes, take the value of the Summary on Parent Item and set it into a number column“ makes this possible.
Date-Triggered Recipes
Purpose: Trigger data movement automatically when a specific date arrives, rather than waiting for manual changes.
Problem solved: Keeps time-sensitive data (deadlines, renewal dates, scheduled reviews) automatically
Recipe in this group includes:
- When date arrives, take the normal column value and add it into a Mirror column
Use Case (Legal / Contract Management)
A legal team tracks contract renewal dates. When the renewal date arrives, they want the mirrored “Client Status” value copied into an internal tracking column automatically, without anyone checking the board manually. The recipe “When a date arrives, take the normal column value and add it into a Mirror column“ automates this.
synced without someone needing to remember to update it.
Recipe in this group includes:
- When date arrives, take the normal column value and add it into a Mirror column
Use Case (Legal / Contract Management)
A legal team tracks contract renewal dates. When the renewal date arrives, they want the mirrored “Client Status” value copied into an internal tracking column automatically, without anyone checking the board manually. The recipe “When a date arrives, take the normal column value and add it into a Mirror column“ automates this.
Basic Value-Set Recipes
Purpose: Set a fixed or default value into a column automatically when an item is created.
Problem solved: Removes the need to manually fill in default values every time a new item is added to a board.
Recipe in this group includes:
- When an item is created, set a specific value into a column
Use Case (Customer Support)
Every new support ticket created on a board should automatically start with a “Priority: Normal” status instead of being blank. The recipe “When an item is created, set a specific value into a column“ ensures every new ticket has a default value without manual entry.
