App integrations

A workspace admin turns an app on once for the workspace. Go to Settings → Apps (/w/<workspace>/admin/settings/apps) and toggle Confluence, Jira, or GitHub on. Until an app is enabled it won’t appear in the composer, and pasted links from that service won’t expand into cards.

Integrations use per-user sign-in: everyone who wants to use an app connects their own account once. The first time you run a command you’ll see a Connect button — click it, approve access in the popup, and you’re set. Actions then run as you, so the source service enforces your own permissions (you can’t merge a PR or move an issue you don’t have rights to).

You can review or disconnect linked accounts any time from your profile’s connected-apps settings.

There are three ways to bring something in:

• Slash commands — type / to see the apps enabled in your workspace, then e.g. /confluence runbook, /jira login bug, or /github auth to search and pick a result.
• The “+ App” button in the composer opens the same picker.
• Paste a link — drop a Confluence page, Jira issue, or GitHub pull-request URL into a channel and it automatically expands into a rich card.

Whatever you pick is sent as a card in the message — and on the providers below, the card carries inline actions.

Search your Confluence pages with /confluence <terms> and drop the result in as a card showing the title, space, and an excerpt. Pasting a Confluence page URL expands it the same way. It’s a rich, deep-linked preview — tap to open the page in Confluence.

Search issues with /jira <terms> or paste a browse/KEY-123 link to get an issue card with its key, status, assignee, and priority. From the card you can:

• Assign to me — take the issue in one click.
• Transition — move it through its workflow (e.g. To Do → In Progress → Done) with a button per available transition.
• Create an issue — type /jira create <summary> to open a quick form (project, type, summary, description) and post the new issue’s card.

Transition and assign need the write permission, so if you connected before these shipped you may be prompted to reconnect.

Search pull requests with /github <terms> or paste a /pull/123 link to get a PR card with state (open/merged/closed/draft), additions/deletions, reviewers, and CI checks. From the card you can:

• Approve the pull request.
• Merge it (with a confirm step) — the card updates in place to “merged”.

With the optional GitHub webhook configured, PR cards update live — when someone merges, closes, or CI finishes, everyone watching the card sees the new state without refreshing.

Every action runs under your own connected account, so the source service is always the authority on what you can see and do. We store only what’s needed to keep the connection working, and we honour account-deletion and update signals from Atlassian on a regular reporting cycle. Disconnecting an app removes its access immediately.