Supabase Beta Authorize User Through Oauth

• scopestring
  Space-separated list of OAuth scopes for requested permissions on user resources (e.g., 'email profile', 'storage.objects.read').
• statestring
  Opaque value to maintain state between request and callback; returned unmodified to aid CSRF prevention.
• client_idstring

  Required
  Unique identifier for the OAuth client application, registered with Supabase. Must be a valid client_id from a registered OAuth application.
• redirect_uristring

  Required
  URI where Supabase redirects the user after authorization; must exactly match a registered URI for the client application.
• response_modestring
  Specifies how authorization response parameters are returned (e.g., 'query', 'fragment', 'form_post'). Default is determined by `response_type` if not specified.
• response_typestring

  Required
  Specifies the authorization flow type: 'code' for Authorization Code Grant; 'token' for Implicit Grant (access token); 'id_token token' for OIDC hybrid flows (ID and access tokens).
• code_challengestring
  PKCE code challenge to secure authorization code grants, typically a BASE64URL-encoded SHA256 hash of `code_verifier`.
• code_challenge_methodstring
  Method to derive `code_challenge` for PKCE: 'S256'/'sha256' for SHA256 hashing; 'plain' sends verifier as is (not for production if hashing possible). Required if `code_challenge` is provided.

• data

  Required
  Data from the action execution
• errorstring
  Error if any occurred during the execution of the action
• successfulboolean

  Required
  Whether or not the action execution was successful or not

No verified related use cases are linked yet.

No published Skills explicitly reference this Action yet.