> ## 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 **more than 150 connectors** covering close to **3,000 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. The **Integrations** cube only lists the connectors your company can actually connect today. To have an agent work directly in your repositories (write code, open pull requests), create a coding agent on the [opencode engine](/concepts/engines) rather than granting GitHub actions.

### Authentication

| Method | Used by |
| - | - |
| **API key** | The majority of connectors — you paste a key or token generated on the provider's side. |
| **OAuth** | Connectors such as Gmail, Google Drive, Google Calendar, Outlook, Microsoft Teams, Salesforce, Zoom, and Dropbox — you authorize Atako's app directly with the provider. Harvest, Pipedrive, and SurveyMonkey also accept 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 on the **Context** storey, in the **Integrations** cube. Go down to the Context storey and click the cube to open it (see [The Floor](/guides/the-floor#context)). Only a company admin can connect, change, or disconnect a tool; everyone else sees the dialog with the message *Only an administrator can change or remove this connection.*

<Steps>
  <Step title="Pick a connector">
    Search by tool or use case, or filter by category. Connected tools are listed first, under **Connected**; click **Connect** on the tool you want.
  </Step>

  <Step title="Review before you connect">
    The dialog shows a description of the tool, a **How to get your key** panel (**How the connection works** for OAuth) linking to the provider's own documentation, and — importantly — the tool's **Endpoints**: 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 and click **Connect**, or click **Continue with** the provider's name to go through its OAuth screen.
  </Step>

  <Step title="Connection goes active">
    The tool now shows as **Connected**, 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? **Ask for an integration**, at the top of the cube, sends a request to the Atako team.
</Tip>

### The native Projects integration

**Projects** is built in rather than connected: it is available company-wide, shows as **Automatic**, and carries no **Connect** or **Disconnect** button. Every agent can use it by default — see [Permissions](/integrations/permissions#the-default-projects-grant).

## Connections are shared, agents are not

A connection created within a company is company-wide: once an admin 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. Grants are set agent by agent, from **Agent settings** — see [Permissions](/integrations/permissions).

Click **Manage** on a connected tool to open its connection:

| Item | Meaning |
| - | - |
| **Connected on** | When the connection was created. |
| **Last call on** | When an agent most recently called an action through it (**Never called** otherwise). |
| **Endpoints** | The actions the tool offers, read-only here — this window grants nothing. |
| **Change the key** | Replaces the API key in place. The connection keeps its identity, so agents keep the rights they already have. For an OAuth tool, **Run the authorization again** instead. |
| **Disconnect** | Revokes the connection and immediately and permanently deletes the underlying credential — see [Security](/integrations/security#revocation). |

A connection is **active**, **revoked**, or in **error** — typically an OAuth token that could not be refreshed. Only active connections show as **Connected** in the cube and can be granted to agents.

## 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="Agents" icon="robot" href="/concepts/agents">
    What an agent is and how integrations fit into its configuration.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.