Skip to main content
OAuth connectors are for services you sign in to. After you authorize, Corvic stores the resulting tokens and refreshes the access token before a run uses it, so agents keep working without handling tokens. There are two ways to connect with OAuth:
  • Personal accounts. Corvic has ready-made OAuth apps for Gmail, Google Calendar, Google Drive, Microsoft Graph, Slack, Notion, Box, Dropbox, Apollo, Supabase, GitHub, and LinkedIn. Pick one under Personal accounts, choose Connect, and sign in.
  • Custom OAuth. For any other OAuth 2.0 service, or to use your own OAuth app, choose Add Custom Connector → OAuth.

​
Custom OAuth connector

Register an OAuth app with the provider, then enter:
  • Client ID: the public identifier of the OAuth app.
  • Client secret: the private credential for that app. Keep it confidential.
  • Scopes: the permissions your agents need, such as reading contacts or creating issues. Request only what you need.
  • Authorization endpoint URL: where the user signs in and approves the scopes.
  • Token endpoint URL: where Corvic exchanges the authorization code for tokens, and later refreshes them.
  • Additional authorization parameters: provider-specific values for the sign-in request. To get a refresh token, some providers need access_type=offline, prompt=consent, or an offline_access scope.
Use the redirect URI Corvic shows in the form when you register the app with the provider.

​
Connection state

An OAuth connector shows one of three states: To see the scopes, endpoints, and token expiry of a connected OAuth connector, open its details from the card.

Personal accounts

Ready-made OAuth connectors.

MCP servers

MCP servers that sign in with OAuth.