txAdmin Discord logs: send every admin action to a channel

Does txAdmin send admin action logs to Discord natively?

No. txAdmin does not natively push its admin action log to a Discord channel. Every ban, kick, warn and restart is recorded in the panel's own history, and you can review it from the web interface, but there is no built-in option to forward those events to Discord. This has been a long-standing community request: at least two threads on the cfx.re forums ask for exactly this feature, and as of July 2026 it is still not part of txAdmin itself. txAdmin does ship a Discord bot integration, but it covers announcements and whitelist requests, not action logging. So if you searched for txAdmin Discord logs, the honest answer is that you need one small extra resource: a webhook script that listens to txAdmin's server events and posts them to your channel. The good news is that solid free options exist, and setup takes minutes.

How does webhook-based Discord logging work?

Webhook-based logging is the mechanism every free solution uses to make txAdmin log admin actions to Discord, and it works in three steps. First, txAdmin fires server-side events whenever an admin acts: txAdmin:events:playerBanned, txAdmin:events:playerKicked or txAdmin:events:playerWarned, plus others for restarts and shutdowns. Second, a small resource running on your FXServer listens for those events, reads the data they carry (who acted, who was targeted, the reason and the duration) and formats it as a Discord embed. Third, it sends that embed with an HTTP POST to a webhook URL you create in your Discord channel settings. The outcome is a channel that fills up with a timestamped, readable record of every admin action, without giving anyone extra access to the txAdmin panel, and with negligible performance impact because everything runs server-side.

• Keep the webhook URL server-side. Put it in the script's server config or a convar; never reference it in a client file, or players can extract it.
• Treat it like a password. Anyone with the URL can post arbitrary messages to your channel. If it leaks, delete the webhook in Discord and create a new one.
• Restrict the log channel. Make it read-only for staff so entries cannot be quietly deleted.

Which free scripts send txAdmin logs to Discord?

Two free scripts cover most servers, and both work exactly as described above. WX txAdmin Logs is a free release published on the cfx.re forums: you drop it into your resources folder, set your webhook URL and it starts posting txAdmin actions as Discord embeds. jhag01/txAdminLogs is an open-source alternative hosted on GitHub with the same approach; since the code is public, you can read exactly what it sends and adapt the embed format to your liking. Neither needs a database or a framework dependency, and both rely only on txAdmin's public events, so they keep working across server restarts without special care. If you also want visual context, the free screenshot-basic resource can push still screenshots to a Discord webhook, which pairs well with a text log of the action itself.

• WX txAdmin Logs (free, cfx.re release): quick setup, embeds for bans, kicks, warns and server events.
• jhag01/txAdminLogs (free, GitHub): open source, easy to fork and customize.

How do you set up txAdmin Discord logs step by step?

Setting up txAdmin Discord logs takes about ten minutes and touches neither your framework nor your database. The process is the same whichever script you pick: you create a webhook in the Discord channel that should receive the log, install the resource on your server, give it the webhook URL in its server-side configuration and restart the resource. From that moment on, every ban, kick, warn and restart triggered from txAdmin appears in your channel as an embed showing the admin, the target player, the reason and the time. Before announcing it to your whole staff team, test it with a harmless action, such as a warn on a test account, and confirm the entry arrives with the fields you expect. If nothing shows up, the webhook URL is almost always the culprit.

1. Create the webhook. Open your Discord channel settings, go to Integrations, create a webhook and copy its URL.
2. Install the script. Download WX txAdmin Logs from the cfx.re forums or jhag01/txAdminLogs from GitHub and place it in your resources folder.
3. Configure the URL server-side. Paste the webhook URL into the script's server config. Never put it in a client file.
4. Start the resource. Add the ensure line to your server.cfg and restart.
5. Test it. Issue a warn from txAdmin and check that the embed lands in your channel.

How do you review what actually happened behind a log entry?

A Discord log tells you that an action happened; it rarely tells you whether it was justified. That is where a monitoring panel complements the webhook. FiveMonitor is not a Discord logger and it is not an anticheat: it does not detect cheats or ban anyone. It is a web panel for FiveM server owners and staff that acts as the eyes layer: you can watch live video of any player's screen (capture runs on the player's client, so the impact on server FPS is 0%), monitor several players at once, and check each player's accumulated playtime, read from txAdmin's own playersDB.json. When a ban shows up in your Discord channel and the player appeals, your staff can cross-check in the panel what the player was doing, how long they have been in the community, and whether the story holds up.

Playtime reading requires starting FXServer with --allow-fs-read, covered in the allow-fs-read setup guide. To see the full picture, check how live player monitoring works and how to track playtime, or browse everything the panel does on the features page. Each staff member can have their own sub-user with a Discord login, so the person named in the Discord log is also the person signed into the panel.

What is the best setup for FiveM admin logs in Discord?

For most servers, the best setup for FiveM admin logs in Discord combines three free or low-cost layers. Use txAdmin as the source of truth: it is free, ships with FXServer and already records every action. Add a free webhook script (WX txAdmin Logs or jhag01/txAdminLogs) so those actions land in a Discord channel your staff actually reads. Then add a review layer if your community is big enough to generate disputes: a panel where staff can watch players live and check their history before confirming or lifting a punishment. The Discord channel gives you the permanent, shareable trail; the panel gives you the context behind each line. Neither replaces the other, and the webhook part costs nothing, so you can have it running this afternoon and decide on the review layer later.

If you want that review layer, FiveMonitor plans start at 9.99 EUR/month (Basic) and 15.99 EUR/month (Pro, unlimited players) as of July 2026, with a 7-day free trial and no card required. Check the pricing page or create your account and start the free trial.