> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/webhook/configuration.md).

# Configuration

Now that the basic onboarding is complete, let's review all fields in the form and how to use them. We have two more fields to explore here: **Templates** and **Secrets.**

{% content-ref url="/pages/u5jOmiA9rqyAqWKxtRys" %}
[Templates](/channels/webhook/templates.md)
{% endcontent-ref %}

### Authorization Header

By default, the webhook will accept all POST requests to the given endpoint, which means that anyone can send requests to the endpoint. In order to prevent unauthorized access, you can enable the authorization header which will generate a random access token for you:

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

This authentication token will only be visible once. If you lose it, you'll need to click the **Regenerate** button to create a new random token, copy that and save the provider form to apply it.

To use this access token, send the following header as part of your POST request:

```
Authorization: Bearer <your access token>
```

### Secrets

Secrets section is used to store the **credentials** safely.

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

These secrets are encrypted and passed to the *process* function as ***params.secrets***


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.edgetag.io/channels/webhook/configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.