Set up accounts and connectors
Connectors let workflows use apps and APIs through configured accounts, OAuth grants, provider keys, and local secrets.
For model keys and routing, see Add model providers.
Before You Start
Decide what the workflow needs:
- which app or API;
- which account;
- read-only or write access;
- which workflow step will use it;
- what approval should be required for side effects.
Add A Connector Account
- Open settings.
- Go to connectors.
- Choose the connector.
- Add or select an OAuth app configuration if required.
- Start account authorization.
- Complete the provider authorization flow.
- Confirm the account appears as connected.
- Run a smoke check when the connector provides one.
Add Provider Keys And Secrets
- Open settings.
- Go to secrets or provider settings.
- Add the key or token.
- Give it a clear name.
- Choose kind and provider.
- Save it to the local secret registry.
- Check status.
Secret values are write-only. Aegis stores metadata and redacted previews separately from local secret material.
Use Connectors In Workflows
- Open the workflow designer.
- Add a connector tool node or configure an agent node with connector tools.
- Select the account.
- Choose the operation.
- Fill in required inputs.
- Confirm scopes and approval policy.
- Save and test with safe data.
Connector Write Operations
Prefer typed connector operations for side effects. For example, use gmail.create-draft for Gmail drafts instead of a raw Gmail API request, because typed tools can name their purpose, required scopes, policy class, and output receipt.
Generic OAuth request tools such as github.api-request, google-sheets.api-request, or stripe.api-request are advanced escape hatches. They are useful while building a typed connector operation, but they should not be the default workflow surface.
Unsafe generic OAuth methods (POST, PUT, PATCH, and DELETE) require an approvalPreview that matches the connector id, method, path, and account id before the request can run. The preview summary should describe the intended side effect in operator-readable language. If the preview does not match the actual request, Aegis blocks the call before reading OAuth tokens or contacting the provider.
When adding connector writes:
- start with read-only API access;
- add a typed write operation when the workflow repeats;
- keep generic request tools marked advanced;
- include the account, endpoint, scopes, payload summary, and expected receipt in the approval preview;
- avoid connector writes for purchases, trades, tax, device/network changes, or self-extension until that domain has a dedicated checklist and approval path.
Use Connectors In Dashboard Components
Dashboard components can use connector-backed data for views such as Planner, calendar context, source refreshes, and notifications. Configure the account first, then select it in the component or settings panel.
Current Catalog Coverage
The current OAuth catalog covers Google Workspace, GitHub, GitLab, Jira, Linear, Slack, Discord, Microsoft Teams, Microsoft Excel, Notion, Calendly, Zoom, Stripe, PayPal, Shopify, Mailchimp, Bitly, LinkedIn, Facebook, Instagram, WhatsApp, Twitter / X, Spotify, Strava, and YouTube. Apple Developer and Plaid have dedicated app configuration surfaces.
For the full connector and tool inventory, see Capability Inventory.