What this workflow can do

  • Build authorization URL
  • Exchange authorization code
  • Refresh token
  • Verify access token

Before starting

  • Client ID
  • Client secret
  • Redirect URI
  • Scopes
  • PKCE challenge and verifier
  • Callback code and state

Result handling

  • Access token returns from exchange and can be verified in the result panel.
  • Refresh token may return from exchange or refresh.
  • Callback state is only used to validate the current handshake.
  • Anonymous OAuth Hub workflows do not store client secrets, authorization codes, access tokens, or refresh tokens.
  1. 01PrepareEnter provider credentials, scopes, callback details, and PKCE values if required.
  2. 02AuthorizeBuild the authorization URL and open provider consent.
  3. 03ExchangePaste the returned code and state, then exchange them for tokens.
  4. 04VerifyTest the access token against the provider verification endpoint.
  5. 05Next stepsCopy tokens or metadata, then store them safely outside anonymous mode.

Credentials

OAuth handshake

Provider callback returns code and state. Refresh uses refresh_token.

This provider requires both PKCE fields.

Troubleshooting

  • Authorization codes expire after 10 minutes and are single-use even when an exchange fails.
  • Access tokens last about one hour; rotating refresh tokens expire after 60 days of inactivity.