AGENTOS DOCS / EXTENDING

Connectors

Connectors give your agents direct, secure access to your accounts. Set a connector up once, then turn it on for each workspace that should use it.

Available connectors

ConnectorAuthenticationWhat the agent can do
GmailOAuth 2.0Search and read your inbox, send email
Google CalendarOAuth 2.0 or Service AccountList and create events across your calendars
Google Drive, Docs, Sheets, SlidesOAuth 2.0 or Service AccountSearch, read and create files; read and write sheet data
Google PlacesAPI keySearch places and look up business details
JiraOAuth 2.0Search and create issues
TrelloAPI key + tokenRead boards and cards; create, move, update and comment (optional read-only mode)
AWS S3 · SQS · BillingAccess key + secretObjects, queues, costs, forecasts and invoices
ZapierAPI keyRun Zapier AI Actions
IMAP · POP3 · SMTP · SendmailServer + credentialsRead and send email through any mail server
Microsoft SQL Server · MySQLServer + credentialsQuery databases (read-only unless you allow writes)

Most connectors support multiple named instances, so you can add one IMAP connector for your personal mailbox and another for work.

Setting up a connector

  1. Go to Global Settings → Connectors and add the service. Follow the on-screen setup steps for that service.
  2. Go to Workspace Settings → Connectors and turn on the connectors that workspace's agent may use.

A connector's tools appear to an agent only when the connector is connected globally and enabled for that workspace.

Google: OAuth 2.0 or Service Account

  • OAuth 2.0: create a Google Cloud OAuth app and authorize AgentOS against your account. This supports every Google connector, including Gmail.
  • Service Account: paste a Google Cloud service-account JSON key. There's no browser sign-in and no token expiry, which makes it ideal for scheduled jobs. Share the calendars or files you want with the service account's email address. This covers Calendar, Drive, Docs, Sheets and Slides, but not Gmail.

Security

  • Connector secrets and OAuth tokens are encrypted at rest (AES-256-GCM) on your machine. They are never shown to the model or written to logs.
  • Database connectors are read-only by default. Turn on Allow writes per connector only if you need it.
  • Data the agent reads from a connected account becomes part of the conversation sent to your model. See the Privacy Policy.

Example prompts

What's on my calendar for the rest of this week? Give me a day-by-day summary.
Search my inbox for anything about the Acme invoice and summarize it.
Show me all open Jira bugs assigned to me, prioritize them, and add them as todos.
Every Monday at 8am, check my calendar and open Jira tickets and write "weekly-plan.md".