1
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 for the current UI and permissions.
2
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.3
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.thread_id query parameter identifying an existing thread. See Discord’s execute-webhook reference 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 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.