Integrations
Integrations connect Ticket Tool to the external apps you already use. Connect an app once, then use it to look up customer details inside a ticket, escalate bugs to your tracker, post to chat, copy transcripts to your own storage, or open tickets automatically when something happens in that app.
Plans
Commerce, escalation, productivity and storage apps, Custom HTTP, Incoming Webhook and inbound triggers are on Pro. The lookup connections (Bloxlink, BattleMetrics and Roblox Open Cloud) and game server plugin keys are on Community and Pro. Free servers see an upgrade prompt.
Where to find them
Everything lives in the Automations group of the dashboard, and needs the Manager role (the manageAutomations permission):
Connections
Connect apps, manage their credentials and create game server plugin keys.
Rules
Inbound triggers: when an app sends an event, open a ticket, post a message or run a flow.
Activity Logs
Each inbound event, as a rule run, and each call a flow makes to a connected app, with status and errors.
API tokens, ticket webhooks and Twilio SMS are a separate page, Settings & Access → API & Webhooks. See the API Reference and Notifications.
Supported apps
Some apps only send data out (outbound actions), and some can also receive events (inbound triggers).
Commerce
These look up a customer's status and most can open tickets on store events.
| App | What it does | Credential |
|---|---|---|
| Whop | Look up a member's plan; react to membership and payment events | API key |
| Stripe | Look up a customer, subscription or recent charges, make a billing portal link, cancel at period end; react to charges, refunds, disputes, checkouts and subscription changes | Secret key (a restricted key works) |
| Patreon | Look up a patron by email; react to member and pledge events | Creator access token |
| Sellix | Look up a buyer's latest order or one order; react to order and subscription events | API key |
| Tebex | Look up a player's purchases or one payment; react to payments, refunds, disputes and subscriptions | Server secret |
| Lemon Squeezy | Look up a buyer's order or subscription; react to orders, refunds and subscription changes | API key |
| Paddle | Look up a customer and their subscription; react to transactions, refunds and subscription changes | API key (sandbox keys call the sandbox) |
| Gumroad | Look up a buyer's latest sale or check a license key (lookups only) | Access token |
| Ko-fi | React to donations, memberships, commissions and shop orders (events only) | Verification token |
Escalation and productivity
| App | What it does | Credential |
|---|---|---|
| GitHub | Create, comment on, close, reopen, label, look up and search issues; react to issue, comment, pull request and release events | Personal access token with issue write access |
| Linear | Create, comment on, move and look up issues; react to issue and comment events | API key |
| Jira | Create, comment on, transition and look up issues in Jira Cloud | Site, email and API token |
| Trello | Create, comment on and move cards | API key and token |
| ClickUp | Create, comment on, update the status of and look up tasks | Personal API token |
| Asana | Create, comment on, complete and look up tasks | Personal access token |
| Slack | Post a message, post with a link button, or reply in a thread | Bot token with chat:write |
| Notion | Add a page to a database, append text to a page, set a select property | Internal integration secret |
Any other app
| App | What it does | Credential |
|---|---|---|
| Incoming Webhook | A URL any app, form tool or script can post to, so its events run your rules. See Inbound Triggers | None (Ticket Tool makes a secret) |
Storage
Receives a copy of each ticket transcript. See Copy Transcripts to Your Own Storage.
| App | What it does | Credential |
|---|---|---|
| S3-compatible storage | Copy transcripts to AWS S3, Cloudflare R2, Backblaze B2 or similar | Access key ID and secret access key |
| Google Drive | Copy transcripts to a folder in your Google Drive | Google sign-in (drive.file only) |
Lookups
Used by a category's player lookups and ban lookup when a ticket opens.
| App | What it does | Credential |
|---|---|---|
| Bloxlink | Find the opener's linked Roblox account | Bloxlink server API key |
| BattleMetrics | Check the opener's bans in your BattleMetrics organization | Personal access token |
| Roblox Open Cloud | Check the opener's bans in your Roblox experience | API key with universe.user-restriction:read, plus the universe ID |
| Custom HTTP | Authenticate a Custom HTTP lookup or an API Request node to your own API (Pro) | Header value (Bearer token or key), plus the address it may be sent to |
Your own Minecraft, FiveM, RedM, Garry's Mod, Rust or CS2 server can answer lookups too, through a plugin key instead of a connection. See Game Server Plugins.
Connecting an app
Pick the app
Go to Dashboard → Automations → Connections and pick an app from the gallery.
Enter credentials
Paste the credential for that app (each field has a hint for where to find it in the provider's dashboard). You can give the connection a name if you run more than one of the same app.
Save
Ticket Tool checks the credential before it saves it, and a credential the app rejects isn't saved. Credentials are encrypted before they are stored and are never shown again. Editing a connection later shows a masked value, so leaving a field untouched keeps the existing secret.
Test it later
Use Test connection on the connection at any time to confirm the credential still works. The status shows active or error, plus when it was last used.
Credentials are write-only
Once saved, a credential cannot be viewed again, only replaced. Store the original somewhere safe (a password manager), and use a read-scoped or restricted key where the provider supports one.
Using an app inside a flow
Connected apps show up in the flow editor's node picker under AI & Integrations, one entry per action, such as Stripe: Lookup Customer or GitHub: Create Issue. Each adds an Integration node, which is Pro.
Add the action
In the flow editor, open the node picker and pick the app's action. Apps you haven't connected appear grayed out until you do.
Fill the inputs
Provide the values the action needs. You can reference flow variables with double braces, for example {{responses.email}} or {{user.id}}.
Use the result
The node saves the response into flow variables (for example a customer id or plan name) that later nodes can read. It has separate success and error branches, so you can handle a failed lookup gracefully.
For fields like the repository, team, channel, database, project or list, the field suggests choices from the connected account as you click into it. You can still type a value or a {{variable}} instead.
Linked tickets
When a flow running in a ticket creates an issue, card, task or page (for example GitHub: Create Issue), the ticket remembers it. Linked items show under Connected apps in the ticket's side panel, with a link to open them and a button to unlink.
GitHub and Linear also send events about those issues. A rule on an event such as Issue closed can then Post in the linked ticket or Close the linked ticket, so customers hear back when the fix ships. See Inbound Triggers.
Without a flow
For a single action you don't need a flow:
- From a rule. Pick Do something in a connected app as a rule's action, for example to comment on the linked GitHub issue when a ticket closes. See Automation Rules.
- By hand. Admins with the Manage Settings permission can use Run an app action under Connected apps in a ticket's side panel. Ticket variables such as
{{ticket.number}}work in the fields, and the result shows once it runs.
Custom HTTP in API Request nodes
An API Request node can sign in with a saved Custom HTTP connection instead of a token typed into the flow. Pick Saved connection as its authentication. The connection's Only send to address is required for this: the token is only ever sent to URLs under that address, so someone editing a flow can't send it anywhere else.
Common uses: look up a buyer's order the moment a billing ticket opens and show it to staff, or create a GitHub issue when a bug-report flow finishes.
Logs
Automations → Activity Logs shows what each connection did, so you can debug failures:
- The Activity tab shows each inbound event that matched a rule, as a run of that rule marked Ran, Skipped or Error with the reason. See Inbound Triggers.
- The Logs tab lists the latest 100 calls that Integration nodes made to your connected apps, with the connection, Delivered or Error, any error message, and the time. Filter by status to find failures fast.
Related
Inbound Triggers
Turn store, GitHub, Linear and any other app's events into tickets
Player Lookups
Show staff who opened the ticket, from Roblox, your game server or your own API
Linked Accounts
See the Steam and other accounts a member shared with your server
Game Server Plugins
Open-source plugins for Minecraft, FiveM, Garry's Mod, Rust and CS2