Send FlaskTrack laboratory events to Discord without moving the system of record

Use a channel webhook to bring operational notifications into the server where your team coordinates work.

The webhook delivers awareness while FlaskTrack retains the authoritative laboratory record, execution context, and history behind the event.

What you need

A Discord server Use the server where the relevant laboratory, operations, engineering, or quality team coordinates work.

A destination channel Choose the text channel that should receive notifications and verify that you can manage its webhooks.

FlaskTrack administrator access Organization administrators manage provider URLs, testing, status, and removal.

1. Open the destination channel. Select the server and text channel that should receive FlaskTrack alerts.
2. Open integration settings. Edit the channel, open Integrations, and locate Webhooks. Webhooks may also be available from the server Integrations page.
3. Create a webhook. Give it a recognizable name such as FlaskTrack and confirm the intended channel.
4. Copy the webhook URL. Use Discord's Copy Webhook URL control and treat the complete URL as a secret.
5. Open FlaskTrack notification providers. Go to organization settings and open Notification Providers.
6. Add the Discord provider. Select Discord and paste the complete webhook URL. Default channel is optional and is retained as an administrative reference.
7. Save and send a test. Confirm the notification appears in the correct Discord channel.
8. Keep the configuration controlled. Disable or delete it when the channel should no longer receive FlaskTrack notifications.

Protect the webhook URL Do not expose it in public code, screenshots, chat history, documentation, or support tickets.

Delete unused webhooks Remove both the Discord webhook and FlaskTrack provider when the integration is retired.

Use notifications as pointers Direct users to the controlled source record in FlaskTrack rather than relying on chat as the evidence record.

Test after permission changes Retest after editing the channel, changing roles, moving the webhook, or replacing its URL.