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

# Send Alerts to a webhook

> Send Method Alerts to a generic HTTP webhook endpoint.

A generic HTTP webhook channel POSTs each Alert as JSON to an HTTPS endpoint you control. The Teams and Slack channels format Alerts as chat messages; a webhook sends the JSON for you to route into your own systems.

For the shared Alerts model and how to create Alert rules, see [Set up Alerts](/guides/administration/alerts/overview).

---

## Add a webhook channel

#### Open Alerts and add a channel

In the **Admin** panel, open **Alerts** under the **Setup** group. Under **External channels**, click **Add channel** and set the channel type to **Webhook**.

![The Alerts page showing the External channels and Alert rules sections, with the Add channel button](/_fern-files/methodsecurity.docs.buildwithfern.com/3658442e4aed66586d64c5ae9b3d5fef674fb1d1a5f4c257c671aba4f282b146/pages/guides/administration/alerts/generic-webhook/create-new-webhook.gif)

#### Enter the channel details

Fill in the Webhook channel fields:

* **Channel Label**: a display name for this destination in the External channels list, such as `SIEM Ingest` or `Incident Intake`. It is cosmetic and does not affect the payload.
* **Webhook URL**: the full HTTPS endpoint Method posts the Alert JSON to. This can be any endpoint you control, such as a SIEM webhook collector, an internal relay or serverless function, an automation or workflow platform, or an incident-management intake URL.
* **HTTP Headers**: zero or more key/value pairs added to every outbound POST, added with **+ Add header**. Covered in the next step.

![New Target Channel form set to Webhook, with a Channel Label of System Web Hook, a Webhook URL field, and an HTTP Headers section with an Add header button](/_fern-files/_img/d24ea932d9ef2b6189fd18b447e352e83e0d9f7b4daf44233c565e4f48cdcd80.webp)

#### Add authentication headers

Authentication goes in **HTTP Headers**. Click **+ Add header** and add the key/value pair the receiving system expects, for example `Authorization` set to `Bearer <token>`, or `X-Api-Key` set to your key. Add a header for every value the endpoint requires.

![Webhook channel form with an HTTP header added: Authorization set to a Bearer token, with a delete control beside it](/_fern-files/_img/e1aff9dcdf8708385f9d2097424a4f9ec280f8115cb38a1a4dd48575dd78d45f.webp)

#### Save the channel

Click **Add**. The webhook appears in the **External channels** list and is ready to receive Alerts.

![External channels list showing the System Web Hook Webhook channel connected](/_fern-files/_img/863129ad8b48548504ecee68e42ca26db9b9c5ac41a0e4979e880198cc68bf10.webp)

Once the channel is connected, [create an Alert rule](/guides/administration/alerts/overview#create-an-alert-rule) to route events to it.