Connectors
Connect external services to Alumia tools.
Connectors give agents controlled access to external systems. Alumia supports 2028 connector slugs across productivity, communication, developer, billing, commerce, cloud, research, knowledge, and data services.
How connectors work
Most connectors use OAuth or API keys. OAuth opens the provider in a normal new tab (never a sized popup). Use ?selectAccount=1 on /api/v1/connections/oauth/start when the UI must show the provider account picker. Once connected, the platform stores credentials encrypted, exposes only supported operations, and records usage through normal tool-call and audit paths. The originating page refreshes via BroadcastChannel / localStorage and blocked chat sessions resume automatically.
Some connectors can also receive provider events. These use Alumia's inbound connector event runtime: each provider gets a verified webhook endpoint, inbound payloads are normalized into connector events, duplicate deliveries are ignored, and routed agent work is queued durably so the app can continue processing even if the user refreshes, switches sessions, or closes the UI. Telegram is the first full provider implementation through its setup-webhook command; Slack, Discord, WhatsApp, Twilio, Gmail push, GitHub, Linear, and Stripe share the same adapter interface for verified inbound events.
Production webhook setup requires CONNECTOR_WEBHOOK_BASE_URL or an equivalent public HTTPS app URL (NEXT_PUBLIC_APP_URL or APP_URL). Use /admin/connector-events to inspect endpoint health, event delivery, and queued connector jobs. Run live Telegram smoke only when a real bot token and connection have been intentionally provisioned for that test.
Common connectors
Popular connectors include Gmail, Google Calendar, Google Drive, Docs, Sheets, Slides, YouTube, Slack, Discord, X, Notion, GitHub, Linear, Asana, Trello, QuickBooks, Stripe, Shopify, Mercury, Vercel, Cloudflare, Supabase, Sentry, GoDaddy, Telegram, Wikipedia, arXiv, PubMed, Open Library, and Open-Meteo.
Use connector scopes narrowly. If an agent only needs to read a calendar, do not grant write access.