# Integrations

> Connect the tools you already use. Learn how integrations work, which ones are available now, and which are Coming soon.

Integrations connect your assistants to the tools you already use: your code host, your mail, your calendar, your issue tracker. An assistant that can see the right tool does better work, and an assistant that has to ask you for every detail does not.

Today three integrations are available, all for source control: **GitHub**, **GitLab**, and **Bitbucket**. Every other integration on this page is **Coming soon**.

## How integrations work

1. **Create an access token in the tool.** Give it only the permissions the assistant needs. Each page lists them in plain words.
2. **Connect it.** Open [Integrations](https://stellarfirm.ai/app/integrations), pick the tool, paste the token, and press **Connect**.
3. **Ask for the work.** In chat, tell the assistant what you want. It uses the tool without you pasting anything again.

Your token stays with your StellarFirm workspace. It is never shown back to you after you connect: the page shows only that the tool is connected. You never paste a token into a chat message.

## Reads on its own, or waits for your Approve

Every ability falls into one of two groups, and each integration page tells you which.

| Kind | What it means | Examples |
| --- | --- | --- |
| Reads on its own | The assistant can do it without asking, because nothing leaves your control | List issues, read a pull request, list upcoming events, create a draft that is not sent |
| Waits for your Approve | The assistant stops and asks before it does anything that sends, deploys, charges, publishes, or creates | Push a branch, open a pull request, send mail, create an event |

> [!IMPORTANT]
> Whether a step waits for you depends on your [house rules](/docs/ceo/house-rules): the rules in your company brief plus what you allow without asking in Auto-approve in Settings. The tables on each page show the default. See [approvals](/docs/ceo/approvals).

## Every integration

| Integration | Category | Status |
| --- | --- | --- |
| [GitHub](/docs/integrations/github) | Source control | Available |
| [GitLab](/docs/integrations/gitlab) | Source control | Available |
| [Bitbucket](/docs/integrations/bitbucket) | Source control | Available |
| [Slack](/docs/integrations/slack) | Chat | Coming soon |
| [Telegram](/docs/integrations/telegram) | Chat | Coming soon |
| [Discord](/docs/integrations/discord) | Chat | Coming soon |
| [Gmail](/docs/integrations/gmail) | Mail and calendar | Coming soon |
| [Outlook](/docs/integrations/outlook) | Mail and calendar | Coming soon |
| [Google Calendar](/docs/integrations/google-calendar) | Mail and calendar | Coming soon |
| [Google Drive](/docs/integrations/google-drive) | Files | Coming soon |
| [Linear](/docs/integrations/linear) | Issue tracking | Coming soon |
| [Lovable](/docs/integrations/lovable) | App builders | Coming soon |
| [Sentry](/docs/integrations/sentry) | Errors and support | Coming soon |
| [PostHog](/docs/integrations/posthog) | Errors and support | Coming soon |
| [Resend](/docs/integrations/resend) | Email sending | Coming soon |
| [SendGrid](/docs/integrations/sendgrid) | Email sending | Coming soon |
| [Stripe](/docs/integrations/stripe) | Payments | Coming soon |
| [Notion](/docs/integrations/notion) | Docs and wikis | Coming soon |
| [Jira and Confluence](/docs/integrations/jira-and-confluence) | Issue tracking | Coming soon |
| [Asana](/docs/integrations/asana) | Issue tracking | Coming soon |
| [Datadog](/docs/integrations/datadog) | Monitoring | Coming soon |
| [PagerDuty](/docs/integrations/pagerduty) | Monitoring | Coming soon |
| [Box](/docs/integrations/box) | Files | Coming soon |
| [Dropbox](/docs/integrations/dropbox) | Files | Coming soon |
| [Egnyte](/docs/integrations/egnyte) | Files | Coming soon |
| [Docusign](/docs/integrations/docusign) | Business apps | Coming soon |
| [Salesforce](/docs/integrations/salesforce) | Business apps | Coming soon |
| [Snowflake](/docs/integrations/snowflake) | Business apps | Coming soon |
| [Cursor and VS Code](/docs/integrations/code-editors) | Coding | Coming soon |

## Which assistants use which tool

Every connected tool is shared with your team, so the CEO assistant knows what is connected when it briefs an assistant. Each assistant then uses the tools that fit its job. Today the Coder is the assistant that is available, so source control is where integrations matter first. The other assistants arrive with the tools that suit them, such as mail for the Accountant and Legal.

An assistant never pretends a tool is connected. If you have not connected it, the assistant leaves it out and tells you.

## Preflight checklist

Before you connect a tool:

- You can create an access token in that tool.
- You know the smallest set of repositories, folders, or projects the assistant should see.
- You have decided what your house rules allow without asking.

## Staying in control

- **Connect with the least access that works.** You can always make a token wider later.
- **Disconnect at any time.** Revoke the token in the tool itself and the assistant loses access straight away.
- **Check what happened.** [Jobs](https://stellarfirm.ai/app/jobs) and [Approvals](https://stellarfirm.ai/app/approvals) keep a record of what each assistant did with each tool. See the [activity log](/docs/workspaces/activity-log).

> [!SOON]
> Every integration marked Coming soon is not open yet. Its page describes how it will work, and its setup steps are titled "Setup (when it opens)".

## Prompt

```prompt title="Check what is connected"
CEO, which of my integrations are connected, and which assistant would use each one? Tell me what you would not be able to do without the ones that are missing.
```

---

Source: https://stellarfirm.ai/docs/integrations