Appearance
YouTube
Search, manage, and analyze YouTube videos, channels, and playlists.
| Detail | Value |
|---|---|
| Category | Social Media |
| Base URL | https://www.googleapis.com/youtube/v3 |
| Authentication | OAuth2 |
| Endpoints | 5 |
| Connector key | youtube |
Using YouTube in a workflow
- Go to Connections and click New Connection.
- Pick YouTube from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /search | Search YouTube |
GET /videos | List videos |
GET /channels | List channels |
GET /playlists | List playlists |
GET /commentThreads | List comment threads |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /search
Search YouTube
| Detail | Value |
|---|---|
| Operation ID | social.search |
| Method | GET |
| Path | /search |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
q | query | string | No |
type | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your YouTube connection from the Connection dropdown.
- In the Operation dropdown, select
social.search. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream YouTube API reference.
GET /videos
List videos
| Detail | Value |
|---|---|
| Operation ID | social.listVideos |
| Method | GET |
| Path | /videos |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
part | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your YouTube connection from the Connection dropdown.
- In the Operation dropdown, select
social.listVideos. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream YouTube API reference.
GET /channels
List channels
| Detail | Value |
|---|---|
| Operation ID | social.listChannels |
| Method | GET |
| Path | /channels |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
part | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your YouTube connection from the Connection dropdown.
- In the Operation dropdown, select
social.listChannels. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream YouTube API reference.
GET /playlists
List playlists
| Detail | Value |
|---|---|
| Operation ID | social.listPlaylists |
| Method | GET |
| Path | /playlists |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
part | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your YouTube connection from the Connection dropdown.
- In the Operation dropdown, select
social.listPlaylists. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream YouTube API reference.
GET /commentThreads
List comment threads
| Detail | Value |
|---|---|
| Operation ID | social.listComments |
| Method | GET |
| Path | /commentThreads |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
part | query | string | Yes |
videoId | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your YouTube connection from the Connection dropdown.
- In the Operation dropdown, select
social.listComments. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream YouTube API reference.