Bring Your Own OAuth App

How to provide your own OAuth app (Client ID and Secret) — required for every sign-in connection your agent uses.

Written By Philippe

Last updated 2 days ago

Bring Your Own OAuth App

Some of your agent's connections use OAuth — the "Sign in with…" flow (Slack, Google, GitHub, and similar). Those flows always run through an OAuth app registered with the provider. The publish form requires you to supply your own.

Do I Need To?

Yes — for every OAuth connection your agent uses. There is no shared platform app: each sign-in connection runs through the OAuth app you register with the provider and enter in the publish form. Publishing fails until every OAuth connection has a Client ID and Client Secret.

If you later see a message that an OAuth app "is not registered for this service", re-publish the agent with your OAuth app credentials filled in.

What You Provide

Two values from the provider's developer console:

  • Client ID — public identifier of your OAuth app.
  • Client Secret — treated like a password; stored encrypted in the Secure Vault, never shown to buyers.

How to Register an OAuth App

The steps are provider-specific, but the shape is always:

  1. Open the provider's developer console (e.g. Slack → Your Apps, Google Cloud → Credentials, GitHub → Developer settings → OAuth Apps).
  2. Create a new OAuth app.
  3. Set the redirect URL shown in the publish form for that provider.
  4. Copy the Client ID and Client Secret into the form.

Grant only the scopes your agent's nodes actually need — buyers see the consent screen and over-broad scopes hurt trust.

What Buyers See

When a buyer activates your agent, the OAuth consent screen shows your app's name. They sign in with their own account; you never see their tokens.