Skip to main content
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.
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 for the full mechanism.

​
The catalog

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

Code & dev tools

GitHub, GitLab, Bitbucket, Linear, Jira — issues, pull requests, branches, releases.

Support & CRM

Zendesk, Intercom, Freshdesk, HubSpot, Pipedrive, Close, Attio — tickets, contacts, deals.

Productivity & docs

Google Drive, Google Calendar, Notion, Coda, Airtable, Dropbox — files, pages, records, events.

Comms & scheduling

Slack, Discord, Gmail, Outlook, Calendly, Twilio — messages, threads, emails, meetings.

Commerce & billing

Stripe, Shopify, Chargebee — payments, orders, subscriptions.

Ops & analytics

Datadog, PostHog, BambooHR, Ashby — monitoring, product analytics, HR data.
Every connector has its own reference page listing all of its actions, each tagged read or write — see GitHub for an example. Atako also has a special internal capability, Code, that lets an agent investigate and modify your repositories directly rather than through the GitHub API.

​
Authentication

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:
1

Pick a connector

Search or browse the connector list and select the tool you want to connect.
2

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.
3

Authenticate

Paste the API key, or continue through the provider’s OAuth screen for connectors that support it.
4

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.
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.

​
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 for how grants work. Your connections list, under Settings → Integrations, shows for each one: 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.

Permissions

How grants control exactly what each agent can do with a connection.

Security

How your credentials are encrypted, used, and audited — and why agents never see them.

Code capability

Let an agent investigate, implement, and reproduce issues directly in your repositories.

Agents

What an agent is and how integrations fit into its configuration.