> For the complete documentation index, see [llms.txt](https://guides.stellaraio.com/stellar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-settings-tab/how-to-set-up-discord-notifications.md). # Discord Notifications Complete guide to setup Discord Notifications A Discord webhook lets Stellar send notifications directly to a text channel in your Discord server. This makes it easier to follow checkouts and stock alerts without watching every task. ### 1. Create a server or choose one you manage If you already have a server where you can manage webhooks, skip to the next section. Otherwise: 1. Click the **+** at the bottom of your Discord server list. 2. Choose **Create My Own**. 3. Choose **For me and my friends**. 4. Name your server and create it. How to set up Discord Notifications? provider setup reference How to set up Discord Notifications? provider setup reference How to set up Discord Notifications? provider setup reference How to set up Discord Notifications? provider setup reference ### 2. Create a channel and webhook 1. Create a text channel for Stellar notifications. 2. Open that channel's settings using the gear icon. 3. Open **Integrations** and create a webhook. 4. Give it a recognizable name and check that the selected channel is correct. 5. Click **Copy Webhook URL**. The webhook URL allows messages to be sent to your channel. Keep it private and do not include it in public screenshots. ### 3. Connect it to Stellar 4.0 1. Open **Settings → Discord**. 2. Paste the URL into **Discord Webhook**. 3. Click **Test** beside the field and check your Discord channel. ### Choose where alerts go * **Discord Webhook:** your main checkout notifications. * **Monitor Webhook:** stock alerts when a monitor finds products. A separate channel is helpful so stock alerts do not bury checkout messages. Leave empty to skip monitor notifications. * **Failure Webhook:** a separate channel for failed checkouts. Leave empty to use the main webhook. * **3DS Webhook:** a separate channel for 3D Secure payment-authentication alerts. Leave empty to use the main webhook. To use another channel, create a webhook for that channel and paste its URL into the matching field. ### Notification switches * **Send on Failure:** enable failure notifications. * **Send on 3D Secure:** enable alerts when payment authentication is required. * **Hide Proxy:** hide proxy information in webhook messages. * **Mention Everyone:** add an @everyone mention. Use this only when you want to notify everyone in that channel. ### Optional Pushover alerts The same page includes **Pushover User Key** and **Pushover API Key** fields for mobile notifications. Use the links beside those fields to get the appropriate keys. The API Key field can stay empty to use the default token. Pushover is optional and separate from pairing the Stellar Mobile Companion App. ### If the test does not arrive Check that you copied the complete URL, selected the intended channel, and that the webhook still exists in Discord. Also check Discord's channel notification settings if messages arrive but you do not receive a notification. --- # 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://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-settings-tab/how-to-set-up-discord-notifications.md?ask=&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.