---
title: Integrations
sidebar_title: Overview
description: What Ysra connects to today — GitHub, Slack, Jira and Gmail — what each connection is used for, how syncing works, and what is planned but not available yet.
---

Integrations give Ysra something to work **on** (your repositories), something
to **know** (your company context), and somewhere to **act** (with your
approval).

## Catalog

| Provider | Knowledge sync | Actions | Status |
|---|---|---|---|
| **GitHub** | — | Clone repositories, push branches, open pull requests, create repositories | Ready |
| **Slack** | Channels and threads | Proposed messages (with approval); run Developer sessions from Slack threads | Ready |
| **Jira** | Issues and comments | Proposed issue creation, updates, comments and transitions (with approval) | Ready |
| **Gmail** | Messages (read-only, owner-private) | Drafts and approved sends through [mail workers](../workers/types.md#mail) | Ready |
| **Google Drive** | — | — | Planned |
| **Confluence** | — | — | Planned |
| **Notion** | — | — | Planned |

Planned providers appear in the app as unavailable until they ship. A provider
listed in the catalog is not usable until it says *Ready*.

## Three ways a connection is used

| Use | What it means |
|---|---|
| **Sync** | Ysra keeps a searchable, permission-aware copy of the source for Knowledge and workers. |
| **Actions** | Ysra proposes a change in the provider; it runs only on your approval. |
| **Live search** | Querying the provider directly at question time. *Planned.* |

## How syncing works

- Syncs run in the background on a schedule you can set, from every minute up to
  once a week, and you can **Sync now** at any time. Your browser doesn't need to
  stay open.
- Each sync picks up where the last one stopped and records what changed:
  documents added, updated and deleted.
- Each connection shows its status, last successful sync, next sync and any
  error.
- Documents keep their access rules. Knowledge only searches what the person
  asking is allowed to see, in the sources selected for the conversation.

## Mentions

When you type `@` in the Ask composer, Ysra looks up real Slack people and
channels and Jira projects and issues. It inserts a readable name but keeps the
stable ID behind it, so proposed actions always target the right thing.

## Where to connect

**Workspace → Integrations** in the portal. Connecting providers happens on the
desktop; the phone uses the connections you've set up.

<div class="cards" markdown>

- [**GitHub**](github.md)

    Repositories for Developer, and delivery.

- [**Slack**](slack.md)

    Company context, proposed messages, and sessions from threads.

- [**Jira**](jira.md)

    Issues as context, and proposed issue changes.

- [**Gmail**](gmail.md)

    Mail as private context, and mail workers.

</div>