Connect your pool to Discord

Send pool updates, like new entries or standings changes, straight to a Discord channel. This uses Discord's own OAuth flow, so you never have to create or paste a webhook URL yourself.

Prerequisites

• You need edit access to the pool.
• You need permission to add webhooks to the Discord server and channel you want to connect.

Connecting

1. Open the pool and go to Integrations.
2. Find Discord and click Connect.
3. Discord opens its own authorization screen. Pick the server you manage, then choose the channel that should receive pool notifications.
4. Approve the request. Discord issues a webhook for that channel and sends you back to the pool's Integrations tab.

If the connection succeeded, the tab shows Discord as connected, along with the name of the channel you picked. If something went wrong, you'll land back on the same tab with a status instead:

• denied - you (or Discord) canceled the authorization.
• forbidden - your account doesn't have edit access to this pool.
• not_configured - Discord isn't set up for this app yet; contact support.
• bad_state or error - the request expired or failed; click Connect again.

Once connected, the pool stores the webhook for that channel and turns on Discord as a notification channel alongside any email, Slack, or Telegram notifications you already have configured. You can still choose which events (new entries, leaderboard changes, etc.) actually get sent from your notification settings.

Testing

Before relying on the integration, confirm the webhook actually delivers messages to the right channel.

1. On the Integrations tab, with Discord connected, click Send test notification (or the equivalent test action next to Discord).
2. Trofeo.live sends a short confirmation message to the connected channel: something like "Test from [Pool Name], notifications are wired up."
3. Check the Discord channel you picked during setup. The message should appear right away.

If the test fails, you'll see an error instead of a success confirmation. This usually means the webhook was deleted or the channel permissions changed on the Discord side. If that happens, disconnect and reconnect Discord from the Integrations tab to generate a fresh webhook.