> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chatflows.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhooks

> Send a copy of each WhatsApp event, like a new message or a template approval, to your own server or app in real time.

Whenever there is activity on your WhatsApp account — like an incoming message, a template approval, or a delivery update — ChatFlows can send the details of that event to your own server, CRM, or automation tools.

Find it under **Settings → Webhooks**.

> [!NOTE]
>
> Only the workspace **owner** can change these settings.

![Global Webhook Config form showing webhook URL, method, signing secret, events, and a list of channel overrides](https://docs.chatflows.io/settings/img/webhooks-form.png)

Image shows the Webhooks page, with the global settings on top and channel overrides below.

## Turning it on

**1. Switch on Global Webhook Config**

Use the switch at the top right of the card. The fields below unlock.

**2. Enter your Webhook URL**

The web address where events are sent, such as `https://your-server.com/webhook`.

> [!WARNING]
>
> The address has to be reachable from the internet. A local address such as `localhost`, `127.0.0.1` or an address inside your own network is refused when you save, for security reasons.

**3. Choose a Method**

You can use POST or GET. POST is recommended. In both cases, the event data is sent as JSON in the request body.

**4. Add a Signing Secret**

Click the refresh icon to generate a secret key. Your server uses this key to confirm that a webhook truly came from ChatFlows and wasn't sent by someone else.

**5. Pick your Events**

Choose which events to forward to your server — from a long list of event types, like **Messages**, **Message Template Status Update** and **Phone Number Quality Update**. Only the events you select are sent.

**6. Save**

Click **Save changes** to turn on forwarding. From now on, every event you selected is sent to your webhook URL as it happens.

## Per-channel webhook settings

By default, all your channels forward their events to the same webhook URL. If you want a specific channel to send its events somewhere else instead, you can give that channel its own webhook settings.

![The Channel Overrides section with a channel expanded, showing an Override toggle, Enable forwarding switch, and its own Webhook URL, Method, Signing Secret, and Events fields, with a Save Channel button](https://docs.chatflows.io/settings/img/webhooks-channel-override.png)

Image shows the Channel Overrides section with a channel's own settings.

**1. Find the channel**

Scroll to **Channel Overrides**. Only connected, active channels are listed.

**2. Turn on Override**

The channel's own fields open up.

**3. Turn on Enable forwarding for this channel**

Then fill in its own **Webhook URL**, **Method**, **Signing Secret** and **Events**. These are separate from the global ones.

**4. Click Save Channel**

That channel now uses its own webhook settings. All your other channels keep using the default settings.

## What's next

> [card] [Developer API Keys](https://docs.chatflows.io/core-setup/api-keys.md)
>
> Read and send data with the REST API for a full two-way integration.

> [card] [WhatsApp Message Log](https://docs.chatflows.io/core-setup/whatsapp-activity-log.md)
>
> See every message that went out from your workspace.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.