Twitter to Discord Bot: Real-Time Tweet Alerts in Your Server (2026)

The Discord half is the easy half

Every Discord channel can mint a webhook URL for free: Server Settings → Integrations → Webhooks → New Webhook. Posting a message is a single HTTP POST with no auth token and no bot user to invite. Here is the entire Discord side, in Python:

import requests

# From Discord: Server Settings -> Integrations -> Webhooks -> New Webhook
WEBHOOK_URL = "https://discord.com/api/webhooks/1234567890/your-token-here"

def post_to_discord(handle: str, text: str, url: str) -> None:
    payload = {
        "username": "Tweet Alerts",
        "embeds": [{
            "author": {"name": f"@{handle}"},
            "description": text[:2000],   # Discord embed limit
            "url": url,
            "color": 0x1DA1F2,
        }],
    }
    r = requests.post(WEBHOOK_URL, json=payload, timeout=10)
    r.raise_for_status()   # 204 No Content on success

# Example
post_to_discord("elonmusk", "gm", "https://x.com/elonmusk/status/123")

That is it. If you already had a stream of tweets, you would be done. The whole problem is producing that stream, so let's look at the three ways to feed the post_to_discord call above.

Option 1, DIY: read tweets yourself, POST to the webhook

Wrap the webhook code above in a loop that reads new tweets and calls it. Two ways to get the tweets, both painful:

• X API v2. The Basic tier is about $200/mo and its read caps are low. Watching a handful of accounts in real time means polling their timelines on a tight interval, which burns quota fast, and even then your worst-case latency is the poll interval, not real time. Reading many accounts pushes you into higher-cost tiers.
• Scraping. No dev account, but you own an anti-bot arms race: rotating IPs, logged-in sessions that get flagged, and markup that changes without notice. When it breaks, your Discord channel goes quiet until you patch it.

Either way, the Discord webhook is five minutes of work and the tweet-sourcing is the entire project, plus ongoing maintenance. If you do want to write custom filtering (keyword rules, contract-address regex), the pattern is worth learning, we walk through a full real-time consumer in the Python KOL alert bot tutorial. The difference is what feeds it.

Option 2, IFTTT / Zapier automations

The no-code route: an IFTTT applet or a Zapier zap with a "new tweet by user" trigger and a "post to Discord" action. It works without a server, but two things make it a bad fit for alerts:

• Slow. These platforms poll on their own schedule and batch runs. Delivery is typically minutes behind the tweet, sometimes much more on lower tiers. For anything time-sensitive that is too late.
• Unreliable since the API changes. After Twitter's API pricing shakeup, the Twitter/X triggers on these platforms became limited and drop events. A missed trigger is a tweet that never reaches your channel, and you rarely find out.

Fine for a low-stakes "log my own tweets somewhere" workflow. Wrong shape for "tell my server the instant this account posts."

Option 3, Managed real-time: a Discord bot that's already built

The third model skips both the API bill and the webhook-hosting. 1322 runs the detection layer continuously and includes a Discord bot that posts tracked-account events straight to your server. No X developer account, no scraping to maintain, no script to keep alive. On X, events arrive typically within 150-250ms of the tweet. Setup is three steps:

• Add accounts to your tracked list in the dashboard.
• Link your Discord server to the bot.
• Events appear in your channel as accounts post, no code.

If you outgrow the built-in bot and want your own filtering, the same feed exposes a WebSocket and REST API, so you can run the Option-1 webhook script but with a reliable, sub-second source behind it instead of the X API. Delivery is not Discord-only either: there is a Telegram bot and signed webhooks to your own backend. More on the no-code delivery bots: Discord & Telegram alert bots, and the underlying feed: Twitter WebSocket API.

Honest comparison

If tweets in Discord are a nice-to-have and minutes are fine, an automation platform is the cheapest start. If you need custom filter logic and are willing to pay and maintain the X API, DIY gives you full control. If you want tracked accounts in your server within a few hundred milliseconds and no infrastructure to run, the managed feed with the included bot is the low-effort real-time option, see pricing.

FAQ