Teamwork
OAuth2 or API key
What sets your agents apart is how deeply they connect to your tools and how tightly they're governed — not which model is underneath. Connect with scoped, encrypted credentials, and every connector follows the same rule below.
Read tools run inline. Listing tasks, reading a thread or pulling a balance has no side effect, so an agent uses them freely as it reasons.
Write tools are approval-gated. Anything that changes the outside world pauses for a human decision — with higher-risk actions flagged accordingly.
OAuth2 or API key
OAuth2 (Atlassian)
OAuth2 (Google)
OAuth2 (Microsoft)
OAuth2 (Slack)
API key
OAuth2 (Xero)
OAuth2 (HubSpot)
OAuth2 (Google)
OAuth2 or PAT
Connect over OAuth or with an API key, depending on the provider. Credentials are held in an encrypted vault and scoped per organisation — never shared between tenants, and never more access than the agent needs. Connecting one Google service (say, Gmail) doesn't grant another (like Drive).
A doc-verified shortlist of providers we're adding next. Want one of these — or something not listed? Tell us; demand shapes the order.
Roadmap items are planned, not yet available.
Tell us what your team runs on. New connectors reuse the same governed framework, so adding one is a known quantity — not a science project.