Integrations

Connect Bloxlink or your Minecraft server so Tickety can use your members' Roblox and Minecraft 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. There are two, both free for every server:

Bloxlink looks up the Roblox account a member linked through Bloxlink in your server.
Minecraft looks up the Minecraft account a member linked through DiscordSRV on your Minecraft server.

From then on you can greet someone by their Roblox or Minecraft username in a ticket welcome message, print their profile link in an application review, or check whether they are online on your server right now.

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.

Tickety reads what the other service already knows, it does not link anyone itself:

For Bloxlink, you need Bloxlink set up in this same Discord server, with members actually linked.
For Minecraft, you need a Paper or Spigot server running DiscordSRV, with members linked through DiscordSRV, and a port on that server you can open to the internet.

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.

Connect Minecraft

Install the plugin

Download Tickety Integration and put it in your server's plugins folder next to DiscordSRV, then restart the server. The Setting it up box on the page links to both plugins.

Edit its config

Open plugins/TicketyIntegration/config.yml:

enabled: true
port: 8080
authorization: changeme

Set port to a port your host lets you open, and replace changeme with a long random password. Restart the server again. Tickety refuses the default changeme, because anyone who knows your address could read your members' links with it.

Fill in the dashboard

In the Default list on the left, click Minecraft. Paste the password from authorization into Plugin Token, and put your server's address with that port in API URL, for example http://play.example.com:8080. The address has to be reachable from the internet: local and private network addresses are refused.

Turn it on

Switch Enable integration on, then save with the bar at the bottom of the page.

Tickety contacts the plugin before saving. A wrong token is refused with a message, and if your Minecraft server does not answer, the save is refused until it does, so check the address and that the server is online. You cannot switch the toggle on without both a token and an API URL.

Unlike the token, the saved API URL is shown back to you, so you can spot a typo.

Saved tokens

A 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`	Nothing saved yet, or for Minecraft, the token or the API URL is still missing
`Configured`	Everything is saved, but Enable integration is off
`Enabled`	On and working
`Needs token`	The service refused the saved token, so Tickety switched the integration off
`Check failed`	The last check did not go through

Placeholders

The Placeholder reference panel on the right lists what the selected integration adds. Click any row to copy it, then paste it into a message anywhere in the dashboard.

Roblox

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

Minecraft

Placeholder	Label in the panel
`{minecraft.player.uuid}`	Player UUID
`{minecraft.player.username}`	Username
`{minecraft.player.online}`	Online now, `true` or `false`
`{minecraft.player.firstPlayed}`	First joined
`{minecraft.player.lastPlayed}`	Last seen

Minecraft details are refreshed about once a minute, so online and lastPlayed stay close to live.

They work in ticket welcome messages and ticket channel names, the support hours notice, the replies to /new and /apply, AI support routing notices, automation messages (every trigger except panel automations) and honeypot DMs. The placeholder picker offers them in exactly those fields, and only once that integration is turned on. Anywhere else, such as panels, close messages or the welcomer, they are printed as typed.

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})

And this one tells staff who they are talking to on your Minecraft server:

Minecraft account: {minecraft.player.username}
Last seen: {timestamp(relative):{minecraft.player.lastPlayed}}

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 something is missing from its setup. The badge tells you which.
The member has never linked an account, through Bloxlink in this server or through DiscordSRV on your Minecraft server. There is nothing to look up.
The service could not be reached at that moment. For Minecraft, that usually means your server is offline or restarting.

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 the service answers again.

If the connection stops working

If the service starts refusing your saved token, for example because it was regenerated or revoked, 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.

On this page