> 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.md).

# Social

Social Steps connect your AirOps workflows with social media platforms, enabling content repurposing, community engagement, and brand monitoring. These integrations allow you to leverage social content and automate your social media presence.

The Social Steps include:

1. [**YouTube**](https://docs.airops.com/integrations/overview/social/youtube.md) -- retrieve captions from videos for content repurposing and analysis
2. [**Reddit**](https://docs.airops.com/integrations/overview/social/reddit.md) -- monitor brand mentions, engage with communities, and manage your Reddit presence

Social integrations transform how you manage your social media presence by enabling automated content workflows across platforms. These connections allow you to repurpose video content into written formats, monitor relevant conversations, and engage with your audience systematically.

With Social Steps, you can build workflows that transform video content into blog posts and articles, extract insights from community discussions, automate brand monitoring across platforms, and create data-driven social media strategies.

{% hint style="info" %}
Note: Social Steps require authentication with the respective platforms. Always follow each platform's terms of service and community guidelines when using automated workflows.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/integrations/overview/social.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
