How to Connect txAdmin to Discord (2026 Guide)

Goal: Enable txAdmin’s native Discord integration for status embeds and (optional) Discord‑backed whitelisting.

This guide is part of our complete FiveM server management hub, covering everything from initial setup to scaling your community.

Works with any FXServer build that includes txAdmin. No third‑party hosting or bot framework required.

Running txAdmin without Discord integration means your community has no way to see server status, scheduled restarts, or player counts without launching the game. Connecting txAdmin to Discord takes about 15 minutes and gives you a live embed that updates every few seconds — a visible sign of server health that builds trust with your player base before they even connect.

This guide covers the full setup from bot creation to whitelist configuration, plus advanced embed customization and common mistakes that trip up most server owners on the first attempt.

---

Prerequisites

• A running FiveM server with txAdmin enabled (Settings → Global shows the panel is active).
• Permission to create a Discord application in your Discord Developer Portal.
• Developer Mode enabled in your Discord user settings (so you can copy Server/Channel/Role IDs).
• The Guild (Server) ID and (optionally) a Channel ID where the bot is allowed to post.

---

Step 1 — Create the Discord Application & Bot

1. Open the Discord Developer Portal and click New Application.
2. Inside the application, go to Bot → Reset Token and copy the Bot Token. Keep it secret.
3. On the same Bot page, enable SERVER MEMBERS INTENT. Save.

Tip: You don’t need the Presence or Message Content intents for txAdmin’s built‑in features.

---

Step 2 — Invite the Bot to Your Discord Server

1. In the Developer Portal, open OAuth2 → URL Generator.
2. Scopes: select bot and applications.commands (slash commands).
3. Permissions: select View Channels, Send Messages, Embed Links, Read Message History.
4. Use the generated URL to invite the bot to your Discord server.

Keep permissions minimal

Keep permissions minimal. The bot only needs to read/post and embed.

---

Step 3 — Wire the Bot in txAdmin

1. Open your txAdmin web panel.
2. Go to Settings → Discord.
3. Toggle Enable Discord Bot.
4. Fill the fields:
   • Bot Token: paste the token from Step 1.
   • Guild ID: your Discord Server ID (right‑click server icon → Copy ID).
   • Announcements Channel ID (optional): a channel ID where txAdmin can post status/restart notices.
   • Save.

Add the Live Status Embed

• In your chosen Discord channel, type: /status add
• txAdmin will post a persistent embed that auto‑updates with server info.

Customize the Status Embed (optional)

• In txAdmin → Settings → Discord, open Change Embed JSON to edit title, description, fields, thumbnail, buttons/links, etc.

---

Step 4 — (Optional) Discord‑Backed Whitelist in txAdmin

You can gate server access by Discord membership or role.

1. In txAdmin, go to Settings → Player Manager.
2. Whitelist Mode: choose one of:
   • Discord Member – anyone in your Discord can join.
   • Discord Role – only members with specified role IDs can join.
   • If using Discord Role, collect role IDs (Server Settings → Roles → right‑click role → Copy ID).
   • Add the role IDs to the whitelist settings. Save.

Approve/Manage Requests:

Approve/Manage Requests:

• Go to Player Manager → Whitelist to review requests and approvals.

Prefer role‑based whitelisting for better control. Update your Discord role assignment workflow accordingly.

---

Troubleshooting

• Saving Discord settings times out → Ensure SERVER MEMBERS INTENT is enabled for your bot in the Discord Developer Portal.
• Slash commands (/status, /info) don’t appear → Re‑invite the bot with the applications.commands scope; make sure it can see the channel.
• Status doesn’t post/update → Verify channel permissions: the bot needs View Channel, Send Messages, Embed Links, Read Message History.
• No messages from txAdmin → Double‑check the Guild ID/Channel ID values and that Developer Mode is enabled when copying IDs.
• Noise in announcements channel → Leave Announcements Channel ID empty in Settings → Discord (txAdmin won’t auto‑post announcements).

---

Step 5 — Advanced Embed Customization

The default txAdmin status embed is functional, but you can make it significantly more informative and on-brand by editing the embed JSON directly.

In txAdmin → Settings → Discord, click Change Embed JSON. The JSON controls every visual aspect of the embed: title, description, fields, footer, thumbnail, and action buttons. Here is a fully commented example you can paste and adapt:

{
  "title": "🎮 MyServer — Live Status",
  "description": "Connect: `connect myserver.com`\nDiscord: discord.gg/myserver",
  "color": 3066993,
  "thumbnail": {
    "url": "https://cdn.discordapp.com/icons/YOUR_SERVER_ID/YOUR_ICON_HASH.png"
  },
  "fields": [
    {
      "name": "🟢 Status",
      "value": "{server_status}",
      "inline": true
    },
    {
      "name": "👥 Players",
      "value": "{players_current}/{players_max}",
      "inline": true
    },
    {
      "name": "⏱️ Uptime",
      "value": "{uptime}",
      "inline": true
    },
    {
      "name": "🗺️ Current Time",
      "value": "{server_time}",
      "inline": true
    }
  ],
  "footer": {
    "text": "Last updated"
  },
  "timestamp": true
}

Available embed variables (txAdmin replaces these at render time):

Variable	Output
{server_status}	Online / Offline / Starting
{players_current}	Current connected player count
{players_max}	Configured max player slots
{uptime}	Human-readable server uptime
{server_time}	In-game clock time

The color field is a decimal integer. Convert hex color codes at any "hex to decimal" converter — for example, #2ECC71 (green) becomes 3066993.

---

Running the Bot on Multiple Servers

If you operate more than one FiveM server, you do not need a separate Discord application for each. A single bot application can be configured independently per txAdmin instance:

1. Create one Discord Application and bot in the Developer Portal.
2. Invite the bot to your Discord server once with the scopes from Step 2.
3. In each txAdmin instance (running on different ports), go to Settings → Discord and paste the same Bot Token.
4. Use a different Guild ID and Channel ID for each txAdmin instance.
5. Run /status add in the appropriate channel for each instance.

Each txAdmin instance manages its own embed independently, so you can track multiple servers from separate channels in one Discord guild — useful for network operators managing several game modes or test servers.

---

Common Mistakes to Avoid

Getting the bot online in Discord is only half the battle. These are the issues that cause the most support tickets:

1. Copying the Client ID instead of the Bot Token The OAuth2 screen shows a Client ID (a public number). The Bot Token is under the Bot tab after clicking Reset Token. These are different. txAdmin needs the token, not the client ID.

2. Forgetting SERVER MEMBERS INTENT This is the most common cause of "Saving Discord settings times out." The intent must be toggled on in the Bot tab of the Developer Portal, then saved there before pasting the token into txAdmin. If you already pasted the token before enabling the intent, simply save the txAdmin settings again — it will re-authenticate.

3. Wrong ID type (Server vs. Channel) The Guild ID is the Discord server's ID (right-click the server icon in the sidebar). The Channel ID is a specific text channel's ID (right-click the channel name). Pasting a channel ID into the Guild ID field is a silent failure — the bot authenticates but cannot match the server.

4. Bot not in the channel's permission list Even if the bot has the correct guild-level permissions, Discord's channel permission overrides can block it. Open the channel's Edit Channel → Permissions, add the bot's role, and explicitly Allow: View Channel, Send Messages, Embed Links, Read Message History.

5. Using /status update when you should run /status add /status add creates a new persistent embed in the channel. /status update refreshes an existing one. If no embed exists yet, /status update fails silently. Always start with /status add.

---

Discord Whitelist Strategy

Role-based whitelisting is the most powerful trust layer you can add to your server without writing custom code. Here is how to structure it effectively:

Recommended Role Hierarchy

Role	Whitelist Action	Notes
@Newcomer	Not whitelisted	Applied on Discord join
@Verified	✅ Whitelisted	Applied after reading rules/verification
@Trusted Member	✅ Whitelisted	Extended community member
@Staff	✅ Whitelisted	Always has access

Keep the whitelist roles to a small, controlled list. Avoid whitelisting @everyone — if your Discord server is public, anyone can join and immediately connect to the game without community vetting.

Automating Role Assignment

Consider pairing txAdmin's whitelist with a Discord verification bot (like Wick, Carl-bot, or YAGPDB) to automate the @Verified role assignment after new members complete your onboarding flow (reading rules, reacting to a message, etc.). This removes the manual work from staff while keeping the whitelist meaningful.

---

Security Notes

• Treat the Bot Token like a password. Rotate it if exposed (Developer Portal → Bot → Reset Token, then update txAdmin settings).
• Avoid granting Administrator or unnecessary permissions — the bot only needs to read and post.
• Restrict the bot to a single posting channel when possible. Use Discord's channel permission overrides to prevent it from reading other channels.
• Never commit your bot token to a public GitHub repository or paste it in any public chat. Discord automatically revokes tokens detected in public repos, but the damage window can still be exploited.
• Review your bot's permission scope quarterly. Discord occasionally adds new permission requirements — keep the bot's role trimmed to what it actively uses.

---

Related Guides & Resources

• txAdmin (official site): https://txadmin.gg/
• How to Set Up a Discord Whitelist for Your FiveM Server (FAXES/DiscordWhitelist) — vertexmods.com: https://vertexmods.com/blog/discord-whitelist-fivem
• Browse FiveM scripts for server management — https://vertexmods.com/fivem-scripts

---

Quick Checklist (Copy/Paste)

• Bot created; SERVER MEMBERS INTENT enabled
• Bot invited with bot + applications.commands scopes
• Permissions: View, Send, Embed, Read History
• Bot Token + Guild ID (and optional Channel ID) saved in txAdmin
• /status add run in the target channel
• Status embed JSON customized with server branding
• (Optional) Whitelist Mode set to Discord Member/Role; role IDs saved
• (Optional) Discord verification bot configured to auto-assign whitelist role

---

Frequently Asked Questions

Does the txAdmin Discord bot work with free Discord accounts?

Yes. The Discord Developer Portal and bot creation are fully free. You do not need Discord Nitro or any paid tier to create a bot application, invite it to your server, or use slash commands. The only requirement is having Manage Server permission in the Discord guild where you want the bot to operate.

Can I use the same bot token on multiple txAdmin instances?

Yes. A single Discord application (and its bot token) can be connected to multiple txAdmin instances simultaneously. Each instance posts to its own designated channel using its own Guild/Channel ID configuration. The bot appears as a single entity in your Discord server regardless of how many txAdmin panels use it.

My status embed stopped updating after a few hours. What happened?

The most common cause is a Discord rate limit or a permission change. Check the txAdmin console for [Discord] log entries — txAdmin will report rate limit hits or HTTP errors there. Also verify the bot still has Embed Links and Send Messages permissions in the channel. Occasionally, Discord refreshes OAuth tokens under the hood; if the embed never recovers, reset the bot token in the Developer Portal and re-enter it in txAdmin Settings.

Is Discord-backed whitelisting secure enough for a serious RP server?

It provides a meaningful barrier, especially when combined with Discord's verification features (phone verification, CAPTCHA). However, Discord accounts are free to create, so a determined bad actor can bypass role-based whitelisting by rejoining with a new account. For high-security servers, consider pairing txAdmin's whitelist with a manual staff review step or a third-party identity verification bot before granting the whitelist role.

Can I disable the whitelist temporarily without losing my configuration?

Yes. In txAdmin → Settings → Player Manager, change the Whitelist Mode to Disabled. Your role IDs and other settings remain saved. Switch it back to Discord Role or Discord Member whenever you want to re-enable it — no reconfiguration needed.