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, or open tickets automatically when something happens in that app.
Pro feature
Integrations are available on the Pro plan. On Free and Community the Integrations tabs show an upgrade prompt. Servers that an organization plan provides the Pro tier to also get integrations.
Find them under Dashboard → Integrations. Managing integrations needs the Admin role (the manageSettings permission).
The Integrations page
The page has a few tabs:
Connected Apps
Connect external apps and manage their credentials.
Inbound Triggers
IFTTT-style rules: when an app sends an event, open a ticket or post a message. See the dedicated page.
Logs
Recent integration activity, inbound and outbound, with status and errors.
The same page also holds API tokens and ticket Webhooks (covered in the API Reference) and Twilio SMS setup (covered in Notifications).
Supported apps
Apps fall into three groups. Some can only send data out (outbound actions), some can also receive events (inbound triggers).
Commerce
These look up a customer's status and can open tickets on store events. All support both outbound lookups and inbound triggers.
| 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 or subscription by email; react to charges, invoices, subscriptions, disputes | Secret key (a restricted read key works) |
| Patreon | Look up a patron by email; react to member and pledge events | Creator access token |
| Sellix | Look up a buyer's most recent order; react to order events | API key |
| Tebex | Look up a player's purchases; react to payments, refunds, chargebacks | Server secret |
Escalation
Outbound only. Push ticket issues into your tracker.
| App | What it does | Credential |
|---|---|---|
| GitHub | Create an issue in a repository | Personal access token with issue write access |
| Linear | Create an issue on a team | API key |
Productivity
Outbound only.
| App | What it does | Credential |
|---|---|---|
| Slack | Post a message to a channel | Bot token with chat:write |
| Notion | Add a page to a database | Internal integration secret |
Connecting an app
Open Connected Apps
Go to Dashboard → Integrations → Connected Apps 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.
Connect
Save the connection. 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
Use Test on the connection to confirm the credential 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 become available in Support Flows through the Integration Action node. Use it to run a provider action partway through a flow and reuse the result in later steps.
Add an Integration Action node
In the flow editor, add an Integration Action node (under the advanced nodes).
Pick the connection and action
Choose one of your connected apps, then the action to run, for example "Look up customer" for Stripe or "Create issue" for GitHub.
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. The node has separate success and error branches, so you can handle a failed lookup gracefully.
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
The Logs tab lists recent integration activity so you can see what happened and debug failures. Each entry shows the direction (inbound event or outbound action), the connection, a status of delivered, error, or skipped, any error message, and the time. Filter by status to find failures fast. The most recent activity is kept per server.
What's next
Outbound actions are only half of it. To have an external app open tickets or post messages automatically when something happens, set up inbound triggers.
Inbound triggers
See Inbound Triggers (IFTTT) to turn events from Whop, Stripe, Patreon, Sellix and Tebex into tickets.