> ## Documentation Index
> Fetch the complete documentation index at: https://3to1go.docs.thesteau.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Discord

> Send backup notifications to a Discord channel using an incoming webhook.

Create an incoming webhook in the Discord channel where you want notifications. You need permission to manage that channel's webhooks. A bot application is not needed for this setup.

<Steps>
  <Step title="Create the webhook in Discord">
    Open the channel settings, then **Integrations → Webhooks**. Create a webhook, select the channel, and copy its webhook URL. Follow [Discord's webhook setup guide](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks) for the current UI and permissions.
  </Step>

  <Step title="Create a destination in 3to1go">
    Open **Integrations** in Scout or Station. Name it, choose **Discord message**, and paste the complete webhook URL into **Destination URL (secret)**. No authorization header is required: the token is already in the URL. For delivery confirmation, append `?wait=true`, or `&wait=true` if the URL already has a query.
  </Step>

  <Step title="Select events and save">
    On Scout, start with `upload-finished` and `unusual-backup`. On Station, start with `upload-received` and `unusual-upload`. Set a message template, save, and click **Test saved destination**. Confirm that the sample appears in the channel.
  </Step>
</Steps>

For example:

```text theme={null}
{{ app }}: {{ job_name }} — {{ event }} / {{ status }}
```

The sender safely encodes message text and disables user, role, and everyone mentions. Messages are capped at 2,000 characters. Start with a normal text channel; forum and media channels need a `thread_id` query parameter identifying an existing thread. See [Discord's execute-webhook reference](https://docs.discord.com/developers/resources/webhook#execute-webhook) for channel types, parameters, and response behavior.

HTTP `429` is reported as a failed delivery and is not automatically retried. If you have many jobs, use event filters or route through [n8n](/integrations/n8n) to aggregate messages and control volume.

Treat the complete webhook URL as a password. If it leaks, delete or replace the webhook in Discord, then replace the saved URL in 3to1go. See [Integration secrets](/integrations/secrets).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.