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

# Integrations overview

> Connect your company's tools once, then let agents act on them — without ever handing over a credential.

An integration connects a third-party tool — GitHub, Slack, Stripe, Google Drive, and dozens more — to your company on Atako. Once connected, any agent you choose can be granted specific actions on it: read a ticket, post a message, update a deal, open a pull request. The agent acts on your tools; it never holds the keys to them.

<Note>
  Every credential you connect is encrypted the moment you submit it and is never shown again — not in the agent's context, not in logs, not even to you. See [Security](/integrations/security) for the full mechanism.
</Note>

## The catalog

Atako ships with roughly **45 connectors** covering close to **1,400 individual actions**, grouped into familiar categories:

<CardGroup cols={2}>
  <Card title="Code & dev tools" icon="code-branch">
    GitHub, GitLab, Bitbucket, Linear, Jira — issues, pull requests, branches, releases.
  </Card>

  <Card title="Support & CRM" icon="headset">
    Zendesk, Intercom, Freshdesk, HubSpot, Pipedrive, Close, Attio — tickets, contacts, deals.
  </Card>

  <Card title="Productivity & docs" icon="file-lines">
    Google Drive, Google Calendar, Notion, Coda, Airtable, Dropbox — files, pages, records, events.
  </Card>

  <Card title="Comms & scheduling" icon="messages">
    Slack, Discord, Gmail, Outlook, Calendly, Twilio — messages, threads, emails, meetings.
  </Card>

  <Card title="Commerce & billing" icon="credit-card">
    Stripe, Shopify, Chargebee — payments, orders, subscriptions.
  </Card>

  <Card title="Ops & analytics" icon="chart-line">
    Datadog, PostHog, BambooHR, Ashby — monitoring, product analytics, HR data.
  </Card>
</CardGroup>

Every connector has its own reference page listing all of its actions, each tagged **read** or **write** — see [GitHub](/integrations/github) for an example. Atako also has a special internal capability, [Code](/integrations/code), that lets an agent investigate and modify your repositories directly rather than through the GitHub API.

### Authentication

| Method        | Used by                                                                                                                                                                                               |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **API key**   | The majority of connectors — you paste a key or token generated on the provider's side.                                                                                                               |
| **OAuth 2.0** | Dropbox, Gmail, Google Calendar, Google Drive, Outlook, and Pipedrive — you authorize Atako's app directly with the provider. Pipedrive also accepts a personal API token as an alternative to OAuth. |

Some connectors need a small extra setting to know where to call — a Zendesk, Jira, Freshdesk, BambooHR or Chargebee **subdomain**, a Datadog **site** or PostHog **region**, a Mailchimp **datacenter**, or a Shopify **store**. The connect dialog asks for these alongside the credential.

## Connecting a tool

Connections live under **Settings → Integrations**, and are set up once per tool:

<Steps>
  <Step title="Pick a connector">
    Search or browse the connector list and select the tool you want to connect.
  </Step>

  <Step title="Review before you connect">
    The dialog shows a description of the tool, a "how to get your key" panel linking to the provider's own documentation, and — importantly — the **complete list of actions** the connector exposes, each badged read or write. You see exactly what an agent could eventually do with this connection before any credential leaves your hands.
  </Step>

  <Step title="Authenticate">
    Paste the API key, or continue through the provider's OAuth screen for connectors that support it.
  </Step>

  <Step title="Connection goes active">
    The connection appears in your list as **active**, ready to be granted to agents. Connecting it does not, by itself, give any agent access — see [Permissions](/integrations/permissions).
  </Step>
</Steps>

<Tip>
  Don't see the tool you need? **Request an integration** is always available at the bottom of the connector list. The Atako team reviews every request.
</Tip>

## Connections are shared, agents are not

A connection created within a company is company-wide: once someone connects your team's Zendesk account, every agent that's granted access to it uses the same underlying credential — nobody re-enters it, and nobody needs their own separate account. (A connection created by a user without a company stays strictly personal.) What differs per agent is not the connection, but the **grant**: which actions that agent is allowed to call on it. See [Permissions](/integrations/permissions) for how grants work.

Your connections list, under Settings → Integrations, shows for each one:

| Field         | Meaning                                                                                    |
| ------------- | ------------------------------------------------------------------------------------------ |
| **Provider**  | Which tool it connects to.                                                                 |
| **Name**      | A display name you choose for the connection.                                              |
| **Status**    | `active`, `revoked`, or `error` (typically an expired OAuth token that failed to refresh). |
| **Last used** | When an agent most recently called an action through it.                                   |

Each connection offers **Manage access**, to review or change which agents can use it, and **Revoke**, which immediately and permanently deletes the underlying credential — see [Security](/integrations/security#revocation).

## Related

<CardGroup cols={2}>
  <Card title="Permissions" icon="shield-check" href="/integrations/permissions">
    How grants control exactly what each agent can do with a connection.
  </Card>

  <Card title="Security" icon="lock" href="/integrations/security">
    How your credentials are encrypted, used, and audited — and why agents never see them.
  </Card>

  <Card title="Code capability" icon="code" href="/integrations/code">
    Let an agent investigate, implement, and reproduce issues directly in your repositories.
  </Card>

  <Card title="Agents" icon="robot" href="/concepts/agents">
    What an agent is and how integrations fit into its configuration.
  </Card>
</CardGroup>