YouTube
YouTube is entry 3222 on the integrations list SHAI was asked to match. SHAI has not written this tool up, so it will not describe it — what it records is the route.
needs-operator-provider
How SHAI connects to it
SHAI connects to it through Pipedream, which holds the sign-in so no token ever reaches SHAI or the model. Pipedream publishes 2 components under this name — `youtube_analytics_api`, `youtube_data_api` — and SHAI will not pick one for you: you choose when you connect.
What it needs
the operator's Pipedream project — then nothing from you but a sign-in
Pipedream publishes 2 components under this name (`youtube_data_api`, `youtube_analytics_api`). SHAI will not pick one for you — choose the one you want when you connect, and it runs through the same door as every other Pipedream app. One click once the operator connects a Pipedream project to this deployment.
Route read from https://github.com/PipedreamHQ/pipedream@58ecb26:components/youtube_data_api/youtube_data_api.app.mjs · https://github.com/PipedreamHQ/pipedream@58ecb26:components/youtube_analytics_api/youtube_analytics_api.app.mjs · verified 2026-09-16 · entry 3222 of the integrations list
Whatever a run does with this tool goes through one door and one approval row: reading is allowed by default, anything that writes, sends or spends stops and asks first, and you can set that per tool on Connections. Plain text for this page: /integrations/youtube/index.md.