Connecting via OAuth

What OAuth connections enable

Some services — like Google, GitHub, and Slack — require OAuth for user-level access. Chase Agents supports OAuth connections that handle the full authorization flow and automatically refresh access tokens, so your automations keep working without manual re-authentication.

The authorization flow

When you add an OAuth connection, Chase Agents uses a PKCE (Proof Key for Code Exchange) flow. You are redirected to the external service's authorization page to grant access. After you authorize, Chase Agents stores the access token and refresh token securely in the credential vault. The access token is automatically refreshed when it expires — you never need to manage token lifecycle in your automation logic.

Using OAuth connections in steps

OAuth connections work identically to API key connections in automation steps. The access token is stored under a variable name you assign during setup. You reference that variable in step headers just like any other credential. The system handles token refresh automatically before substituting the real value at runtime.

Re-authorizing a connection

If an OAuth token is revoked by the user or the external service, automations using it will start returning 401 Unauthorized errors. To fix this, go to My Connections, find the connection, and click to re-authorize. You will be taken through the OAuth flow again and a fresh token will be stored.

Common OAuth services

Chase Agents works with any service that supports standard OAuth 2.0. Common examples include Google APIs (Gmail, Calendar, Drive), GitHub, Slack, and Microsoft services. The Connections Marketplace includes pre-built connectors for many popular OAuth services, which simplify the setup process.