Ghosty
Connectors

Connectors

External accounts the agent accesses on your behalf — Google, Canva, Spotify, Odoo, GitHub — and how they are connected.

Updated 2026-09-16

A connector is an external account the agent can use on your behalf. It is connected once per person and used by all your agents.

How it works

  • They belong to the account, not to the agent. The key is stored encrypted under (your user, provider). An agent has no connectors of its own; it has access to yours when it acts for you.
  • It acts as whoever invokes it. In Teams, if @handle sends an email from a channel, it sends it with the account of the person who mentioned it, not with a shared account. On a public channel (WhatsApp) personal connectors are not available.
  • Disconnecting revokes. Removing a connector deletes the key and revokes the grant at the provider.

Where they are connected

  • Studio: Settings → Connectors. This is where the Google, Canva and Spotify OAuth connectors live, and credential-based ones like Odoo.
  • Teams: the workspace's Settings → Integrations, for what the agent uses inside the workspace (GitHub, Calendly, Deník…).
  • Mobile app: Settings → Integrations with the same list, through the .

Catalog

ConnectorTypeWhat the agent can do
GoogleOAuth2Gmail, Calendar and Drive: read, search, create events, send.
CanvaOAuth2Designs and exports.
SpotifyOAuth2Playback control and playlists.
OdooCredentials (URL, user, API key)Read and create ERP records.
GitHubOAuth2 (Teams)Issues, PRs and code from the workspace's repos.
CalendlyOAuth2 (Teams)Scheduling and availability.
EasyBitsOAuth2The sister platform's services (files, sandboxes).
Deník, Kommo, MailmaskComing soon.

Odoo and other credential-based connectors

Non-OAuth connectors are set up with their credentials (instance URL, user, key). The URL goes through a network guard: only public hosts, no private IPs and no localhost, so a connector can't be used to reach your internal network from the agent's machine.

API

For your own clients (the mobile app uses these):

RouteWhat it does
GET /api/v2/me/connectorsCatalog with conectado: true/false ("connected") per connector.
POST /api/v2/me/connectors/:id/startReturns the authorization url to open in the browser.
DELETE /api/v2/me/connectors/:idDisconnects and revokes.

They require an OAuth2 bearer; see .