Look Up Linked Accounts in a Flow
The Account Lookup node runs the same lookups a category's Lookups card runs when a ticket opens, but at any point in a flow. It fetches a member's linked accounts, fills the usual {{steam.*}}, {{roblox.*}}, {{minecraft.*}} and game server variables, and then branches on what it found. Later steps read those variables like any other.
Use it when the answer should change what happens next: only open a whitelist ticket for members with a linked Steam account, show a player's Minecraft stats before they pick a topic, or send members without a linked account to a "link it first" message instead of a ticket.
What you need
Community or Pro, the same as category lookups. Roblox also needs a Bloxlink connection, and the games need our plugin on your game server. Steam only needs members to link and share their account.
Add the node
Pick the accounts
Open a flow under Automations → Flows, choose Add Node and pick Account Lookup from Data & Notes. Tick the accounts to check: Steam, Roblox, Minecraft, FiveM / RedM, Garry's Mod, Rust or Counter-Strike 2. You can tick several.
Choose whose accounts
Ticket creator is the default. In a flow started from a panel button there is no ticket yet, so it looks up whoever pressed the button. You can also pick Last person to reply, or Specific user / variable and enter an ID or a variable such as {{source.user.id}}.
Wire the branches
The node has four outputs:
| Output | Taken when |
|---|---|
| Found | Any ticked source found an account |
| Not found | Every source answered and none found an account |
| Unavailable | Nothing was found and at least one source could not answer, such as plugin offline |
| Otherwise | Any of the three above that you left unconnected |
Connect only Otherwise if every result should carry on to the same step.
Example: whitelist only linked players
An interactive flow behind a Whitelist panel button:
- Account Lookup with Steam ticked.
- Found goes to Create Ticket, whose intro says
Welcome {{steam.name}}, you have {{steam.hours}} hours on record. - Not found goes to a Send Message step: "Link your Steam account on your Linked accounts page, share it with this server, then press the button again."
- Unavailable goes to Create Ticket too, so a slow Steam profile never blocks anyone.
The same shape works for Minecraft with {{minecraft.name}} and {{minecraft.online}}, or FiveM with {{fivem.details}} to show a character's job.
What later steps can use
The node writes the same variables the category Lookups card does. Each source's variables are empty when it found nothing, so a message never shows a raw placeholder.
| Variable | Meaning |
|---|---|
{{steam.name}}, {{steam.hours}} | The Steam account shared with this server |
{{roblox.name}}, {{roblox.age_days}} | The Roblox account from Bloxlink |
{{minecraft.name}}, {{minecraft.online}} | The linked Minecraft player |
{{fivem.name}}, {{rust.online}}, … | Game server players, per game |
{{_lookupStatus}} | found, not_found or unavailable |
{{_lookupFound}} | The sources that found an account, such as steam,minecraft |
The full lists are in variables reference. In the flow editor, steps after the node offer these variables in their Insert variable menu.
Good to know
- The node only reads accounts the member shared with your server, exactly like ticket lookups. It never sees an account they kept private.
- Only members of your server can be looked up. An ID for anyone else takes the Unavailable branch.
- Every source gives up after 4 seconds. Game server plugins answer live, so a slow plugin only makes that source unavailable.
- If your server's plan stops including lookups, the node takes the Unavailable branch without looking anyone up.
- It works in interactive and automation flows, and in automation flows that run without a ticket.