monday.com Custom Automations Don’t Carry Over to Duplicated Boards

meta_description: “monday.com automations vanish on board duplication — email, Slack, cross-board rules lost. Learn why and how BoardBridge preserves all workflow rules.”

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. Automations panel shows 15 automations. Seven are missing.

You duplicate it again for Project #2. This time, 13 automations show up. Nine are missing.

Different automations vanish each time. You have no idea which ones will survive.

Welcome to monday.com’s automation duplication lottery.

Boards Pain Point #10: 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 behavior — the same automations duplicate every time

What monday.com actually delivers:

Monday.com’s official documentation lists exactly what does NOT carry over:

Automations that are LOST on duplication:

1. Custom recipes using integration blocks — Gmail, Outlook, Slack automations are stripped entirely
2. Cross-board automation recipes — automations that reference other boards do not duplicate
3. Custom recipes — any automation with custom conditions or multi-step logic
4. Automations with item mapping — automations that map column values between items
5. Any automation toggled OFF — even simple automations are lost if they’re inactive

What DOES carry over:

• Regular status-based automations (if toggled ON)
• Simple notification automations (monday.com notifications only, not email)
• Basic same-board recipes

The result: Unpredictable automation loss. Teams report 5-15 automations vanishing per duplication. At scale, this is untenable.

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.

Multiple organizations 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

Integrations are hardcoded to specific board IDs. When boards are duplicated, integrations cannot follow because they reference the old board ID.

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) officially confirmed the scope of what fails:

“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.”

Even on live boards (not duplicated), automations vanish unpredictably.

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 sometimes copied (if it’s “simple” enough)
• 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 email/Slack/webhook integrations, it’s worse: they don’t copy at all. Monday.com strips them during duplication.

How BoardBridge Solves This

BoardBridge uses an entirely different architecture: workflow rules are stored externally in a database, not embedded in monday.com’s automation engine. Source: BoardBridge Architecture Documentation

When you set up a workflow rule like:

“When status changes to Confirmed, send email with CC group”

BoardBridge stores:

“json { "trigger": "status_change", "boardType": "confirmations_board", "column": "status", "value": "Confirmed", "action": "send_email", "emailTemplate": "confirmation_email", "ccGroup": "production_team", "recipientColumn": "email" } “

Notice: The board is referenced as "confirmations_board" — a logical name, not a monday.com board ID.

When a New Project Is Created

After all template boards are duplicated, BoardBridge’s automation cloning workflow executes:

Step 1: Fetch All Template Workflow Rules

Query the database for all workflow rules associated with the template boards.

Step 2: Build Board ID Mapping

Create a lookup table:

“ template_confirmations_board (ID: 123456) → project_confirmations_board (ID: 789012) template_production_board (ID: 234567) → project_production_board (ID: 890123) template_travel_board (ID: 345678) → project_travel_board (ID: 901234) “

Step 3: Clone Each Rule with Board ID Remapping

For each workflow rule, create a copy where every board ID reference is updated. Source: BoardBridge Board ID Remapping System

Original (template): “json { "trigger": "button_click", "boardId": "123456", "action": "create_item", "targetBoardId": "234567" } “

Cloned (project): “json { "trigger": "button_click", "boardId": "789012", // NEW confirmations board "action": "create_item", "targetBoardId": "890123" // NEW production board } “

Step 4: Register Webhooks

For each new project board, register a webhook with monday.com:

“graphql mutation { create_webhook( board_id: 789012, url: "https://api.boardbridge.io/webhooks/monday", event: "change_column_value" ) } “

The webhook ensures BoardBridge receives real-time notifications when triggers fire (status changes, button clicks, etc.).

Step 5: Activate All Cloned Rules

Mark all cloned workflow rules as active. The new project boards are now fully wired.

The Result

Every workflow rule from your template boards is replicated on the new project boards:

• ✅ Status changes trigger emails
• ✅ Button clicks send forms
• ✅ Cross-board triggers create items on the CORRECT new boards
• ✅ CC groups work
• ✅ Conditional email templates work
• ✅ Multi-step workflows execute correctly

Zero manual automation rebuilding.

Real-World Example: 45 Workflow Rules Cloned Automatically

Template boards:

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

Total: 45 workflow rules

When a new event project is created:

1. All 4 boards duplicated
2. All 45 workflow rules cloned
3. Every board ID reference remapped to the new boards
4. Webhooks registered on all 4 new boards
5. All rules active

Manual effort: 0 minutes

With native monday.com: 30-45 minutes to rebuild 45 automations by hand, plus the risk of missing one or misconfiguring a cross-board reference.

Annual savings (at 60 projects/year): 30-45 hours returned to actual work

What Gets Cloned

BoardBridge clones all these workflow rule types:

Status Change Triggers:

• Status changes → send email
• Status changes → create item on another board
• Status changes → update status on another board
• Status changes → conditional email template switching

Button Click Triggers:

• Button → send email with form links
• Button → update multiple status columns
• Button → create item on another board

Cross-Board Triggers:

• Item created on Board A → create item on Board B
• Status changes on Board A → update item on Board B

Email Features:

• Recipient from column value
• CC groups (named email address lists)
• Conditional CC (add recipients based on column data)
• Dynamic subject lines
• Rich text body with column value variables
• File attachments

Conditional Logic:

• If dropdown = “Outbound” → Template A, else Template B
• If status = “Confirmed” AND type = “Band” → CC band coordinator

Email Automations That Native Monday.com Can’t Handle

Native monday.com email automations:

• ❌ No CC recipients
• ❌ No conditional CC
• ❌ Plain text only (no formatting)
• ❌ Limited column value insertion
• ❌ Gmail/Outlook integrations don’t duplicate

BoardBridge email automations:

• ✅ CC groups on every email
• ✅ Conditional CC based on item data
• ✅ Rich text HTML formatting
• ✅ 20+ column values in email body
• ✅ All email rules cloned and remapped automatically

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)

BoardBridge:

• Automation: “When status changes, create item on Production board”
• After duplication: Creates items on the NEW project’s Production board (correct)

Why? Board ID remapping. The system knows which template board maps to which new project board and updates all references automatically.

Limitations You Should Know

Migration required. To use automation cloning, workflow rules must be defined in BoardBridge’s system. Native monday.com automations are not cloned (they follow monday.com’s standard duplication behavior).

Webhooks required. BoardBridge monitors boards via webhooks. If webhooks are disabled in your workspace (rare Enterprise security policy), the system cannot receive real-time triggers.

Retroactive sync not supported. If you add a new automation to a template after projects have been created, it only applies to future projects. Past projects are unaffected.

See It In Action

Stop Rebuilding Automations Every Time You Duplicate a Board

Losing automations on every board duplication means teams either:

• Manually rebuild email, Slack, and cross-board automations (hours per project)
• Accept reduced functionality on duplicated boards (broken workflows at scale)
• Keep automations on a master board and don’t duplicate it (defeats the purpose of templates)

At 50 projects/year with 15-40 automations per template, rebuilding is unsustainable.

BoardBridge preserves all workflow rules — email automations, cross-board triggers, conditional logic — and clones them with automatic board ID remapping. Every duplicated board is a perfect replica of your template, with all automations fully functional.

Ready to keep your automation workflows intact? Book a free 30-minute demo: https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone

Related Articles

• Why monday.com Template Board Settings Are Lost on Duplication — Comprehensive overview of what disappears when boards duplicate
• How to Auto-Duplicate Multiple Template Boards — Full workflow that includes automation cloning
• monday.com Cross-Board Automation Limitations & Solutions — Why cross-board automations are particularly fragile