Integrations

GitHub

Open the dashboard Service status Get support

Open GitHub issues straight from a ticket with /issue — using your repositories' issue templates, filled in from Discord, and linked back to the ticket.

The GitHub integration turns a support conversation into a tracked issue without leaving Discord. Inside a ticket, a support member runs /issue, picks a repository and one of its issue templates, fills in the template's fields, and the issue is created on GitHub — with your default labels and assignees — and linked to the ticket.

Connect with the GitHub App (recommended) or paste an access key. Integrations cost no feature token.

Find it under Integrations → GitHub in the dashboard. Connecting requires administrator rights on the Discord server.

Connect your GitHub account

Use the GitHub App, or paste an access key.

installationId

connect

GitHub App — recommended. Connect with GitHub opens GitHub's installation page; choose the account and the repositories to share. The field then shows GitHub App connected with the account name. Already installed the app on that account? Use Already installed?, enter the org or username, and pick up the existing installation.

token

text

Access key — the alternative to the App: a personal access token with issue read/write on the repositories you want to use. Encrypted at rest; when editing later, leave it blank to keep the current key. Clarify prefers the App installation when both are present.

accountLabel

text

An optional label for your own reference.

Which repositories?

repositories

fetched-select

Only the repositories you select can be used from a ticket. Required. The list shows what the App installation grants (or what the access key can see); Reload refreshes it after you change the installation on GitHub.

Issue defaults

Applied to every issue Clarify opens.

titlePrefix

text

Text put in front of every issue title, for example [Support] . Optional.

defaultLabels

Templates

Repository issue templates are offered automatically: Clarify reads the YAML issue forms in a repository's .github/ISSUE_TEMPLATE folder and turns their fields into a Discord form.

allowBlankIssue

toggle

Offer a Blank issue — title and description only — for repositories that have no template. Default: on. With this off, such repositories are not offered.

Discord forms hold five fields. A template with more text fields than that is trimmed to the first five; dropdowns and checkboxes are asked in a second step.

Who can create issues?

allowedRoles

role-select

The roles allowed to run /issue. Empty means any support role.

Using it in a ticket

Start

Run /issue inside the ticket. A ticket that already has a linked issue tells you so; add force:True to create another one anyway.

Pick a repository and a template

Only your selected repositories are offered, and only those with templates unless blank issues are allowed.

Fill in the form

The template's title and fields appear as a Discord form; dropdowns and checkboxes follow in a second step. Each step waits a minute for you.

Done

You get an Open Issue link, and a permanent GitHub issue linked card with the issue number is posted into the ticket. The dashboard shows the link on the ticket as well.

The issue body contains the answers you gave to the template's fields — not the ticket conversation. Copy anything the developers need into the form.

A blueprint button with the custom id module@github:trigger starts the same flow from any ticket message, for teams that prefer a button to a command.

Frequently asked

Cards & placeholders

Add a GitHub button to a ticket card.

Encryption

How Clarify stores access keys.

All integrations

Stripe, PayPal, Tebex, Patreon and webhooks.

Patreon

Connect your Patreon campaign so a customer's membership shows up on their ticket automatically — from their linked Discord account or their member ID.

Data connectors overview

Connect your own shop, CRM, licence server or any HTTP API and show its data to your team on the ticket — no code.