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

# Datadog Webhook Setup Guide

> Configure Datadog to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](https://docs.stackone.com/connectors/datadog.md#getting-started) on the Datadog connector page.

## How Datadog webhooks work

StackOne creates and manages the webhook automatically when the account is connected — it creates an organization-wide webhook in the Datadog Webhooks integration — named `stackone` unless you set **Webhook Name** on the connection — and deletes it when events are disabled or the account is disconnected.

**1. Grant the webhook scopes**

Creating and deleting the webhook needs two scopes on the Application Key or Personal Access Token, and the key owner must hold the matching Datadog permissions.

<ul>
  <li>**create\_webhooks** — lets StackOne create the webhook.</li>
  <li>**manage\_integrations** — lets StackOne delete the webhook.</li>
  <li>An unscoped Application Key inherits these from its owner.</li>
</ul>

**2. Check the webhook in Datadog**

After you enable events, open **Integrations**, select the **Webhooks** tile, and open the **Configure** tab. The **stackone** webhook (or the **Webhook Name** you set) appears in the **Webhooks** list with its **URL** and **PAYLOAD**; do not edit or delete it, because StackOne manages it.

![Datadog Webhooks integration Configure tab with the stackone webhook selected in the Webhooks list](https://mintcdn.com/stackone-60/Yx9FjiVntAxlAJG7/connectors/datadog/images/events-stackone-webhook.png?fit=max\&auto=format\&n=Yx9FjiVntAxlAJG7\&q=85\&s=23cb57d12a91758a929dc29844bc3b74)

**3. Mention the webhook in your monitors**

A Datadog webhook has no event subscription list — Datadog sends a notification to it only when the notification message mentions it. In each monitor whose alerts StackOne should receive, open **Configure notifications & automations**, type `@webhook-stackone` in the message, and select **@webhook-stackone** under **Webhook** in the suggestions, then save the monitor. If you set a **Webhook Name** on the connection, mention `@webhook-<Webhook Name>` instead.

<ul>
  <li>The same mention works in an incident, security rule, or case notification, which is delivered as an **Other Notification** event.</li>
  <li>See [Datadog monitor notifications](https://docs.datadoghq.com/monitors/notify/) for the full message syntax.</li>
</ul>

![Datadog New Monitor notification message with @webhook-stackone selected from the Webhook suggestions](https://mintcdn.com/stackone-60/Yx9FjiVntAxlAJG7/connectors/datadog/images/events-mention-webhook.png?fit=max\&auto=format\&n=Yx9FjiVntAxlAJG7\&q=85\&s=03f950fa98c3927e5a2a374ea2ca2082)

**4. Set a webhook name for multiple accounts**

Datadog webhook names are unique within an organization. To connect more than one StackOne account to the same Datadog organization, give each connection a different **Webhook Name** (letters, numbers, hyphens, or underscores) and mention the matching `@webhook-<name>` in each monitor. Without it, the second connection fails to create its webhook because `stackone` already exists.

## Available webhook events

The following Datadog events can be enabled. Only events selected in StackOne are delivered, and only for notifications that mention the StackOne webhook (`@webhook-stackone` by default).

**1. Monitor events**

Events fired when a monitor changes state, plus the reminders Datadog re-sends while a state persists. The exact Datadog transition (for example `Re-Triggered`) is kept in the event data.

<ul>
  <li>**Monitor Triggered** (`monitor.triggered`) — Fired when a monitor enters the ALERT state (`Triggered`).</li>
  <li>**Monitor Recovered** (`monitor.recovered`) — Fired when a monitor returns to the OK state (`Recovered`).</li>
  <li>**Monitor Warning** (`monitor.warning`) — Fired when a monitor enters the WARN state (`Warn`).</li>
  <li>**Monitor No Data** (`monitor.no_data`) — Fired when a monitor with no-data notifications enabled stops receiving data (`No data`).</li>
  <li>**Monitor Renotify** (`monitor.renotify`) — Fired when a monitor with a renotify interval is still in ALERT, WARN, or NO DATA and Datadog re-sends the notification (`Re-Triggered`, `Re-Warn`, `Re-No data`).</li>
</ul>

**2. Other notifications**

A catch-all so no delivery is lost.

<ul>
  <li>**Other Notification** (`notification.other`) — Fired for any other notification sent to the StackOne webhook, such as incident, security signal, or case notifications.</li>
</ul>

## Delivery format

Details of how Datadog delivers events to StackOne.

**1. JSON payloads**

Each delivery is an HTTP POST with one notification, rendered from a fixed StackOne payload template of Datadog webhook variables. The notification id (`$ID`) is used as the event ID and `$DATE` (epoch milliseconds) as the event date; `alert_id` in the data is the monitor id, and `alert_cycle_key` links reminders and recoveries to the notification that started the alert.

**2. No signature**

Datadog does not sign webhook deliveries. The account-specific callback URL StackOne registers identifies the connected account.

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


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