> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apollospace.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Composio — no-code integrations

> Connect Notion, Slack, Linear, Gmail, Calendar, and more via OAuth — no SDK to install, no webhook to configure.

Your Chief of Staff agent, Athena, is closing out the week: she updates a
Notion page, drops a summary in Slack, and moves two Linear tickets — all
in the tools your team already lives in. For her to reach any one of those,
someone would normally have to register an OAuth app, handle token refresh,
and keep the credentials safe — one integration at a time. Composio is how
Apollo Space skips that work, so your agents act inside the apps you already
run on and you never touch an SDK or a webhook.

## What it is

[Composio](https://composio.dev) is an **OAuth-as-a-service** layer
for SaaS apps. Instead of each app requiring you to implement the
integration from scratch (registering the app, handling token refresh,
keeping credentials secure), Composio exposes a broad catalog of apps
behind a single connection.

Apollo Space uses Composio to connect your agents to the tools your
company already runs on:

* **Athena** reads and writes to your Notion, Slack, Linear, HubSpot, and more
* **Marcus** can send email via Gmail (instead of Resend) when
  you want to keep the thread in your real inbox
* **Scout** can search internal tools (Confluence, Notion)
  in addition to the public web

## Available toolkits

The full list is at [composio.dev/apps](https://composio.dev/apps).
The most commonly used in the Apollo Space context:

<CardGroup cols={2}>
  <Card title="Productivity" icon="briefcase">
    Notion, Confluence, Google Docs, Google Calendar, Asana, Trello,
    Linear, Jira, ClickUp, Monday, Airtable
  </Card>

  <Card title="Communication" icon="comments">
    Slack, Gmail, Outlook, Discord, Telegram, Microsoft Teams
  </Card>

  <Card title="Sales & CRM" icon="users">
    HubSpot, Salesforce, Pipedrive, Zoho CRM, Calendly
  </Card>

  <Card title="Dev & Ops" icon="code">
    GitHub, GitLab, Bitbucket, Vercel, Supabase, Sentry
  </Card>

  <Card title="Social & Marketing" icon="bullhorn">
    LinkedIn, X (Twitter), Reddit, YouTube, Mailchimp, Canva
  </Card>

  <Card title="Commerce" icon="cart-shopping">
    Stripe, QuickBooks, Shopify (coming soon)
  </Card>
</CardGroup>

## How to authenticate

Authentication goes through the **app's own OAuth**, brokered by Composio:

<Steps>
  <Step title="Choose the toolkit in Apollo Space">
    In **Settings → Integrations**, select the app you want to connect
    (Notion, Slack, etc.).
  </Step>

  <Step title="Apollo Space redirects you to the app's OAuth flow">
    Log in to the app (Notion, Slack, Gmail...) and authorize Apollo Space to
    read/write per the requested scopes.
  </Step>

  <Step title="Composio stores the encrypted token">
    The access token is stored encrypted in Composio.
    Apollo Space never sees the raw token — it only asks Composio to
    execute actions on your behalf.
  </Step>

  <Step title="Agents get access to the toolkit">
    From that point on, your org's agents (Athena, Marcus, Scout,
    Digital Twins) can use that app's tools — subject to each agent's
    permissions.
  </Step>
</Steps>

## Scope: org vs. personal

Each Composio connection can be made in one of two scopes:

<CardGroup cols={2}>
  <Card title="Org-level" icon="building">
    The connection belongs to the organization as a whole. Any org agent
    can use it. **Example**: the company Slack account used by
    operational agents.
  </Card>

  <Card title="Personal" icon="user">
    The connection belongs to a specific user — only agents operating
    "on their behalf" (including that user's [Digital Twin](/en/agents/digital-twins))
    can use it. **Example**: a leader's personal Notion, accessible
    only to their Twin.
  </Card>
</CardGroup>

Apollo Space automatically selects the correct scope based on which agent
is making the call — no accidental mixing of personal and org accounts.

## Automatic cost cap per toolkit

Composio charges for some toolkits per call (most are free — OAuth
brokering only). To protect you from cost spikes:

* Apollo Space tracks spend **per (org, toolkit)** over time
* If the average cost per call exceeds a safe threshold, Apollo Space
  **automatically pauses** that org+toolkit combination
* You're notified and can review before reactivating

The goal: never arrive at a surprise bill because an agent looped on
an expensive tool.

## What lands in your Stars wallet

| What                                                                | How                             |
| ------------------------------------------------------------------- | ------------------------------- |
| **Toolkit execution**                                               | Stars (Apollo Space brokering)  |
| **Composio cost** (some toolkits have a direct charge)              | Your Composio account (BYO key) |
| **Underlying app charges** (e.g. SMS via Twilio, search via Tavily) | Your direct vendor account      |

## Known limitations

* **App OAuth quota** — if the app enforces a 1,000-call/day limit, Apollo Space
  is subject to it too. There's no way around it.
* **App schema changes** — when a SaaS app updates its API, Composio
  needs to catch up. Apollo Space inherits that lag (rare, but it happens).
* **No non-OAuth apps** — Composio only covers apps with public OAuth.
  Custom internal apps at your company require a custom tool.

## Next steps

<CardGroup cols={2}>
  <Card title="Athena — Composio's primary user" icon="user-tie" href="/en/agents/athena">
    The Chief of Staff runs day-to-day operations through Composio integrations.
  </Card>

  <Card title="Stars" icon="star" href="/en/billing/stars">
    How Composio usage feeds into billing.
  </Card>

  <Card title="Trust" icon="shield-check" href="/en/trust/security">
    How Apollo Space protects the credentials Composio stores.
  </Card>
</CardGroup>