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

# Discord

### How to integrate test automation with Discord?

BugBug can send test notifications to a Discord channel using Discord's native webhook system.

Use this integration when your team monitors test results in Discord and wants instant updates about test, suite, or schedule runs.

Keep in mind that Discord integration is available on paid plans. More information about pricing can be found here: <https://bugbug.io/pricing/>

### Create a Discord webhook

Before you create a Discord alert in BugBug, create a webhook URL in Discord.

1. Open Discord and go to the server where you want to receive BugBug notifications.
2. Open **Server Settings**.
3. Go to **Integrations**.
4. Open **Webhooks**.
5. Create a new webhook.
6. Choose the channel where BugBug should post messages.
7. Copy the webhook URL.

Treat the webhook URL as a secret. Anyone with this URL can send messages to your Discord channel.

### Create a Discord message alert

After you have the Discord webhook URL, create an alert in BugBug.

1. Go to the **Alerts** page.
2. Click **New alert**.
3. Choose when the alert should be sent, for example when a test, suite, or schedule finishes.
4. Select **Send Discord message** as the alert action.
5. Paste the Discord webhook URL.
6. Save the alert.

Before saving, use **Trigger Alert** to check that Discord receives the message.

### What this integration supports

BugBug sends messages to Discord channels through Discord webhooks. It does not install a Discord bot and does not send direct messages to Discord users.

If you need a custom payload for another service, use an outgoing webhook alert instead.


---

# 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://docs.bugbug.io/integrations/discord.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.