> This page is for Unified.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.merge.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.merge.dev/_mcp/server.

# Third-party webhooks sent to Merge

> How to set up webhooks in third-party platforms so they push real-time data changes to Merge, reducing sync latency.

> **Info**
>
> This feature is only available to customers on our **Professional** or **Enterprise** plans. View the [Merge Plans](https://merge.dev/pricing) to learn more.

---

## Overview

When an event occurs in a third-party platform, such as a change to end user data, that platform can be configured to send Merge a webhook with a data payload to give you real-time updates regardless of the rate at which Merge syncs data.

Follow the setup instructions below to enable Merge to receive third-party webhooks for a linked account.

---

## Automatic setup

Merge is able to automatically create webhooks in supported third-party APIs to alert Merge of changes. This means neither you nor your end user needs to do the manual setup of a webhook per Linked Account. [See what integrations support automatic webhook creation.](https://docs.merge.dev/integrations/hris/supported-features/)

Automatic webhooks are created on Merge’s initial sync with a third-party platform.

Automatic webhooks are not enabled by default. To enable automatic webhooks, go to **Advanced > Webhooks > Third Party** in your dashboard to toggle this feature on.

![Config Merge to You](/_fern-files/merge-test.docs.buildwithfern.com/e8b19f386075b30e0dc8abd552b309b673dc985d351f1270c61fa4f6c76c7cea/docs/src/assets/images/docs/webhooks/ConfigMergeToYou.svg)

**To enable / disable webhooks for a specific Linked Account**, go to the **Webhooks** tab under a specific Linked Account.

You will see a purple notice that says ****Merge automatically created this webhook in \[App Name].****

Enable or disable the **Merge receiver** (an endpoint in Merge's API that receives third-party data) to control whether Merge updates your data with payloads from the connected app's webhooks.

![Webhook Receivers](/_fern-files/merge-test.docs.buildwithfern.com/a4fea66d098ff53a851ab0f19cf032e7f08c27dcb3b0a0a2ab4a743d307c5834/docs/src/assets/images/docs/webhooks/WebhookReceivers.svg)

---

## Manual setup

There are a few third-party applications that do not support automatic webhook creation via API, but do support manual webhook creation via UI. [See what integrations support automatic webhook creation.](https://docs.merge.dev/integrations/hris/supported-features/)

The only way to set up webhooks for these integrations is:

#### Have your end user manually configure the webhook subscriptions in their third-party app instance.

See our Help Center for guides to configure webhooks in the third party.

#### Manually configure third-party webhooks in Merge

Navigate to Linked Accounts and select an account integrated with a third-party platform that supports third-party webhooks.

Go to the **Webhooks** tab of the Linked Account to:

* Access the **Merge Receiver URLs** and **Signature Keys**
* Enable each event you want Merge to listen to

Enable events one Linked Account at a time. An event you have not enabled has no listener behind it, so the **Webhooks** tab shows it as disabled and Merge discards any payload the third party sends for it.

![Webhook Receiver Config](/_fern-files/merge-test.docs.buildwithfern.com/86df719ce52d5cda3b1a718e3e390107573f027f2dc745096e115de450950491/docs/src/assets/images/docs/webhooks/WebhookReceiverConfig.svg)

> **Fill in the organization-level signature key before you enable an event**
>
> A few integrations verify every inbound payload against one signature key held in your organization-level credentials rather than a per-Linked-Account key. For those, fill in the signature key for that integration on the **Integrations** page of your dashboard. Enabling an event without that key returns an error, because a key Merge generates on your behalf will never match the signature the third party sends.

Once your webhooks are configured, the third-party application will send webhooks to the **Merge Receiver URLs.**

For each webhook request, Merge will immediately process the incoming data and save the updated model(s).

Webhooks will be sent from Merge to your system for all relevant **Merge Webhooks** you have set up, allowing real-time updates to flow from the third-party app all the way to your system.