Skip to main content
Per-app Google setup is deprecated. All Google apps now share one Google OAuth client and one Redirect URI. To use your own client, follow the Google setup guide. Credentials saved for one Google app apply to all of them.

​
Overview

OneCLI connects AI agents to YouTube through Google’s OAuth flow. Agents can search for videos, list channel content, manage playlists, and read analytics data. The gateway injects OAuth credentials into requests to the YouTube Data API automatically. This is useful for agents that manage video content, curate playlists, monitor channel performance, or gather video metadata.

​
What you will set up

  • A YouTube connection through Google OAuth, in one click on OneCLI Cloud or with your own client
  • Automatic token injection on YouTube API requests
  • Per-agent, per-tool access to your channel

​
Connect on OneCLI Cloud (one click)

1

Go to Connections

Open the OneCLI dashboard and navigate to Connections > YouTube.
2

Authorize

Click Connect YouTube. You’ll go straight to Google: pick your account, review the permissions, and click Allow. No Google Cloud setup needed.
On self-hosted OneCLI, or to use your own Google client on Cloud, see Use your own Google client.

​
Use your own Google client

This is for self-hosted OneCLI, and for OneCLI Cloud when you choose Custom credentials instead of one-click. One Google client serves every Google app in OneCLI, so you set it up once. If you already did it for another Google app, skip to step 2.

1. Set up your Google client

Follow the Google setup guide. It enables the Google APIs, sets up the consent screen, creates the OAuth client, and adds the Redirect URI.You paste the client into Connections > YouTube > Custom credentials, under the Redirect URI the guide asks you to register:
OneCLI Custom credentials card for YouTube with the setup guide link, the Redirect URI and its copy button, and the Client ID and Client Secret fields.

Custom credentials for YouTube in OneCLI.

Open Connections > YouTube, select Connect YouTube, pick your Google account, and click Allow.
OneCLI connect window for YouTube showing Configuration required and the Configure credentials button.

The YouTube connect window before a Google client is set up.

​
What agents can do

  • Search for videos by keyword, topic, or channel
  • List videos on a channel with metadata (title, description, publish date, view count)
  • Get detailed video information (duration, tags, category, thumbnail URLs)
  • Create, update, and delete playlists
  • Add and remove videos from playlists
  • Read channel analytics (views, watch time, subscribers gained/lost)
  • List and read video comments
  • Post comments on videos
  • Read video captions and transcripts
  • List channel subscriptions

​
Controlling access

Access is per agent: grant the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization rules add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches YouTube.

​
FAQ

No. The token stays in OneCLI, and the gateway adds it at the proxy. See How it works.
Yes. A read-only agent is a single grant.
Open Connections > YouTube and connect again with the account you want. Agents with access use the new connection automatically.