Create a Discord webhook
In your Discord server, go to channel settings and create a webhook. Copy the webhook URL. This is the endpoint where your automation will POST Flux board notifications.
// Discord + Flux
Post Flux card notifications to Discord channels. Keep your team or community informed about what shipped, what moved, and what is blocked. Discord webhooks plus the Flux API.
In your Discord server, go to channel settings and create a webhook. Copy the webhook URL. This is the endpoint where your automation will POST Flux board notifications.
Use an automation platform (Zapier, Make, n8n) or a custom script to monitor Flux board changes. Poll the Flux API for updates or listen to Flux SSE events, then forward formatted messages to your Discord webhook.
Discord webhooks support rich embeds with titles, descriptions, colors, and fields. Format your card notifications as embeds: card title as the embed title, column name as a field, and a link back to the Flux board.
Configure your automation to only notify on events that matter to your community or team. Cards reaching Done, new high-priority cards, or overdue tasks. Avoid flooding the channel with every minor update.
Yes, with a Discord bot. Build a bot that listens for a slash command (e.g., /card) in your server, extracts the card title from the message, and POSTs to the Flux /api/cards endpoint. This requires hosting the bot and providing it with a Flux API key.
Flux does not push events to Discord directly. You need an automation layer that reads from the Flux API or SSE stream and posts to a Discord webhook. This can be a Zapier/Make/n8n workflow or a small custom service.
Yes. If your open-source project uses Flux for issue tracking, you can post card updates to a public Discord channel so contributors can follow project progress without needing Flux accounts.
// Keep everyone informed
Flux REST API + Discord webhooks. Board notifications in your server.