# Webhook Configuration

<figure><img src="/files/Ci6ejvacGuQp0oHvtgFG" alt=""><figcaption></figcaption></figure>

### Creating a Webhook

1. Navigate to **Settings** → **Integrations** → **Webhooks**
2. Click **Create Webhook**
3. Configure:
   * **Name**: Descriptive name (e.g., "Security Team Slack")
   * **URL**: Destination endpoint
   * **Events**: Select event types to receive
   * **Active**: Enable/disable webhook
4. Click **Save**

Sentry will send a test payload to verify the endpoint.

### Webhook Payload

Sentry sends POST requests with JSON payloads:

```json
{
  "event": "BREACH_ALERT",
  "timestamp": "2026-01-07T10:30:00Z",
  "organizationId": "org_abc123",
  "severity": "HIGH",
  "data": {
    "title": "New credential breach detected",
    "message": "Email user@company.com found in Dropbox breach",
    "service": "Dropbox",
    "breachDate": "2024-08-15",
    "dataClasses": ["Email", "Password"]
  },
  "metadata": {
    "alertId": "alert_xyz789",
    "dashboardUrl": "https://sentry.auditware.io/alerts/alert_xyz789"
  }
}
```

### Webhook Security

**HTTPS Required**: Sentry only sends to HTTPS endpoints (enforced security).

**Signature Verification**: Each webhook includes a signature header:

```
X-Sentry-Signature: sha256=<signature>
```

The secret is the shared key, and the signature is the cryptographic proof.\
Sentry doesn't send the secret itself (that would be insecure), it sends the signature computed from the secret.

**IP Allowlisting**: Optionally restrict to Sentry's webhook IPs (provided in settings).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sentry.auditware.io/monitoring/alert-webhooks/webhook-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.