> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/workflow-builder/nodes/apps/youtube.md).

# YouTube

<figure><img src="/files/KIoRBlhwEeX0juY3Letd" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/s6qv38LiOEFYDnCM06Dn" alt=""><figcaption></figcaption></figure>

## Description

The YouTube component allows you to analyze and extract meaning from YouTube videos.&#x20;

{% hint style="info" %}
Note that the YouTube video must have a subtitle for it to be able to be analyzed.
{% endhint %}

The YouTube component value has the identifier of ytb-**X**, where **X** represents the instance number of the YouTube component.

## Inputs

The YouTube component does not have any input connections.

## Component settings

| Parameter Name    | Description                                                                 |
| ----------------- | --------------------------------------------------------------------------- |
| URL               | This parameter specifies the URL or collection of URLs to source data from. |
| Detected language | Set the language for your video.                                            |

## Advanced configurations

| Options        | Description                                                                                                                                                                                                               |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Enable caching | This option determines whether the results of the component are cached. This means that on the next run of the Flow, Diaflow will utilize the previous computed component output, as long as the inputs have not changed. |
| Caching time   | <p>Only applicable if the "Enable Caching" option has been enabled.<br>This parameter controls how long Diaflow will wait before automatically clearing the cache.</p>                                                    |

## Outputs

The YouTube component has the following output connections.

| Output Name            | Description                                                                        | Constraints                                                            |
| ---------------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| To VectorDB/LLM/Python | This output connection represents the YouTube video at the specified URL location. | This must be connected to either an LLM, Python or VectorDB component. |

## Use case

Here is a simple use case of the YouTube component, where the YouTube component is being used to provide input context to an OpenAI GPT AI component, which generates an answer to a user supplied question regarding the YouTube video.

<figure><img src="/files/AsoJ05eg9wHAHIGTJTL5" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.diaflow.io/workflow-builder/nodes/apps/youtube.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.