Integrations
Connect Bloxlink so Tickety can use your members' Roblox details in any message.
An integration connects Tickety to a service you already run, and hands you that service's data as placeholders you can drop into any message. Today there is one, Bloxlink, and it is free for every server.
Connect it and Tickety can look up the Roblox account a member linked through Bloxlink in your server. From then on you can greet someone by their Roblox username in a ticket welcome message, print their profile link in an application review, or put their account age in a welcome card.
Integrations bring data into Tickety. HTTP Events sends data out of Tickety to a server you run, and lives under Settings instead. They are two different features.
Access the Web Dashboard
Open your Tickety Dashboard. Log in using your Discord Account.
Navigate to Integrations
-
Once logged in, find the Server section in the sidebar.
-
Select Integrations.
Before you start
You need to be the server owner or an administrator, or hold a role with Full Dashboard Access under Settings > Access Control. See Settings for that.
You also need Bloxlink set up in this same Discord server, with members actually linked. Tickety reads what Bloxlink already knows, it does not link anyone itself.
Connect Bloxlink
Open the integration
In the Default list on the left, click Bloxlink. The badge on the row tells you where you stand.
Get your token
Open your Bloxlink dashboard in another tab, select this Discord server, and copy the Server API token from the developer area. The Need a token? box on the page has an Open Bloxlink dashboard button that takes you there.
Paste it in
Put the token in Server API Token. It accepts up to 500 characters, and the field is masked.
Turn it on
Switch Enable integration on, then save with the bar at the bottom of the page.
Tickety checks the token with Bloxlink before saving, so a wrong or expired token is refused right there with a message rather than failing quietly later. You cannot switch the toggle on without a token.
The saved token is never shown back to you. Once one is stored, the field reads Token saved. Enter a new token to replace it., and saving with the box left empty keeps the token you already have.
What the status badge means
| Badge | What it means |
|---|---|
Not configured | No token saved yet |
Configured | A token is saved, but Enable integration is off |
Enabled | On and working |
Needs token | Bloxlink refused the saved token, so Tickety switched the integration off |
Check failed | The last check did not go through |
Roblox placeholders
The Placeholder reference panel on the right lists what the integration adds. Click any row to copy it, then paste it into a message anywhere in the dashboard.
| Placeholder | Label in the panel |
|---|---|
{roblox.bloxlink.id} | Roblox ID |
{roblox.bloxlink.url} | Profile URL |
{roblox.bloxlink.name} | Username |
{roblox.bloxlink.displayName} | Display name |
{roblox.bloxlink.about} | Profile bio |
{roblox.bloxlink.createdAt} | Created date |
They resolve anywhere member placeholders resolve: ticket messages, application messages, panels, welcome messages and DMs, and automation replies. They also appear in the placeholder picker under the Roblox group.
A ticket welcome message like this greets the member by their Roblox name and links their profile:
Hey {member.mention}, thanks for opening a ticket.
Roblox account: [{roblox.bloxlink.name}]({roblox.bloxlink.url})See Placeholders for everything else you can put in a message.
When a placeholder comes out empty
Three things cause it, in the order worth checking:
- The integration is off, or no token is saved. The badge tells you which.
- The member has never linked a Roblox account through Bloxlink in this server. There is nothing to look up.
- Bloxlink could not be reached at that moment.
In the third case the message prints the literal text {unavailable} where the value should be. If you see that word in one of your messages, you did not type it by mistake. It clears on its own once Bloxlink answers again.
If the connection stops working
If Bloxlink starts refusing your saved token, for example because it was regenerated or revoked on the Bloxlink side, Tickety switches Enable integration off by itself and the badge changes to Needs token.
Paste a fresh token, turn the toggle back on and save. Nothing else needs redoing, and every placeholder you already put in your messages starts working again.
Where to go next
- Placeholders: every value you can put in a Tickety message.
- Settings: Access Control, and the HTTP Events feature this page is often confused with.
- HTTP Events: send Tickety's events to a server you run.