Vellum Oauth Integrations

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

assistant/CLAUDE.md

assistant/src/approvals/CLAUDE.md

assistant/src/notifications/CLAUDE.md

assistant/src/runtime/CLAUDE.md

gateway/CLAUDE.md

- **Token endpoint auth method:** secret via POST body

- `repo` - full access to repositories

Do NOT collect the client secret conversationally. Never solicit the secret in chat and never store a chat-pasted value with `assistant credentials set`. Always collect it through the secure `assistan

Follow the `vellum-oauth-integrations` workflow to collect credentials, register the OAuth app, connect, and verify.

Follow the `vellum-oauth-integrations` workflow to collect credentials, register the OAuth app, connect, and verify.

Follow the `vellum-oauth-integrations` workflow to collect credentials, register the OAuth app, connect, and verify.

Follow the `vellum-oauth-integrations` workflow to collect credentials, register the OAuth app, connect, and verify.

Audit 0.4.1 · source sha 19bc86343b63 · 14 Oct 2026Report an issue or request a re-scan

• Publishervellum-ai GitHub organizationOwner of the repository this skill is read from
• Source foldervellum-ai/vellum-assistant/skills/vellum-oauth-integrationsThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict19bc86343b63A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Act on behalf of your user in any third-party software that supports OAuth 2.0

---
name: vellum-oauth-integrations
description: Act on behalf of your user in any third-party software that supports OAuth 2.0
compatibility: "Designed for Vellum personal assistants"
metadata:
  emoji: "🔌"
  vellum:
    category: "integrations"
    display-name: "Vellum OAuth Integrations"
---

## Using OAuth Integrations

Integrating with a third-party software via OAuth is typically used to perform actions on behalf of the user. It involves having the user log in using their own credentials, specifying the scopes that they want to provide, and then afterwards, API requests can be made on their behalf.

**Important:** Avoid reaching for an OAuth integration if your intent is to act as yourself rather than as your user.

## The Assistant OAuth CLI

You are provided with the `assistant oauth` CLI for performing all necessary oauth-related actions.

**Important:** When in doubt how a command works or how to do something, read the references at the bottom. Never guess at how the CLI works. Read references and use the `--help` flag for any command you're about to run.

## Viewing Available OAuth Providers

Vellum assistants can natively integrate with any application that supports OAuth 2.0. Many OAuth providers come pre-configured and ready to use. You can view them by running:

```bash
assistant oauth providers list
```

You can also search for specific providers. Here's an example that searches for the "google" provider:

```bash
assistant oauth providers list --provider-key google
```

## Managed vs Your-Own Mode

All providers support "your-own" mode and some support "managed" mode.

### Default: Managed Mode

"managed" mode relies on a first-class integration with the Vellum Platform. Managed mode is typically easier to set up and get going, often only requiring the user to log in with no additional configuration needed before they can begin using the integration. Managed mode is the recommended method for most users, especially those that are less technical or newer to their Vellum assistant.

When a task needs a managed OAuth connection, present it in chat with `ui_show` using `surface_type: "oauth_connect"` instead of sending the user to Settings or trying to open the OAuth flow from shell. See [Connecting Accounts](references/CONNECTING_ACCOUNTS.md) for the exact surface shape.

Note that using managed mode:

- Requires an account with the Vellum Platform
- May result in billable usage
- Requires that requests to the third party are sent through Vellum's servers

### Your-Own Mode

"your-own" mode requires that the user creates their own OAuth application directly with the third-party and then enter the application's Client ID and Client Secret into Vellum.

Your-own mode is typically best if:

- Vellum does not have a first-party integration with the provider and managed mode is not supported
- The user is more tech-savvy and comfortable setting up OAuth apps
- The user does not want to create an account with the Vellum Platform
- The user is more sensitive to potential billing implications
- The user is sensitive to their data going to the Vellum Platform

### How to Choose

**Default to managed mode whenever the provider supports it.** Check support with:

```bash
assistant oauth providers get <provider-key> --json | jq -r '.managedServiceConfigKey'
```

If this returns a non-null value, managed mode is supported and should be your starting recommendation. Only fall back to your-own mode if:

- The provider does not support managed mode (`managedServiceConfigKey` is null), OR
- The user explicitly wants their own OAuth app (e.g. they're running self-hosted, they're privacy-sensitive, they're configuring a per-assistant Slack app), OR
- The user already has a working your-own connection — don't re-recommend managed mid-flow for already-connected providers.

Do not present managed and your-own as equivalent choices to a fresh user. Lead with managed, then offer your-own as an alternative if they push back.

### Differentiating & Setting a Provider's Mode

You can determine whether a given provider supports managed mode based on the details returned by:

```bash
# Find the provider of interest in the list response
assistant oauth providers list

# Or, return just the provider of interest with their details
assistant oauth providers get <provider-key>
```

You can determine what mode the provider is currently set to use with:

```bash
assistant oauth mode <provider-key>
```

You can update which mode a given provider should use with:

```bash
assistant oauth mode <provider-key> --set "managed"|"your-own"
```

## Troubleshooting

### Permission / Insufficient Scope Errors

If an API request returns a `403 Forbidden`, `401 Unauthorized`, or a message about missing scopes, the connection likely doesn't have the scopes needed for that action. See [Updating Scopes](references/UPDATING_SCOPES.md) for how to disconnect and reconnect with the required scopes.

# Reference

For detailed information on the following topics, see the reference files:

- **[Registering New OAuth Providers](references/REGISTERING_PROVIDERS.md)** - How to register a new OAuth provider that doesn't come with Vellum's defaults
- **[Configuring a New OAuth Application](references/CONFIGURING_APPLICATIONS.md)** - How to configure a user-managed OAuth Application for providers whose mode is set to "your-own"
- **[Connecting Accounts](references/CONNECTING_ACCOUNTS.md)** - How to direct the user to log in and create a new OAuth connection
- **[Updating Scopes](references/UPDATING_SCOPES.md)** - How to update the scopes on an existing connection when additional permissions are needed
- **[Making Requests on Behalf of the User](references/MAKING_REQUESTS.md)** - How to make requests and take actions on behalf of the user once they have connected their account

Excerpt, first 5,837 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/vellum-ai/vellum-assistant
git -C vellum-assistant checkout 19bc86343b63

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 19bc86343b63

Questions about Vellum Oauth Integrations

• github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-oa — the audited source at commit 19bc86343b63 and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology