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

# Receive an alert from Sentry

> Called by Sentry only. A signed Sentry alert becomes DevOps work, which only ever proposes.

This is the **Webhook URL** of your Sentry internal integration. You do not call it yourself: the
DevOps page shows the exact address beside your attached Sentry connection, to paste into Sentry.

It takes no API key. Sentry signs every request with your integration's **client secret**, and the
signature (`Sentry-Hook-Signature`) is checked over the exact bytes before anything in the body is
read. The client secret is the one you saved with the Sentry connection the address names; a
connection saved without one accepts nothing. A request that does not verify is `401`.

It acts as the person who attached the connection, checked again on every request: if they leave,
lose the role, or the organisation is paused, nothing is filed.

> [!WARNING]
>
> AI employees are in **beta**. This answers `404` unless your deployment has switched on the beta
> and picking up work by itself, and for an address no DevOps attachment holds. Not yet run against
> a real Sentry account. See [DevOps](https://docs.mithunai.com/team/devops.md).

**credential\_id** `string` *required*

The saved Sentry connection attached to the DevOps employee. It names the connection, not your
organisation; the signature is what is trusted.

## What is read

| `Sentry-Hook-Resource` | Filed when | Reference | Service |
| - | - | - | - |
| `event_alert` | `action` is `triggered` | `sentry-<issue id>` | The event's `service` tag, else the Sentry project |
| `metric_alert` | `action` is `critical`/`warning` | Service and title | The alert rule's first project |
| `issue` | `action` is `created` | `sentry-<issue id>` | The issue's project |

Everything else -- `installation`, a resolved alert, a comment -- is answered `200` and files
nothing. No URL in the body is followed. The investigation reads the issue and its latest event back
from Sentry, with your token, rather than trusting the body for them.

## Response

**results** `object[]` *required*

One per alert filed, with `service`, `title`, `status` and `task_id`; empty when nothing was.


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