> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# YouTube

> Connect YouTube to Tess to find videos, channel data, and content context from chat and agents.

The **YouTube** connector integrates Tess with YouTube. Once connected, the AI can help find videos and channel information and turn that context into useful summaries inside chats and agents.

YouTube is part of the Tess [Connectors](/en/connectors) ecosystem and uses **OAuth** authentication for Apps connectors.

## Prerequisites

<Info>
  * A Google account with access to the YouTube data you need.
  * Permission to authorize YouTube-related OAuth scopes.
</Info>

## How to connect

<Tip>
  On some Apps connectors, the OAuth consent screen may show a third-party connection bridge name rather than Tess. That is normal—review the requested permissions and continue if they match what you expect.
</Tip>

<Steps>
  <Step title="Open the Connectors panel">
    In chat, click the **+** next to the message box and select **Connectors**.
    You can also manage connectors while editing an agent in Agent Studio.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/youtube/01-connect-panel.png" alt="PRINT: (Connectors panel with YouTube highlighted and the Connect button visible)" />
    </Frame>
  </Step>

  <Step title="Find YouTube and click Connect">
    Under **Apps**, locate **YouTube** and click **Connect** to start authentication.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/youtube/02-oauth-consent.png" alt="PRINT: (Provider authorization / consent screen for YouTube)" />
    </Frame>
  </Step>

  <Step title="Authorize access">
    Sign in with the account you want to use and review the requested permissions before confirming.
  </Step>

  <Step title="Confirm it is active">
    Back in Tess, **YouTube** should appear under **Connected**, ready for chats and agents.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/youtube/03-connected.png" alt="PRINT: (Tess callback or Connectors list showing YouTube as Connected with a success state)" />
    </Frame>
  </Step>
</Steps>

## What you can do

* **Search videos and channels** relevant to a topic
* **Pull video metadata** such as titles, descriptions, and basic stats when available
* **Support content research** for marketing, education, and product teams
* **Summarize findings** into briefs or next-step recommendations
* **Keep research inside Tess** instead of switching tabs

## Example prompts

> 1. Find the 5 most relevant YouTube videos about AI agents for enterprise and summarize each one.
> 2. What are the latest uploads from our brand channel?
> 3. Create a short brief from videos about HubSpot automation for sales teams.
> 4. Compare the top results for 'Google Sheets automation' and list common tips.

## Best practices

* Be specific about topic, language, and freshness.
* Ask for sources/titles in the answer when you need to reuse the research.
* In agents, clarify whether YouTube is for research, channel monitoring, or content briefs.

## Troubleshooting

<AccordionGroup>
  <Accordion icon="circle-question" title="Authorization fails">
    Reconnect with the Google account that owns or can access the needed YouTube data.
  </Accordion>

  <Accordion icon="circle-question" title="401 / connection dropped">
    Reconnect YouTube in Connectors after credential or policy changes.
  </Accordion>

  <Accordion icon="circle-question" title="Limited results">
    Some channel or private data may be unavailable depending on account permissions.
  </Accordion>
</AccordionGroup>

<Note>
  Tess uses the permissions of the connected account. It does not expand access beyond what that account can already do.

  Connectors involve access to external systems. Only connect accounts that fit the usage context, and review permissions carefully.
</Note>