> For the complete documentation index, see [llms.txt](https://prisma-logs.gitbook.io/prisma-logs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prisma-logs.gitbook.io/prisma-logs/docs/en/the-panel/discord-webhooks.md).

# Discord webhooks

Logs of a category can also go to a Discord channel. They stay in the panel as well.

## Creating a webhook

1. Open the channel in Discord, for example `#logs-items`.
2. **Edit Channel → Integrations → Webhooks → New Webhook**.
3. Give it a name and press **Copy Webhook URL**.

## Connecting it

1. Go to **Categories** in the panel.
2. Press **Edit** on the category.
3. Paste the URL under **Discord Webhook** and save.

From now on every log arrives as a message in the channel, with the category as title, all fields below it, a color per category and a link to the panel.

## Limits

Discord lets a webhook send about 30 messages per minute. Per batch at most 20 logs per category go to Discord. On a busy server not every log reaches Discord, but all of them are in the panel.

{% hint style="info" %}
Tip: put webhooks on categories you really want to follow, like `admin`, `explosions` or `police & crime`, not on busy ones like `chat`.
{% endhint %}


---

# 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://prisma-logs.gitbook.io/prisma-logs/docs/en/the-panel/discord-webhooks.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.