Connectors
External services that agents can call as scoped tools.
A connector is a registered integration with an external service. When an org connects a service, the platform stores credentials encrypted and exposes a fixed set of operations as agent-callable tools.
Alumia ships 541 connector slugs across category modules in packages/web/lib/connectors/registry/. Each slug declares its auth type and the operations agents may call.
Auth types
| Type | Used by | Setup |
|---|---|---|
oauth | Google services, Slack, Discord, GitHub, Linear, Stripe, X, etc. | Click connect, complete provider consent in a new tab. |
api_key | Twilio, Sentry, Vercel, Cloudflare, Supabase, Shopify, Mercury, etc. | Paste key on the org Connectors page. |
none | Wikipedia, arXiv, PubMed, Open Library, Open-Meteo. | No credentials required. |
See OAuth flow and API keys.
Where to set up
Connectors are managed at /[orgSlug]/connectors. Each connection belongs to one org. Members with permission can add, rotate, or remove a connection.
Attaching to an agent
An agent only sees a connector's tools if you grant it explicitly. Edit the agent at /[orgSlug]/agents, choose which connectors it may call, and save. New tools appear on the next session message.
Scoping
Use the narrowest scope that lets the agent do its job.
- Read-only when write isn't needed.
- One workspace's connection rather than an org-wide one when the work is project-scoped.
- Separate connections per environment when the upstream supports it (test vs live).
Categories
- Google Workspace — Gmail, Calendar, Drive, Docs, Sheets, Slides, YouTube.
- Messaging — Slack, Discord, Telegram, WhatsApp, Twilio, X.
- Developer — GitHub, Linear, Asana, Trello, Jira, Sentry, Vercel, Cloudflare, Supabase.
- Commerce & finance — Stripe, Shopify, QuickBooks, HubSpot, Salesforce, Mercury.
- Research & data — web search, arXiv, Wikipedia, PubMed, Open Library, Open-Meteo.
Advanced
- Build your own — registering a custom connector.