# monday.com Webhook Subscriptions Don’t Transfer on Duplication Canonical: https://www.taskrhino.ca/monday-com-automations/webhook-subscriptions-dont-transfer/ > API-created monday.com webhooks stay on the original board when you duplicate it. Why, and how to re-register them with a script or a Webhooks recipe. Published: 2026-02-26 Updated: 2026-10-29 Author: Rakesh Patel Categories: BoardBridge **Key takeaways** - A webhook created through the API subscribes to one board ID; a duplicated board gets a new ID, and monday.com doesn’t document API webhooks carrying over. - Turned-on integration recipes, including Webhooks recipes, are duplicated with the board, so building the webhook as a recipe on the template keeps it on every copy. - A script that duplicates boards through the API already knows the new board ID and can call create\_webhook for it straight away. - The API’s webhooks query lists a board’s webhooks, so you can spot missing or duplicate ones and remove extras with delete\_webhook. - Make, Zapier and similar tools watch the board they were set up on; point them at each new board. 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](https://www.taskrhino.ca/monday-com-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. Definition **Webhook subscription:** a standing instruction for monday.com to POST an event from one board (an item created, a column changed) to a URL you control. Webhooks work by creating **active subscriptions** tied to specific board IDs. [Source: monday.com Developer Docs – Webhooks](https://developer.monday.com/apps/docs/webhooks-1) 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: 1. **Create the webhook:** your app calls the GraphQL API’s `create_webhook` mutation with a board ID, a URL and an event, for example `create_webhook (board_id: 987654321, url: "https://example.com/webhook", event: create_item)`. 2. **Pass the challenge:** monday.com POSTs a random `challenge` token to the URL, and your endpoint returns it. 3. **Receive events:** when the event happens on board 987654321, monday.com POSTs the payload, which includes the `boardId`. 4. **Process them:** your external system acts on the event. When you duplicate the board to board ID 111111111: 1. New board created (111111111) 2. Turned-on recipes copied, including any Webhooks integration recipe 3. But webhook subscription still only listens to board 987654321 4. Events on board 111111111 are NOT sent to your webhook URL 5. External system receives zero notifications 6. Automations fail silently ### 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. Key stat 30 minutes is how long monday.com retries a failed webhook request (once a minute). A board without a subscription never sends one. ### The Broader Pattern This issue is part of a broader pattern where [external integrations don’t duplicate](https://www.taskrhino.ca/monday-com-automations/external-integrations-dont-duplicate/) and [cross-board automations break](https://www.taskrhino.ca/monday-com-automations/dont-carry-over-duplicated-boards/). **See BoardBridge Forms in Action** Book a free demo of BoardBridge forms for monday.com — live, with your data. [Book a Free Demo](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) 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](https://developer.monday.com/api-reference/reference/webhooks)). ## 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. TaskRhino tip Keep the template’s webhook URLs and events in one config file your script reads, so every new board gets the same set. ### 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](https://www.taskrhino.ca/contact-us/). **Need Help With Your monday.com Setup?** TaskRhino has implemented monday.com for 110+ teams. Get a free consultation. [Schedule Free Consultation](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ### 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. TaskRhino tip Name template-based boards with a fixed prefix, so a poller or script can tell project boards from everything else at a glance. Wondering whether BoardBridge fits your setup? [Ask us](https://www.taskrhino.ca/contact-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 | Option | Works for | Watch out for | | --- | --- | --- | | **Webhooks recipe on the template** | Sending board events to one URL | Boards created from a template get integrations turned off | | **create\_webhook after duplicate\_board** | Your own apps and scripts | The URL must answer the challenge; calls count toward the daily limit | | **Re-pointing Make or Zapier** | Scenarios and Zaps | One more board to add for every project | | **webhooks query audit** | Finding missing or duplicate webhooks | Board by board | ## Post-Duplication Webhook Checklist 1. **List the template’s webhooks:** run the `webhooks` query on the template board and note each URL and event. 2. **Duplicate the board** (in monday.com or with `duplicate_board`). 3. **Check recipes:** open the new board’s Automations page and confirm any Webhooks recipes are on. 4. **Register API webhooks:** call `create_webhook` for the new board for each URL and event your app needs. 5. **Re-point tools:** add the new board to every Make scenario or Zap that should watch it. 6. **Test:** create a test item on the new board and confirm your endpoint receives the event. ## 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](https://www.taskrhino.ca/monday-com-customization/). **Stop Creating Duplicates** BoardBridge forms update existing items — no Enterprise plan, no workarounds, no duplicates. [See It In Action](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ## Frequently Asked Questions **Why do monday.com webhook subscriptions fail to transfer when duplicating a board?** ### Webhooks registered through the API are tied to the original board’s ID, which changes on duplication; monday.com’s duplication doc says turned-on integration recipes are duplicated but doesn’t cover API-created webhooks. Register them again on the new board with the API’s create\_webhook mutation, or build them as Webhooks integration recipes on the template so they’re copied with the board. **How can I automatically recreate webhook integrations after monday.com board duplication?** ### If your own script duplicates the board, call the API’s create\_webhook mutation for the new board ID right after, with the same URLs and events. Or build the webhook as a Webhooks integration recipe on the template, since turned-on integration recipes are duplicated with the board. Make and Zapier scenarios need the new board added. **Are there duplicate webhook requests after duplicating a monday.com board with integrations?** ### It can happen if both a duplicated integration recipe and your own script register a webhook for the same event on the new board. List the board’s webhooks through the API and delete the extras. **Why do webhook automations break when copying monday.com boards from templates via API?** ### API-based duplication of template boards fails to properly transfer webhook integrations, leading to broken automations and odd errors due to board ID mismatches. Workarounds involve post-duplication API calls to recreate subscriptions: the duplicate\_board response gives the new board ID, and create\_webhook registers each webhook on it. **Do third-party app webhooks like Zapier copy over on monday.com board duplication?** ### Third-party webhooks from apps like Zapier often do not copy over during board duplication or templating, unlike some built-in integrations that appear in ‘ghost’ status. They must be manually reconfigured with the new board ID to restore functionality: add the new board to the Zap or scenario, or create a new one. **What’s the best workaround for lost webhooks on frequently duplicated monday.com template boards?** ### Built-in automations may partially transfer, but webhooks consistently require recreation using API scripting or tools like Make.com after each duplication. Build what you can as Webhooks integration recipes on the template, and have the script that creates each board call create\_webhook for the rest. **How to automatically register webhooks for boards created via monday.com automations?** ### Boards created from templates by automations or workflows don’t get your API-registered webhooks, so they need post-creation API calls or third-party tools. In a workflow, a Send HTTP Request block after the board-creation step can call a service that registers them; polling with a tool like Make works too, but new boards wait for the next poll. **What triggers are needed to detect new boards and auto-register webhooks in monday.com?** ### monday.com lacks built-in webhooks for board creation or structural changes, so detecting new boards requires polling via API or external schedulers. Where you control how boards are created (your own script, or a workflow with a Send HTTP Request step), register the webhooks in that same step instead.