monday.com Webhook Subscriptions Don’t Transfer on Duplication

Webhook automations should work. Not fail silently.

Are monday.com webhooks lost on board duplication? When you duplicate a monday.com board, turned-on integration recipes (including Webhooks integration recipes) are duplicated, but webhooks your own app or script registered through the API are tied to the original board’s ID, and monday.com doesn’t document them carrying over. The new board may have no active webhook listeners for your external system, so automations that depend on webhooks silently fail until someone manually re-registers them. This is particularly problematic when automating project creation from templates, where webhook-driven workflows are critical.

This is a critical scalability problem for teams using external automation platforms, custom integrations, or any system that listens for monday.com board events via webhooks.

Below: why it happens, and how to get every new board sending events again.

Why Webhooks Don’t Transfer on Board Duplication

API-registered webhook subscriptions aren’t documented to carry over when boards are duplicated, requiring manual re-registration on every new board.

Webhooks work by creating active subscriptions tied to specific board IDs. Source: monday.com Developer Docs – Webhooks When monday.com duplicates a board, it copies:

• Columns
• Groups
• Views
• Turned-on automation and integration recipes
• API-created webhook subscriptions (not documented to transfer)

A Webhooks integration recipe on the board (“when an item is created, send a webhook”) is copied with the other turned-on recipes, but a webhook subscription your app created through the API stays tied to the original board.

How Webhooks Actually Work

When you register a webhook on a board:

When you duplicate the board to board ID 111111111:

What Gets Lost

Webhooks to external systems that disappear:

• Make — automation platform webhooks stop receiving events
• Zapier — integration webhooks go silent
• Custom apps — your own integration servers stop receiving notifications
• Pabbly Connect — webhook automation platform loses connection
• N8N — workflow automation webhooks break
• Custom Node.js/Python apps — your custom webhook listeners stop working

The Silent Failure Problem

This is more dangerous than integrations that show errors. With webhooks:

1. The webhook still listens to the original board, but the PM doesn’t know
2. Automations appear active in the automation center
3. External system silently receives zero events (no error messages)
4. Workflow silently fails without alerting anyone
5. Hours/days pass before someone realizes something’s wrong

Retries don’t help either: monday.com retries a failed webhook request once a minute for 30 minutes, but a board with no subscription sends nothing to retry.

The Broader Pattern

This issue is part of a broader pattern where external integrations don’t duplicate and cross-board automations break.

monday.com’s documentation doesn’t cover what happens to API-registered webhooks on duplication, and there is no webhook event for board creation that an external system could listen for (monday.com developer docs).

How to Get Webhooks Running on a Duplicated Board

1. Build the Webhook as a Recipe on the Template

The Webhooks integration (Integrate, then Webhooks in the board Automations page) sends a payload to your URL each time the chosen event happens on the board. Turned-on integration recipes are duplicated with the board, so a Webhooks recipe built on the template comes across with every copy. Boards created from a saved template get their integrations turned off; reactivate each one. One endpoint can serve every board: each payload carries its boardId.

2. Register Webhooks in the Script That Duplicates

If your app duplicates boards through the API (duplicate_board), it already has the new board’s ID. Call create_webhook for that board, with the same URL and events, right after. monday.com recommends creating webhooks with an integration app token, which end users can’t disable.

3. Point Make, Zapier and Similar Tools at the New Board

Scenarios and Zaps that watch a monday.com board are set up for that board. Add the new board to the scenario or Zap, or create one for it.

4. Audit Webhooks Board by Board

The API’s webhooks query lists the webhooks on a board (app_webhooks_only limits it to your app’s), and delete_webhook removes extras. Each call counts toward the account’s daily API limit: 200 calls on Free, 1,000 on Basic and Standard, 10,000 on Pro and 25,000 on Enterprise.

Wondering whether BoardBridge fits your setup? Ask us.

5. End a Board-Creating Workflow With an HTTP Request

When boards are created by a workflow (for example, with the Create from template block), add a Send HTTP Request block at the end. It sends a GET, POST or PUT request to your URL, with an API token from the Credentials app, and retries on server errors. Your service can then register the webhooks. Check that the new board’s ID can be passed in the request before relying on this.

6. Poll for New Boards When Nothing Else Fits

With no board-creation event to listen for, an external scheduler can query the account’s boards through the API at intervals and register webhooks on any new ones. New boards wait until the next poll, and every query counts toward the daily limit.

Wondering whether BoardBridge fits your setup? Ask us.

Real-World Scenario: Multi-Board Automation at Scale

A company uses Zapier to sync monday.com boards with external systems (CRM, email marketing, project tracking). All events are piped through webhooks.

Before (webhooks left on the template):

1. Template board has webhooks registered by Zapier
2. New project board duplicated
3. Webhook subscriptions don’t transfer to new board
4. Events happen on new board (items created, statuses change)
5. The endpoint receives zero events (silent failure)
6. Zapier doesn’t trigger, data doesn’t sync to external systems
7. Someone notices when emails aren’t being sent, and the Zap is pointed at the new board

With a re-registration step:

1. The script that duplicates the board calls create_webhook for the new board ID
2. The Zap gets the new board added on the same day
3. A test item on the new board confirms events arrive
4. Data syncs from the first event on

Native Options Compared

Post-Duplication Webhook Checklist

Who This Is For

This checklist matters most for teams who:

• Use webhooks to sync monday.com with external systems (Zapier, Make, custom apps)
• Create multiple projects per month from template boards
• Have had silent webhook failures where external systems stopped receiving events

Need webhook registration built into your project setup? We can build it as one of our custom monday.com builds.

Frequently Asked Questions