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 more than 150 connectors covering close to 3,000 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.
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 on the Context storey, in the Integrations cube. Go down to the Context storey and click the cube to open it (see The Floor). 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.1
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.
2
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.
3
Authenticate
Paste the API key and click Connect, or click Continue with the provider’s name to go through its OAuth screen.
4
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.
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.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. Click Manage on a connected tool to open its connection:
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
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.
Agents
What an agent is and how integrations fit into its configuration.