monday.com Automations Don't Carry Over to Duplicated Boards

You’ve built the perfect workflow. Your template board has 22 automations:

Status “Confirmed” → sends confirmation email to the client
Button “Send Forms” → emails 3 form links with team CC’d
Status “Shipped” → creates an item on the Logistics board
Gmail integration → notifies external vendors
Slack integration → pings the team channel
Cross-board trigger → updates the master Dashboard when milestones hit

You save it as a template. You duplicate it for Project #1. The Automations panel is missing some of them.

The automations that vanish are the custom ones built with Gmail, Outlook or Slack blocks, plus any that were turned off. Unless you know the rule, you won’t know which ones to rebuild.

Some Custom Automations Vanish When Boards Are Duplicated

Here’s what teams need when duplicating template boards:

All automations carry over to the new board
Email automations (Gmail, Outlook) remain functional
Cross-board automations update to reference the NEW boards (not the template boards)
External integrations (Slack, webhooks) transfer
Consistent behaviour — the same automations duplicate every time

What monday.com actually delivers:

monday.com’s duplication article (monday.com Help Center) says what does NOT carry over:

Automations that are LOST on duplication:

Custom automations using integration blocks — Gmail, Outlook and Slack blocks have to be recreated
Any automation toggled OFF — only turned-on recipes are duplicated

What DOES carry over:

All automation and integration recipes that are turned on (integration recipes need their account connection selected again)

Connect Boards and Mirror column settings aren’t carried over either. A 2023 staff forum reply (quoted below) also listed cross-board, custom and item-mapping recipes; the current article doesn’t.

The result: Automation loss that’s easy to miss. Teams that rely on email or Slack automations rebuild them on every duplicated board.

What monday.com Users Are Saying

Thread: Duplicate board not carrying ALL automations to the new duplicated board — September 2021 – June 2024 (3 years unresolved, 20+ replies) |⁠ Source: monday.com Community

“All recipes (automations) that has integration with ’email’…are not carrying to new duplicated board.” — Roni Raimundo, September 17, 2021

The user’s template board had 44 automations. After duplication: 39 automations. Five automations silently vanished.

Several users in the thread described this as a “HUGE time saver” if resolved, citing the risk of human error when manually recreating dozens of automations.

No monday.com staff response in this thread as of June 2024.

Thread: Email Automations Don’t Duplicate When the Board Duplicates — June 2022 – June 2024 (11 replies) |⁠ Source: monday.com Community

“I have a templated board for project managers and am now having to rebuild 10 automations on each PM’s board to ensure it works correctly.” — Jeanette, February 22, 2023

“so annoying to have to recreate the entire automation” — dk_NFroehlich, June 10, 2022

“one of the main reasons to make a ‘template’ is that custom automations with emails or slack notifications are fiddly to reproduce.” — Louise McKay, March 6, 2023

“Rewriting the all the automations 200 times is incredibly tedious.” — Aprel Dobson, February 9, 2024

monday.com staff (Juliette, June 2024) encouraged voting on feature requests. No fix offered. No timeline provided.

Thread: Duplicate integrations when duplicating a board — April 2020 – present (6 years unresolved, 20+ replies) |⁠ Source: monday.com Community

“when I’m duplicating a board that already has some automations & integrations set up, only the automations get duplicated [not integrations]” — pszymanska (Patrycja), April 21, 2020

“templates are kind of useless if they don’t duplicate integrations…it’s a major pain that we can’t make use of the integrations feature.” — JessS, August 20, 2020

“I have a webhook integration…it is not copying over. Would really love to see this at least be a ghost option!” — jailynnhoops, November 18, 2022

monday.com staff (ErickE) officially explained the root cause:

Integrations are “mapped directly to the Board ID” — ErickE-monday.com, May 14, 2020

That was 2020. Today monday.com duplicates turned-on integration recipes, which then need their account connection selected again; custom automations built with Gmail, Outlook or Slack blocks are the ones that don’t carry over (monday.com Help Center).

Thread: Automations not working properly when new board is created from template — June 2023 – November 2024 |⁠ Source: monday.com Community

“I created a template board…When I create a new board from the template, everything works fine. However, when she creates a new board from the template, none of the automated notifications work.” — misti4marketing (Misti Buckner), June 29, 2023

“I’m having the same issue… Is this something monday.com is working on?” — jstanko1982, May 10, 2024

monday.com staff (BiancaT) described the scope in 2023 (the current duplication article lists only custom automations with integration blocks):

“Automation recipes that include item mapping will not duplicate. Cross-board automation recipes will not duplicate. Custom recipes.” — BiancaT (Monday.com staff), July 3, 2023

Thread: Missing/Deleted automations — April – May 2024 |⁠ Source: monday.com Community

“I have a board with 180 automations (133 active) and on Friday a user mentioned to me that one of them wasn’t working…I have 21 automations for a specific process that just disappeared.” — rriker (Rusty Riker), April 9, 2024

“It appears that the missing automations have come back so I now have 2 automations triggering the same action.” — rriker, May 9, 2024

“We also found a missing automation, and cannot see who deleted it, why it was deleted, it cannot be recovered. Why wouldn’t this go in the recycle bin like everything else?” — Rach12, May 14, 2024

monday.com staff (BiancaT) said “restoring deleted automations is not something we typically support” Source: monday.com Community – Missing/Deleted automations thread but offered to investigate automations “randomly disappearing.”

Users have also reported automations disappearing from live boards.

Need help setting up new projects in monday.com?

Book a free 30-minute call with a certified monday.com partner.

Book a Free CallFree 30-minute call · No obligation

Why This Happens: Board IDs Are Hardcoded

monday.com automations reference boards by unique ID. When you create an automation like:

“When status changes to Done, create an item on the Production board”

monday.com stores:

Trigger: status_change on board 123456789
Action:  create_item on board 987654321

When you duplicate the board:

New board is created with ID 234567890
Automation is copied (if it was turned on)
Automation still says: create_item on board 987654321

The automation now points to the WRONG board. It creates items on the original template Production board, not the new project’s Production board.

For custom automations built with Gmail, Outlook or Slack blocks, it’s worse: they don’t copy at all. Integration recipes do copy, but need their account connection selected again.

How to Keep Your Automations When You Duplicate

There is no setting that copies everything, but this routine keeps the loss predictable (monday.com Help Center) (monday.com Help Center):

Turn on every automation you want copied. Only automations toggled On are included when boards and templates are duplicated.
Save each custom automation as a template from its three-dot menu, starting with the ones built with Gmail, Outlook or Slack blocks. Anyone in your account can then add it to another board.
Duplicate the board: structure only, structure and content, or structure, content and updates.
Select the account connection again on each integration recipe.
Add the saved templates for the custom automations that didn’t carry over, and point cross-board automations at the new project’s boards.
Test with one item and open each automation’s Run History.

If the process lives in the workflow builder, Duplicate workflow reuses the same logic on other boards without rebuilding it (monday.com Help Center).

Need help structuring your monday.com boards?

Book a free 30-minute call with a certified monday.com partner.

Book a Free CallFree 30-minute call · No obligation

Example: Duplicating a 45-Automation Event Template

Template boards:

Event Overview (15 automations)
Band Confirmations (8 automations)
Travel (12 automations)
Production (10 automations)

Total: 45 automations

When a new event project is created:

All 4 boards duplicated, with every automation turned on beforehand
Account connections selected again on each integration recipe
Saved automation templates added for each Gmail, Outlook or Slack custom automation
Every cross-board automation checked against the new boards
One test item run through each board

Turned-on recipes duplicate, but every Gmail, Outlook or Slack custom automation has to be added again on each new board, with the risk of missing one or misconfiguring a cross-board reference. Saved templates make that step faster, not automatic.

Templates Keep More Than Duplicates

1. Create Boards From a Template, Not by Duplicating

A saved template carries more than a duplicate. Automations that are turned on when the board is saved carry over to every board created from it, except custom recipes that use apps or integrations. Integrations that are turned on carry over too, but turned off: reactivate each one by opening the recipe and resetting the connection. Column values (including people in the People column, who aren’t notified), files and Dependency column links stay. Only the person who creates the board becomes its member, and the automations appear under their name.

2. Use Managed Templates on Enterprise

Managed templates (Enterprise; 20 included per account) keep instances in line with a master template. Published board automations and integrations apply to new instances but don’t sync to existing ones. Connect Boards, Mirror, Dependency and Button column settings aren’t supported when new columns transfer.

What Carries Over and What Doesn’t

Automation or setting	On duplication	What to do
Turned-on automation recipes	Duplicated	Check cross-board references
Turned-on integration recipes	Duplicated	Select the account connection again
Custom automations with Gmail, Outlook or Slack blocks	Not duplicated	Add them from a saved automation template
Automations turned off	Not duplicated	Turn them on before duplicating
Connect Boards and Mirror column settings	Not carried over	Reconnect them on the new board

Duplicate vs Template

Setting	Duplicate board	Create from template
Turned-on automation recipes	Copied	Carry over
Custom automations with integration blocks	Not copied	Not supported
Integration recipes	Copied, greyed out until reconnected	Carry over turned off; reset the connection
Connect Boards and Mirror settings	Not carried over	Not documented
Column values and People column	Copied with Structure & items	Carry over; people aren’t notified
Column permissions	Copied	Not documented
Board members	Not documented	Only the creator
Files and dependencies	Not documented	Stay attached and connected

Email Automations That Native monday.com Can’t Handle

Native monday.com email automations:

No CC on the standard Gmail/Outlook action (monday service’s Send new email block has CC/BCC)
No conditional CC
~ HTML bodies only in the New Automation Builder and workflow email blocks (the Integration blocks page still says Gmail can’t format text)
Limited column value insertion
Custom automations with Gmail/Outlook blocks don’t duplicate

BoardBridge emails: sent from a button, with rich HTML and item column values merged in, CC/BCC, a custom sender name and reply-to. Ask us how they fit your duplicated boards.

Cross-Board Recipes: What Breaks and Why Nobody Notices

Community reports say cross-board automations still reference template boards after duplication, so workflows fail silently.

When you set up a cross-board automation, it is tied to a specific target board, identified by its board ID. For example:

When Status changes to “Confirmed”, create item on Board ID: 987654321

When you duplicate the board, monday.com copies the automation rules that are turned on (monday.com Help Center). It doesn’t document what happens to the target-board reference; community reports describe the copy still pointing to:

Board ID: 987654321 (the original template board)

Instead of:

Board ID: 123456789 (the newly created board in the new project)

What Breaks

Typical cross-board automations on template boards:

“When Status = Confirmed, create item on Production board” → Still points to template Production board
“When Status changes, sync to CRM board” → Still points to template CRM board
“When item created, notify Logistics board” → Still points to template Logistics board

This breakage extends to all types of cross-board automation workflows, making template-based project creation unreliable.

When your new project board tries to run these automations, they:

Look for the target board (e.g., template Production board)
Create items on the wrong board
Sync data to the wrong CRM
Notify the wrong Logistics team

Your new project’s workflow is broken, and it’s easy to miss: the automations appear active with no error messages. Each automation’s Run History and Analytics show where it acted, but only if someone checks (monday.com Help Center).

The “Silent Failure” Problem

Because nothing errors, teams often find out only when items appear on the wrong board.

monday.com doesn’t document an option to remap target boards on duplication. Combined with issues like external integrations not duplicating and webhook subscriptions not transferring, board duplication creates multiple automation failures.

Cross-Board Automations That Work After Duplication

Native monday.com:

Automation: “When status changes, create item on Production board”
After duplication: Creates items on the ORIGINAL template Production board (broken)

The fix:

Open each cross-board automation on the new board and pick the new project’s Production board
Or add it fresh from a saved automation template, choosing the new boards as you set it up

Why? Automations reference boards by ID, so a copied automation keeps the template’s board until you change it.

How to Fix Cross-Board Recipes After Duplicating

List the recipes: open the new board’s Automations page and note every recipe that names another board.
Repoint each one: open the recipe and change its target board to the new project’s board.
Reconfigure connections: set up the Connect Boards and Mirror columns again, since their settings aren’t carried over.
Recreate integration recipes: custom automations with integration blocks (Gmail, Outlook, Slack) don’t duplicate and must be rebuilt.
Test: trigger each recipe once and check its Run History to confirm it acted on the new board.

Set Up New Projects So Fewer Recipes Break

Instead of duplicating boards one at a time, save the project’s boards as one template: the Template Editor can save an entire workspace as a template, with up to 10 components on Pro and 30 on Enterprise (Standard templates hold 1). monday.com’s own multi-board templates install two or three connected boards with pre-set automations together in a folder. monday.com doesn’t document whether a custom template’s cross-board recipes point to the new boards, so test with a first project. More on this in auto-duplicating template boards. To create the whole project folder from a CRM deal, see auto-creating a project folder with boards from a CRM trigger, and to fill the new boards with deal data, see pre-populating new project boards with CRM data. If new projects start as requests, building an automated project intake board covers the form and routing that come first.

Wondering whether BoardBridge fits your project setup? Ask us.

Limitations You Should Know

Templates don’t update past projects. If you add an automation to a template after projects have been created, it only reaches boards duplicated later. Workarounds built on template automations carry their own risk: see managed template editor changes that break workarounds.

Deleted automations are hard to recover. monday.com staff say restoring deleted automations is not something they typically support, so keep a list of each template’s automations.

Integration recipes need a connection. Each duplicated integration recipe waits for its account connection before it runs.

Not sure which route fits your boards? Ask us, or have our monday.com customization team set up your templates.

Need Help With Your monday.com Setup?

TaskRhino has implemented monday.com for 110+ teams. Get a free consultation.

Schedule Free ConsultationFree 30-minute call · No obligation

Frequently Asked Questions

11 questions

Why do integration-based automations (Gmail, Outlook, Slack) fail to carry over when I duplicate a board, even though recipe automations do?

monday.com’s duplication article says custom automations built with Gmail, Outlook or Slack blocks must be recreated on the new board; they are tied to a connected account. Turned-on recipe automations (status changes, button triggers) and integration recipes are duplicated, though integration recipes need their account connection selected again.

I created a board template with 22 automations but only 15 appeared when I created a new board from that template—which automation types are most likely to be missing?

Custom automations built with Gmail, Outlook or Slack blocks, and any automation that was turned off, are the ones monday.com doesn’t duplicate. Users also report cross-board automations that carry over but need their column mappings and board references checked.

Is there a native monday.com way to copy automations between existing boards without duplicating the entire board structure?

Yes. A custom automation can be saved as a template that anyone in the account can add to another board, and a workflow can be reused on other boards with Duplicate workflow. Duplicating the whole board also copies every turned-on automation except custom automations with Gmail, Outlook or Slack blocks.

Why would I lose 5-7 automations (like in the scenario above where 22 became 15) even when duplicating a board that contains only recipe automations?

monday.com’s duplication article says all turned-on automation recipes are duplicated, so a board with only recipe automations shouldn’t lose any. If some are missing, check whether they were turned off on the original or were custom automations with integration blocks; users also report cross-board recipes whose board references need checking.

How do I avoid rebuilding missing automations after duplicating a board?

Turn on every automation before you duplicate, save each Gmail, Outlook or Slack custom automation as a template, then add those templates to the new board and select the account connection again on each integration recipe. Check cross-board automations point at the new boards, and test with one item.

If I need the same 22 automations across 10 project boards, what’s the fastest approach given monday.com’s current limitations?

Build the template board with recipe automations, save each Gmail or Slack custom automation as an automation template, duplicate the board for each project, then add the saved templates to each board. It takes a few steps per board but is predictable; if the process is a workflow, Duplicate workflow reuses it.

Why do monday.com cross-board automations reference the original template board IDs after duplicating a board?

Community reports describe duplicated cross-board automations keeping the original target board, so they point to the template instead of the new board. monday.com’s duplication article doesn’t say how target-board references are handled, so check each cross-board recipe after duplicating.

How to fix broken cross-board recipes after monday.com board duplication without recreating them?

Open each cross-board automation on the new board and change its target board to the new project’s board; monday.com doesn’t document a bulk remap. Then trigger each recipe once and check its Run History to confirm it acted on the new board. To cut the work, build new projects from a multi-board template and test whether its recipes point to the new boards.

What happens to Connect Boards columns in cross-board automations after monday.com board duplication?

Connect Boards column settings aren’t carried over when a board is duplicated, so the new board’s links have to be set up again, and Mirror column settings need reconfiguring too. Point each Connect Boards column at the new project’s boards, then rebuild the mirrors.

Is there a native monday.com setting to remap cross-board automation board IDs on duplication?

Not a documented one: monday.com’s duplication article doesn’t mention remapping target boards, so you edit each recipe. For many boards, save the project’s boards as one template and test whether its recipes point to the new boards.

How to retain subitem settings in board views after duplicating a monday.com template?

monday.com’s duplication docs don’t say whether subitem settings in views like Gantt or Kanban carry over, so check them after duplicating. Workarounds include manually reapplying settings or using the monday.com SDK for custom view apps.