Player Lookups
Game communities spend the first minutes of most tickets asking "what's your username?". A lookup answers that before anyone types: it runs the moment a ticket opens, fetches details about the member who opened it, and shows them to staff in an info card. You can also drop the results into the category's intro message, the "ticket created" DM, and any flow that runs for the ticket.
There are four kinds:
Roblox
The Roblox account the member linked through Bloxlink: username, display name, account age, verified badge and ban status. Community and Pro.
Minecraft
Asked of your own server's plugin: name, UUID, online or last seen. The member links their account in game. Community and Pro.
FiveM, Garry's Mod, Rust, CS2
Asked of your own server's plugin: name, online or last seen, and extra lines such as job or rank. Matched by Discord ID (FiveM) or the shared Steam account. Community and Pro.
Custom HTTP
Call your own API with the member's Discord ID and map fields from its JSON reply into variables. Pro.
Set it up
Add a connection
Go to Dashboard → Automations → Connections:
- For Roblox, add Bloxlink with a Bloxlink server API key. See Roblox Lookups.
- For your own API, add Custom HTTP only if the API needs a token. A public endpoint needs no connection. See Custom HTTP Lookups.
- For a game server, create a key under Game server plugins instead and install the plugin. See Game Server Plugins.
Ticket Tool checks a credential when you save it, so a wrong key fails here rather than in a ticket.
Turn it on for a category
Edit the category under Dashboard → Categories and open Game server tools at the bottom of the General tab. In the Lookups card, switch on Roblox and pick the Bloxlink connection, switch on a game (Minecraft, FiveM / RedM, Garry's Mod, Rust or Counter-Strike 2), or switch on Custom HTTP and fill in the request. You can use any combination.
Leave Post an info card on so staff see the results, then save.
Open a test ticket
Open a ticket from an account that has a linked Roblox account, or that has played on your game server, and check the card.
Where the info card appears
- If the category has a staff thread, the card is posted in that thread alongside its opening notice, out of the member's view.
- Otherwise the ticket gets a short notice with a View account lookup button. Pressing it shows the card privately to staff, so the member never sees it and it stays out of the transcript. The card can be opened for 24 hours.
If the member has no linked account for a lookup, the card says so. If a lookup doesn't answer in time, the card says it was unavailable.
Speed and reliability
- The lookup starts while the ticket channel is being created, so a quick source adds no wait.
- Every lookup gives up after 4 seconds. The ticket always opens: a slow, failing or misconfigured lookup only leaves its variables empty.
- Roblox and Custom HTTP results are cached for 10 minutes per member, so someone who opens several tickets in a row is looked up once. Game server plugins are asked on every ticket, so online status is current.
- Flows that run later in the ticket see the same values the intro did, for up to 24 hours after the ticket opened.
Use the results
Lookup variables work in the category's intro message, the "ticket created" DM, and anywhere flow variables do:
Thanks {{user.mention}}! {{#if roblox.name}}We found your Roblox account **{{roblox.name}}**.{{/if}}
To run a lookup from a flow instead, before a ticket exists or for a different member, add an Account Lookup node. It checks Steam, Roblox, Minecraft and the game server plugins, fills the same variables, and branches Found, Not found or Unavailable. See Account Lookups in Flows for a walkthrough. Custom HTTP is not part of the node; use an API Request node for your own API.
In a flow, a Condition node with the Has Roblox account preset sends linked members one way and everyone else another, for example to ask unlinked members to verify with Bloxlink first.
Every lookup variable is listed in the variables reference.