> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/guides/integrating-with-tools/messanger-apps/discord.md).

# Discord

BugSplat’s Discord integration allows your team to receive alerts for new crashes and errors or new groups of crashes or errors. Receiving BugSplat alerts through Discord lets you stay on top of your application's stability and can serve as an early warning that something might be wrong.

## Integrating Discord with BugSplat <a href="#integrating-slack-with-bugsplat-docs" id="integrating-slack-with-bugsplat-docs"></a>

1. Create a new Discord webhook following the guide found [here](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks).
2. Login to [BugSplat](https://app.bugsplat.com/cognito/login) and navigate to the [Notifications](https://app.bugsplat.com/v2/database/integrations#notifications) page.
3. Select the Database for which you'd like to configure alerts
4. Under the **Discord** section, enter the webhook URL for your channel and click **Update**. More information regarding how to create a webhook URL can be found [here](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks).
5. Use the toggle buttons to set your notification preferences. You can choose to be notified for each new report or each new unique report group.
6. Use the **Fields** dropdown to select the fields you'd like to include in your notifications.

<figure><img src="https://976110677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LBMgmIcgkIXSUfnXDSv%2Fuploads%2Fgit-blob-4ab225437eacfc25e5a38e9ef0bd7f353cdf0c2e%2Fdiscord-integration-settings.png?alt=media" alt="BugSplat Discord notification settings"><figcaption><p>Configuring BugSplat's Discord Integration</p></figcaption></figure>


---

# 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.bugsplat.com/guides/integrating-with-tools/messanger-apps/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.