How to Set Up FiveM Server Status Alerts in Your Discord

Add your server to CFXR's watchlist and configure a Discord webhook as the alert destination. From then on, status changes — the server going offline, coming back online, crossing a player-count threshold, or changing its reported details — post directly into whichever Discord channel you pointed the webhook at, with no bot hosting or code required.

Manually checking a server's status means someone has to remember to look, and outages that happen overnight or during a busy day routinely go unnoticed until a player complains in a support channel. Pushing status changes into Discord instead turns monitoring into something that happens automatically and is visible to whoever is already watching the server — which for most communities is staff already active in Discord around the clock. It also creates a timestamped record of exactly when a server went down and came back, which is useful when troubleshooting with a host or explaining downtime to players afterward.

On the watchlist page, add the server by its join code or cfx.re link, then attach a notification channel to it. CFXR supports a per-server Discord webhook, a generic JSON webhook for your own automation or dashboard, or email — the Discord webhook is the most common choice for community servers since it needs no separate hosting or bot process to run. Paste the webhook URL from your Discord channel's integration settings into the watchlist configuration and it starts receiving alerts for that server immediately.

Not every alert type is useful for every community. Online/offline transitions are the baseline most servers want — they tell you the moment a server goes down and the moment it recovers. Player-count thresholds are worth adding if you want to catch a partial problem, such as an unexpected mass disconnect that doesn't take the server fully offline. Server-detail change alerts, which fire when the server's reported name or resource list changes, are more useful for tracking a server you don't operate yourself — for example, keeping an eye on a partner or competitor community — than for your own server's day-to-day monitoring.

Before treating the Discord channel as your source of truth for server status, confirm the alert actually fires. Take the server offline briefly during a low-traffic window, or lower the player-count threshold temporarily, and check that the message lands in the expected channel. It is worth doing this once after initial setup and again any time you change the webhook URL or move the alert to a different channel, since a silently broken webhook gives you false confidence that monitoring is working when it isn't.

It is also worth periodically re-testing an alert you set up months ago. Discord webhooks can be invalidated if a channel is deleted or recreated, and a watchlist entry that was configured correctly at launch can go quiet without anyone noticing until an actual outage goes unreported. Treat the alert channel the same way you would any other piece of monitoring infrastructure — something to periodically confirm is still working, not something to set up once and forget.