> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/settings/inbound-secret.md).

# Manage the inbound webhook secret

The workspace's **Webhook secret** can authenticate inbound workflow webhooks that use bearer authentication. Each endpoint can also have its own authentication setup.

## Configure a sender

1. Open the workspace's Webhook secret page as an admin.
2. Create or reveal the secret when you need to configure an authorized sender.
3. Copy it into the external system's protected credential store.
4. Send it in `Authorization: Bearer YOUR_SECRET` to the generated endpoint.
5. Capture a sample and check the accepted input before publication.

Use the receiving URL from the workflow's **Webhook setup**. Do not infer the URL from the workflow name.

## Rotate the secret

Review every sender using the workspace secret before rotating it. Replace the protected credential in those senders and verify a controlled event afterward.

An old secret stops authenticating after rotation. Endpoint-specific authentication may be a better choice when separate senders need independent credential lifecycles.

## Know the credential types

The inbound secret accepts events at configured webhook endpoints. It is not your general API token and does not grant scheduling API access. HMAC endpoints have their own signing requirements; use their generated example rather than sending a bearer secret to every endpoint.

See [API and webhooks](/workflows/api-and-webhooks.md) and [Webhook integrations](/integrations/webhook-tools.md).


---

# 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 dynamically by asking a question.

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

```
GET https://docs.distro.so/settings/inbound-secret.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 `build a script that syncs our docs to a CMS` 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.