N8N Tools - YouTube Enhanced
Actions83
- Videos Actions
- Channels Actions
- Playlists Actions
- Search Actions
- Analytics Actions
- Get Channel Analytics
- Get Video Analytics
- Get Playlist Analytics
- Get Content Owner Analytics
- Get Audience Retention
- Get Demographics
- Get Geographic Data
- Get Device Data
- Get Traffic Source Data
- Get Revenue Data
- Get Ad Performance Data
- Get Subscriber Analytics
- Get Playback Location Data
- Get Video Performance Data
- Get Playlist Performance Data
- Get Annotation Performance Data
- Get Card Performance Data
- Get Sharing Service Data
- Get Live Streaming Data
- Get Content Type Data
- Get Time Based Data
- Comments Actions
- Subscriptions Actions
- Live Streaming Actions
- Video Upload Actions
- Community Posts Actions
- Thumbnails Actions
- Captions Actions
- Channel Memberships Actions
- Super Chat & Thanks Actions
Overview
The node "N8N Tools - YouTube Enhanced" integrates deeply with the YouTube Data API v3 and YouTube Analytics API, providing extensive capabilities to retrieve and manage YouTube data within n8n workflows. Specifically, the Analytics > Get Card Performance Data operation fetches detailed analytics about card performance on a specified YouTube channel over a defined date range.
This operation is useful for content creators, marketers, and analysts who want to understand how interactive cards (which can promote videos, playlists, channels, or external links) are performing in terms of impressions, clicks, and click rates. For example, a YouTube channel manager could use this node to track which cards generate the most engagement and optimize their video content strategy accordingly.
Properties
| Name | Meaning |
|---|---|
| Channel ID | The unique identifier of the YouTube channel for which to retrieve card performance analytics. |
| Start Date | The start date (inclusive) for the analytics data period. |
| End Date | The end date (inclusive) for the analytics data period. |
| Metrics | The specific metrics to include in the report. Options include: Views, Estimated Minutes Watched, Average View Duration, Average View Percentage, Subscribers, Likes, Dislikes, Comments, Shares, Estimated Revenue, Ad Revenue, Gross Revenue, CPM, CPC, Impressions, Monetized Playbacks, Playback Based CPM, Annotation Impressions, Annotation Clicks, Annotation Clickable Impressions, Annotation Closable Impressions, Annotation Closes, Annotation Close Rate, Card Impressions, Card Clicks, Card Click Rate, Card Teaser Impressions, Card Teaser Clicks, Card Teaser Click Rate, Audience Watch Ratio, Relative Retention Performance. Default includes "views" and "estimatedMinutesWatched". |
| Max Results | Maximum number of results to return (minimum 1, maximum 1000). Defaults to 100. |
| Start Index | The index of the first result to return (minimum 1). Defaults to 1. |
Output
The output JSON contains the analytics data retrieved from YouTube's Analytics API for card performance on the specified channel. This typically includes:
- Time series or aggregated data points for the requested metrics (e.g., card impressions, card clicks, card click rate).
- Data structured according to the dimensions and filters applied (in this case, mainly by date range and channel).
- Each item corresponds to a set of metric values for the given parameters.
No binary data output is indicated for this operation.
Dependencies
- Requires an active subscription and valid API key credential for the "N8N Tools API" service.
- Requires OAuth2 credentials for YouTube API access.
- The node internally uses helper classes that wrap YouTube API endpoints for analytics.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Invalid subscription or API key error: If the node throws an error indicating invalid subscription or API key, verify that the API key credential is correct and has the necessary permissions.
- API quota limits: YouTube API enforces quotas; exceeding them may cause errors or incomplete data. Monitor usage and adjust requests accordingly.
- Date range issues: Ensure the start date is before or equal to the end date; otherwise, the API may return errors or empty results.
- Missing required parameters: The Channel ID, Start Date, End Date, and Metrics are mandatory. Omitting any will cause the node to fail.
- Network or connectivity problems: Temporary network issues can cause request failures; retrying may resolve transient errors.