Connectors
A connector is a stored, authorized link to an external account — a Gmail inbox, a QuickBooks company, a Notion workspace. Connect an account once, and every connector-backed tool can act on it: the tool config just points at the connector, and Autessa handles the credentials (including refreshing OAuth tokens automatically before each call).
What it's for
Agents become genuinely useful when they can touch your real systems. Connectors separate authorization from automation: an admin links the account, and tool builders reference it without ever seeing tokens or keys. Each connector unlocks a whole family of tool types — a single Gmail connector powers read, send, label, and search tools; a QuickBooks connector powers invoices, payments, reports, and more. See the Tool Types reference for every family.
Navigating here
From the dashboard sidebar, open Connectors. The page is a searchable grid grouped by category — Google Services, Social Media, Content Marketing, File Storage, Ticketing Platforms, ERP Systems, CRM Systems, Accounting / Payments, Microsoft Services. Click a card to open that connector's own page, where its connected accounts are listed and managed.
Key concepts
The full catalog
| Connector | Category | Authentication |
|---|---|---|
| Gmail | Google Services | OAuth |
| Google Calendar | Google Services | OAuth |
| Google Analytics | Google Services | OAuth |
| Outlook | Microsoft Services | OAuth |
| Outlook Calendar | Microsoft Services | OAuth |
| Social Media | OAuth | |
| X (Twitter) | Social Media | OAuth |
| Social Media | OAuth | |
| Social Media | OAuth | |
| Social Media | OAuth | |
| Threads | Social Media | OAuth |
| Bluesky | Social Media | Handle + app password |
| YouTube | Social Media | OAuth |
| TikTok | Social Media | OAuth |
| Ghost | Content Marketing | API key |
| Mailchimp | Content Marketing | OAuth (access token only) |
| Beehiiv | Content Marketing | API key |
| Box | File Storage | OAuth |
| Notion | File Storage | OAuth |
| Zendesk | Ticketing Platforms | OAuth |
| Acumatica | ERP Systems | OAuth |
| HubSpot | CRM Systems | OAuth |
| Zoho CRM | CRM Systems | OAuth |
| QuickBooks | Accounting / Payments | OAuth |
| Autessa Payments | Accounting / Payments | Special — embedded onboarding |
| Meeting Bot | — | Special — provisioned by Meeting Recorder |
Two entries are special: Autessa Payments is a payments account onboarded through a secure verification flow rather than an OAuth redirect (agents can then invoice, charge, and refund your customers), and Meeting Bot is the bot identity created by the Meeting Recorder rather than something you connect from this page. The exact cards shown on your Connectors page can vary — a few connectors are enabled per environment.
The connect flow
OAuth connectors follow the standard redirect dance: you name the connector, get sent to the provider's consent screen, approve the requested scopes, and land back on the connector's page with the new account listed. API-key connectors (Ghost, Beehiiv) skip the redirect — you paste the key. Bluesky takes your handle plus an app password and authenticates at call time.
You can connect multiple accounts per connector type — e.g. a support inbox and a billing inbox as two Gmail connectors — and each tool picks which one it uses.
Reconnection
If the external provider revokes or expires the grant (password change, admin policy, long inactivity), tools using the connector start failing with auth errors. Reconnect on the connector's card re-runs the OAuth flow for the same connector — its identity and every tool referencing it stay intact. Prefer reconnecting over deleting and re-adding.
How connectors power tools
A connector-backed tool names its connector in its configuration; at execution time Autessa loads the credentials, refreshes tokens if needed, and makes the call. Connector pages also offer a bulk Create Tools action that generates a ready-made set of tools for that account in one step — the fastest way from "account connected" to "agent can use it."
Sharing
A connector is private to its creator by default. Share it with specific teammates or company-wide, with read/write/admin levels — sharing the connector is what lets others build and run tools against that account without ever holding its credentials. Ownership can be transferred. Deleting a connector also removes the tools that use it, so audit dependents first.
How to connect an account
- On the Connectors page, find the service (search or browse by category) and open its page.
- Click connect and name the connector — something that identifies the account, like
SupportInbox. - Complete the provider's flow (OAuth consent, API key, or credentials). You'll return to the connector page with a success confirmation.
- Optionally use Create Tools to generate the standard toolset for the account, or reference the connector from individual tools.
- Share the connector with your team if others should build against it.
How to fix a broken connector
- If connector-backed tools start failing with authorization errors, open the connector's page.
- Click Reconnect on the affected account and re-approve access at the provider.
- Re-run a failing tool with Execute Tool to confirm the fix — no tool configuration changes needed.
Sharing and access levels
Every connector starts private to its owner. Share it with specific teammates — each at their own access level — or company-wide at a single level for everyone. Sharing is what lets teammates' tools act through the connection without ever holding its credentials. What each level allows:
| Level | What it lets a teammate do |
|---|---|
| READ | Use the connection — their tools can act through it, and it appears in their connector list |
| WRITE | Edit the connection (rename it, activate or deactivate it) |
| PUBLISH | Nothing beyond READ — connectors have no publish step, and edits require WRITE |
| ADMIN | Share the connector |
Deleting a connector and transferring its ownership are both owner-only. The owner always has ADMIN implicitly. Deleting a connector removes the tools that use it and its auto-created tables — those tables can't be shared, transferred, or deleted directly; manage the connector instead.