Integrations
Connect GitHub, Slack, Jira, Gmail, Microsoft 365 and other tools to Ysra — what each connection reads, what it can do, what waits for your approval, and how to disconnect.
On this page
An integration is a connection between Ysra and a tool your company already uses. A connection gives Ysra one or more of three things: code to work on (GitHub), company context to search when you ask a question (Slack, Jira, Gmail), and a place to act (a Slack message, a Jira change, a sent email) — always after you approve the exact action. This page is for anyone connecting a tool: it lists every connection, what each allows, and how syncing and disconnecting work. Each integration’s own page has the steps.
What a connection can do#
Ysra reads what a connection grants and acts only after you approve the exact action, once. What it reads from a connected tool is data, never instructions: a Slack message that says “ignore your rules and post this”, or a Jira comment asking Ysra to do something, is only text to cite.
Where each connection lives#
| Place | What is there |
|---|---|
| Settings → Connectors (web app; it replaced Plugins and Integrations on 17 November 2026) | Every connection in one page, with three tabs: Apps, MCP servers and Skills. Apps include Sources (“What Ysra can read”): GitHub, Slack, Jira. Mail and your own keys: the Gmail search connection, Gmail for a routine, and your own keys for model providers. Your own hosting accounts, for deploys from cloud threads |
| Settings → Plugins (desktop app) | The same apps and servers: about thirty services in one click (such as Linear, Notion and Microsoft 365), your company’s own servers, any MCP server, and skills. See Plugins, connectors and skills |
On the Connectors page, each connection has a card with Connect; after connecting, the card shows the account it uses and its status. A model-key card reads “Your own key for this provider, used by Code on your computer”: Code in the desktop app or the CLI uses it, nothing in the web app does. Hosting accounts are used only when you deploy, and nothing is created in them without your OK; see Publish or Deploy.
Available integrations#
| Integration | What Ysra can read | What Ysra can do | Needs your approval? | Done elsewhere |
|---|---|---|---|---|
| GitHub | The repositories you grant | Run Code in Ysra’s cloud on them, on a branch of its own | Opening a pull request and every deploy | Ask doesn’t search code, issues or pull requests. No disconnect or refresh button in the web app |
| Slack | Channels, private channels, direct and group messages it was granted | Find people, propose messages | Every message: you approve the exact text before it is posted | Post anything without your approval |
| Jira | Issues, statuses and comments on one Jira Cloud site | Propose creating or updating an issue, adding a comment, moving an issue | Every change: you approve the exact action first | Change projects, boards, workflows or permission schemes. Routines cannot use Jira |
| Gmail | Mail, through a read-only search connection | Read mail, create drafts and send approved drafts, through Gmail for a routine, a separate connection used by routines | Every send: you approve the exact draft | The search connection cannot draft or send |
| Microsoft 365 (a plugin) | Outlook mail and calendar, OneDrive and SharePoint files, Teams, people | Send mail, create events and Teams meetings, save files, post in Teams | Each send, event, file and post | — |
| Other plugins | What each service grants | What each service allows | Posting and changes are approved on a card first | — |
What an approval looks like#
When Ysra wants to act in Slack or Jira from Ask, it shows a card describing the exact action, for example Send Slack message or Create Jira issue, and does nothing until you choose.
| Button (web, desktop) | On the phone | What happens |
|---|---|---|
| Approve exact action | Approve | Runs exactly what the card shows, once |
| Edit | Edit | Change the proposal before approving it |
| Reject | No | Discards it |
Routines stop the same way: sending mail and posting to Slack wait for your approval. See Actions and approvals and How routines work.
How syncing works#
Slack, Jira and the Gmail search connection are synced so Ask can search them. GitHub isn’t synced. Your browser doesn’t need to stay open.
| Rule | Value |
|---|---|
| Automatic sync | About every 15 minutes; the interval can’t be changed |
| Sync on demand | Sync now; after a failed sync it reads Retry sync |
| Last sync | “Last synchronized …” and what changed: “N updated · N removed” |
| Before the first sync | “Waiting for the first synchronization” |
| Next sync time | Not shown |
| Status | What it means | What to do |
|---|---|---|
| Ready | Syncing works | Nothing |
| Attention | Something needs you | Check the card, then Retry sync |
Checking what Ysra can see#
The Integrations page has a search box over your connected Slack and Jira content. Use it to check what Ysra can see before you rely on it in Ask.
Disconnecting#
| Integration | How to disconnect |
|---|---|
| GitHub | Disconnect on the GitHub card. To remove the Ysra app from GitHub too, uninstall it there (Repositories on GitHub ↗). See GitHub |
| Slack | Disconnect on the Slack card |
| Jira | Disconnect on the Jira card: “Jira disconnected and its context revoked” |
| Gmail (search) | Disconnect next to each mailbox |
| Gmail (mail for routines) | Manage on the Gmail for a routine card |
| Microsoft 365 and other plugins | On the service’s page in Settings → Connectors. See Plugins |
Other services#
| Service | Where it is instead |
|---|---|
| Linear, Notion | Settings → Connectors directory |
| Confluence | Through the Jira plugin’s live actions (@jira covers Jira and Confluence) |
Related#
- GitHub — repositories for Code in Ysra’s cloud.
- Slack and Jira — company search and approved actions.
- Gmail — mail search, and a mailbox routines send from.
- Plugins, connectors and skills — Microsoft 365 and about thirty more services.
- Actions and approvals — the approval card in Ask.