monday.com External Integrations Don’t Duplicate

Email automations should duplicate. Not vanish completely.
Are monday.com integrations lost on board duplication? You’ve spent hours setting up the perfect monday.com board template. Gmail integration for client emails. Slack notifications for team updates. Outlook integration for meeting invites. You duplicate the board for a new project — and the integrations stop working. This problem compounds when you’re trying to auto-create project boards from CRM triggers, where reliable automation is essential.
Integration recipes come across grayed out until someone re-selects the account connection. Custom automations built with Gmail, Outlook or Slack blocks are gone (monday.com Help Center).
Those custom automations are missing from the Automation center on the duplicated board, and the grayed-out recipes send nothing until they’re reconnected.
Below: what monday.com copies, what it leaves behind, and a checklist to get every integration running on the new board.
Why monday.com Integrations Disappear on Board Duplication
Custom automations built with integration blocks (Gmail, Outlook, Slack) don’t survive when boards are duplicated, and integration recipes need their connection re-selected.
When you set up an integration on a monday.com board, the integration is tied to that specific board. Integrations typically require:
- Authentication (you logged in with your Gmail account)
- Configuration (which team members to notify, which email templates to use)
- Permissions (the integration has access to send emails on your behalf)
When you duplicate the board, monday.com copies:
- Columns
- Groups
- Views
- Automation and integration recipes that are turned on
- Integration connections (recipes appear grayed out until you re-select the connection)
- Custom automations with integration blocks (Gmail, Outlook, Slack — must be recreated)
- Connect Boards and Mirror column settings (reconfigure them on the new board)
That’s from monday.com’s articles on duplicating a board and templates.
Why This Happens
monday.com integrations are authentication-specific: each recipe runs through a connected account, and fields that hold remote data (a Slack channel, a Jira project) come from that account.
When the board is duplicated, monday.com copies turned-on integration recipes but not the account connection, so each one waits for you to re-select it. Custom automations built with integration blocks aren’t copied at all.
What Gets Lost
Common integrations affected:
- Gmail — automated emails to clients, team members, stakeholders
- Outlook — meeting invites, email notifications
- Slack — team notifications, status updates
- Twilio — SMS notifications
- Zapier/Make blocks — cross-tool automation
- Custom webhooks — external system integrations
The Broken Workflow
Here’s what happens when teams use integrations with template board duplication:
- Build template board with Gmail integration set up
- Configure automation: “When status changes to Sent, send email to client”
- Duplicate board for new project
- The Gmail automation is grayed out until the connection is re-selected — or gone, if it was a custom automation with a Gmail block
- Status changes, but no email is sent
- Client doesn’t get notified
- PM realizes the integration isn’t running, and has to reconnect or rebuild it on the new board
- Time wasted re-configuring integrations
What the Community Says
Users describe rebuilding Gmail, Slack and Outlook automations for every new project. monday.com’s duplication article documents the cause: custom automations with integration blocks must be recreated (monday.com Help Center). Like cross-board automations that break and webhooks that don’t transfer, integration loss is a systemic board duplication issue.
See BoardBridge Forms in Action
Book a free demo of BoardBridge forms for monday.com — live, with your data.
Book a Free DemoFree 30-minute call · No obligation
How to Get Integrations Running on a Duplicated Board
1. Reconnect Grayed-Out Integration Recipes
monday.com’s templates article gives the steps:
- Open the integrations: click the icon of the integrated app to the left of the board name; the Board automations tab of the Automation center opens.
- Find the grayed-out recipes: integration recipes that carried over from the original board are grayed out.
- Add to Board: click Add to Board on each recipe, then pick an existing connection or create a new one.
- Check the setup: fields without remote data keep their original setup; re-select channels, projects and other data from the connected tool.
Reconnected integrations appear under the name of the person who reconnected them. Use a shared team connection where you have one, so the setup doesn’t hang on one person’s account.
2. Rebuild Custom Automations With Integration Blocks
Custom automations that use Gmail, Outlook or Slack blocks don’t carry over at all, whether you duplicate the board or create it from a template. Keep a written list of them on the template (trigger, action, recipients) so each one can be rebuilt on the new board. More on automations that don’t carry over.
3. Plan Email Around a Connection
monday.com’s Send an email action needs a connected Gmail or Outlook integration on the account, so every email automation on a new board depends on a connection. The Connections tab of the Autopilot Hub lists every connection in the account; from there you can reconnect or delete one.
4. Reconfigure Connect Boards and Mirror Columns
Connect Boards and Mirror column settings aren’t carried over to the duplicate. Set them up again before relying on any automation that reads them.
5. Check Run History
Trigger each automation once and open its Run History. When an integration fails, monday.com shows a bell notification and a message in the Activity Log.
BoardBridge sends emails from a button on the item, with rich HTML, merged column values, CC/BCC, a custom sender name and reply-to. Wondering whether it fits your duplicated boards? Ask us.
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
Real-World Scenario: Event Confirmation Emails
An event management company uses email automations to notify clients when events are confirmed.
What breaks:
- The template board has a Gmail recipe: “When status changes to Confirmed, send an email to the client”
- A new event board is duplicated from it
- The Gmail recipe arrives grayed out, so confirming an event sends nothing
- Nobody notices until a client asks where their confirmation is
The fix:
- Right after duplicating, the PM opens the Board automations tab
- The grayed-out Gmail recipe gets Add to Board and the team’s connection
- A test item is set to Confirmed, and Run History shows the email went out
- Clients get their confirmations from the first event on
What Carries Over, and What to Do
| Part of the board | On duplication | What to do |
|---|---|---|
| Columns, groups and items | Copied (Structure & items) | Nothing |
| Automation recipes that are turned on | Copied | Turn on the ones you want copied before duplicating |
| Integration recipes that are turned on | Copied, grayed out | Add to Board and pick a connection |
| Custom automations with integration blocks | Not copied | Rebuild them |
| Connect Boards and Mirror columns | Settings not carried over | Reconfigure them |
| Column permissions | Copied | Nothing |
Post-Duplication Checklist
- Before duplicating: check that the template’s recipes are turned on; only those are copied. See also template settings lost on duplication.
- Duplicate: choose Structure & items (or structure only).
- Reconnect: open the Board automations tab and click Add to Board on each grayed-out integration recipe.
- Rebuild: recreate custom automations with Gmail, Outlook or Slack blocks from your list.
- Reconfigure: set up Connect Boards and Mirror columns again.
- Repoint: update any Zap, Make scenario or webhook that should watch the new board.
- Test: trigger each automation once and check Run History.
Who This Is For
This checklist matters most for teams who:
- Duplicate template boards for every new project, client or event
- Send client or team emails from Gmail or Outlook automations
- Post updates to Slack from board recipes
- Run Zapier, Make or webhook flows off a template board
Need a duplication checklist built into your templates? We can set one up when customizing monday.com for your workflow.
Stop Creating Duplicates
BoardBridge forms update existing items — no Enterprise plan, no workarounds, no duplicates.
See It In ActionFree 30-minute call · No obligation
Frequently Asked Questions
Why do Gmail and Outlook integrations disappear when duplicating a monday.com board?
Turned-on integration recipes are duplicated but appear grayed out until you click Add to Board and re-select the account connection. Custom automations built with Gmail or Outlook integration blocks do not carry over and must be recreated, as monday.com’s duplication article confirms.
Do cross-board automations survive monday.com board duplication?
monday.com’s duplication article says turned-on recipes are copied, but it doesn’t say what happens to a cross-board recipe’s target board; community reports say the copies keep pointing at the template’s boards. Open each cross-board recipe on the new board, change its target, and check Run History. Connect Boards and Mirror column settings also need reconfiguring.
How to duplicate monday.com boards with all automations intact, including email notifications?
Native monday.com duplication copies every turned-on automation and integration recipe, but custom automations with Gmail or Outlook blocks must be recreated, integration recipes need their connection re-selected, and community reports say cross-board references can still point to the template. Follow a post-duplication checklist: reconnect grayed-out recipes, rebuild custom integration automations, reconfigure Connect Boards and Mirror columns, then test each automation and check Run History.
What happens to webhook integrations like Zapier or Make when duplicating monday.com boards?
Webhook integrations from apps like Zapier or Make do not copy over during board duplication and remain unavailable on the new board. Unlike built-in integrations that may appear in ‘ghost’ status, third-party app integrations require full recreation: point each Zap or scenario at the new board, or create a new one.
Why are some automations missing after duplicating a monday.com board with 40+ recipes?
When duplicating boards with many automations (e.g., 44 recipes), monday.com’s duplication article says all turned-on recipes are duplicated except custom automations with integration blocks, so those, plus any automations that were turned off, are the usual gaps. Before duplicating, turn on the recipes you want copied; afterwards, compare the new board’s Automation center with the template’s and rebuild what’s missing.
Can I create monday.com board templates that retain external integrations after duplication?
monday.com template boards keep turned-on integration recipes, which need their connection re-selected, but lose custom automations built with Gmail, Outlook or Slack blocks; community reports say cross-board automations can keep pointing to the template. Integrations arrive turned off on the new board: reactivate each one by opening the recipe and resetting its connection.








