Integrations and provider accounts
Integrations is one setup area with two connection types. OAuth apps delegate access through the provider. Provider accounts store an encrypted API credential for native Agent Team actions.
OAuth apps
Use OAuth for GitHub, Slack, Jira, Linear, Notion, Figma, GitLab, Bitbucket, and Vercel when available. Codelit receives scoped tokens and shows the connected identity so the user knows which account a team will use.
Provider accounts
Use provider accounts for services such as support, CRM, communication, data, and infrastructure APIs that need an API token plus provider-specific settings. Credentials are encrypted in the hosted vault and never rendered back to the browser.
Native provider catalog
Agent Team provider accounts currently cover Google Workspace, Microsoft 365, Zendesk, Intercom, Stripe, Shopify, HubSpot, Salesforce, Sentry, PostHog, Datadog, PagerDuty, and Supabase. Each pack exposes a small typed read and write surface rather than unrestricted API access.
- Work: Google Workspace and Microsoft 365.
- Support: Zendesk, Intercom, Stripe, and Shopify.
- Revenue: HubSpot and Salesforce.
- Engineering and data: Sentry, PostHog, Datadog, PagerDuty, and Supabase.
Attach capabilities to a card
Connecting an app makes it available; adding its tool to an Agent Team card gives that responsibility permission to use it. The run validator blocks design-only tools and missing credentials before Live run.
- Prefer a native action for reliable reads and writes.
- Use custom actions for an API Codelit does not yet model.
- Use Browser Operator when no suitable API exists.