Do I need a custom Slack bot?

Not for Incoming Webhooks. Use a bot only if you want richer Block Kit UI or thread replies — then verify HMAC on your server and call Slack Web API.

Is Discord supported the same way?

Yes — see /twitter-discord-alerts. Discord and Slack URLs are auto-detected.

Documented at /docs/integrations/make — Custom Webhook trigger → Slack.

Slack alerts

Watch public @handles and push matches into Slack. XFlux formats Slack Incoming Webhook payloads for you — or send signed JSON to your own Slack bot.

Paste the Slack webhook URL on a monitor. We adapt the message body for Slack’s expected JSON.

Prefer no-code? Custom Webhook in Make.com → Slack module. Same monitor.hit events.

Only alert when posts match tickers, product names, or macro phrases.

1
Create a Slack Incoming Webhook
In Slack apps, add Incoming Webhooks and copy the URL for your channel.
2
Attach it to an XFlux monitor
Dashboard → Monitors → Webhook → Save → Test. Free allows test pings.
3
Upgrade for live hits
Starter delivers when new tweets match. Discord users: see /twitter-discord-alerts.

XFlux detects Slack webhook hosts and posts a Slack-compatible payload.

XFlux monitor hit
        ↓
Slack Incoming Webhook URL detected
        ↓
POST { "text": "@handle: tweet text…" }
        ↓
Channel message in Slack

Do I need a custom Slack bot?: Not for Incoming Webhooks. Use a bot only if you want richer Block Kit UI or thread replies — then verify HMAC on your server and call Slack Web API.
Is Discord supported the same way?: Yes — see /twitter-discord-alerts. Discord and Slack URLs are auto-detected.
Make.com path?: Documented at /docs/integrations/make — Custom Webhook trigger → Slack.

Free includes 1 monitor and Dashboard hit history. Live webhook delivery starts on Starter ($19/mo).