> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/integrations/overview/social/youtube.md).

# YouTube

The YouTube Integration step allows you to retrieve captions from videos on your own YouTube channel. This integration enables content repurposing by extracting text content from your video library for use in articles, summaries, and other content formats.

### How to Configure the YouTube Integration Step

#### Action Type

**Retrieve Video Captions**: Extract captions/transcript from your YouTube video

#### Video URL or ID

Enter the YouTube video ID from your channel:

* Video ID: `dQw4w9WgXcQ`

#### Key Output Fields

* `full_text`: Complete captions as a single string
* `transcript`: Array of timed caption segments
* `video_title`: Title of your video
* `video_id`: YouTube video identifier

### Common Use Cases

* Transform video content into blog posts
* Generate video summaries and key points
* Create show notes for podcast episodes
* Extract quotes for social media content
* Build searchable content from your video library

**Note:** You must authenticate your YouTube account in AirOps Settings > Integrations before using this step.


---

# 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.airops.com/integrations/overview/social/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.