Connectors

Connectors expose configured apps and APIs as workflow tools. A connector appears once in the picker, then each workflow step controls the operation, account, permissions, and inputs it needs.

Current Connector Areas

• Google: Gmail, Drive, Calendar, Chat, Meet, Docs, Sheets, Slides, Analytics, and YouTube.
• Developer and work systems: GitHub, GitLab, Jira, Linear, Slack, Discord, Microsoft Teams, Microsoft Excel, Notion, Calendly, and Zoom.
• Commerce, finance, and growth systems: Stripe, PayPal, Shopify, Plaid, Mailchimp, Bitly, LinkedIn, Facebook, Instagram, WhatsApp, Twitter / X, Spotify, and Strava.
• Dedicated app configuration: Apple Developer and Plaid.
• Local utility surfaces: HTTP, webhook, storage, parser, artifact, notification, source, report, and coordinator tools.

Credential Storage

Connector credentials, OAuth accounts, provider keys, and webhook secrets are stored locally through settings screens and the local secret registry.

For setup steps, see Set up accounts and connectors.

Policy

Connector actions should remain permissioned, auditable, and scoped to the workflow step that requested them.

OAuth catalog entries generally expose <connector>.api-read and <connector>.api-request tools. Treat generic request tools as advanced escape hatches. Prefer typed operations for repeated side effects, and require an approval preview for unsafe generic methods before Aegis reads tokens or contacts the provider.

For the current catalog and tool family map, see Capability Inventory.