> For the complete documentation index, see [llms.txt](https://help.sleuth.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sleuth.io/sleuth-dora/sleuth-automations/actions/webhook.md).

# Webhook Actions

The `webhook` action will send an HTTP POST to the URL of your choosing. The body contains information about the deployment, and a signature to verify the webhook is valid and originated at Sleuth.

## Body

The body of the webhook will look something like this:

```
{
  "organization": {
    "slug": "myorg"
  },
  "name": "791f0e0",
  "on": "2021-02-03T00:35:09.823706+00:00",
  "branch": "master",
  "revision": "791f0e0ce8612717da226d73caac7790e0de4032",
  "environment": {
    "slug": "production"
  },
  "changeSource": {
    "slug": "sleuth-test"
  },
  "health": "healthy",
  "author": {
    "email": "nobody@example.com"
  }
}
```

## Signature

The webhook will contain two headers you can use to safely validate the message:

* `X-SLEUTH-TIMESTAMP` - The unix timestamp, in seconds, of when the webhook was created
* `X-SLEUTH-SIGNATURE` - The signature of the timestamp and request body, signed with the API key

The signature follows the format Slack uses to validate their webhooks. For more information how it works and how to validate the signature, see [the Slack docs](https://api.slack.com/authentication/verifying-requests-from-slack)

The only difference is Sleuth uses the API key from your Sleuth [organization](/sleuth-dora/settings/organization/details.md) as the signing key.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sleuth.io/sleuth-dora/sleuth-automations/actions/webhook.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.