Blog/
Discord Twitter Alerts Without Polling Timelines
Discord Twitter integration for account alerts: discover handles, promote them to monitors, push signed webhooks into Discord — Free to test, Starter for live hits. Hub: /twitter-webhook.
Polling Discord alerts does not scale
Searches like “discord twitter” or “discord twitter integration” usually mean one job: when these public accounts post, the Discord channel lights up. DIY cron + timeline fetch works for one handle — then you own workers, cursors, rate limits, and silent misses.
X does not ship a public new-tweet webhook. Treat Discord delivery as the last hop of a Twitter webhook pipeline: monitors detect posts, signed HTTP POSTs hit your stack, Discord Incoming Webhooks (or a bot) render the message. Product hub: /twitter-webhook. Landing: /twitter-discord-alerts.
Architecture: discover then promote
Discover candidates with search (from:user, cashtags, lang:) the same way you would for crypto KOLs. Keep accounts that produce actionable posts — not pure engagement bait.
Promote keepers to XFlux monitors. Paste a Discord Incoming Webhook URL on the monitor (XFlux formats Discord payloads) or point at Make/n8n/your HTTPS receiver and forward yourself. Make path: /docs/integrations/make. Custom Node HMAC: /twitter-webhook-nodejs.
// After verifying X-XFlux-Signature on the raw body...
const discordWebhook = process.env.DISCORD_WEBHOOK_URL;
const { tweet, monitor } = payload; // monitor.hit shape
await fetch(discordWebhook, {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
content: `**@${monitor.targetUsername}** posted:\n${tweet.text}`,
}),
});Alert hygiene
Split Discord channels by risk: macro vs crypto KOLs vs brand watches so traders can mute noise. Add keyword filters on noisy monitors. Deduplicate by tweet id; rate-limit if an account threads aggressively.
Same hygiene playbook as the general webhook guide: /blog/twitter-webhooks-account-alerts. Keyword templates: /docs/guides/trading-keywords.
Budgeting API calls
Exploration burns search/timeline quota. Steady-state should be monitor-heavy so you are not polling every account for Discord. Free: 1 monitor, Dashboard hits, Test webhook pings to prove Discord wiring. Starter: live monitor.hit delivery and faster polling.
If you also need Slack or a custom server, start from /twitter-webhook and branch to /twitter-slack-alerts — same monitor events, different destinations.
FAQ
- Can Discord call XFlux directly?
- Discord Incoming Webhooks only receive POSTs. Either paste the Discord URL into XFlux (we format the payload) or use a middle layer (Make/n8n/your server) that XFlux calls first.
- Is a Discord bot token required?
- Not for channel webhooks. Bot tokens are for richer bots (slash commands, roles). Webhooks cover most “post appeared” alerts.
- Where do I start?
- Register → add one monitor → paste Discord webhook → Test → upgrade when you need live hits. Hub: /twitter-webhook. Product page: /twitter-discord-alerts.
Monitor these accounts — hits can go to Discord or Slack
Free includes 1 monitor. Pick the handle that moves your workflow; after it's created you can attach a Discord or Slack webhook.
Build with XFlux
Free tier for reads and one monitor. Starter from $19/mo for signed webhooks and faster polling.