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 "Get Time Based Data" operation under the Analytics resource in this YouTube Enhanced node fetches detailed time-series analytics data for a specified YouTube channel. It allows users to retrieve various metrics grouped by different dimensions over a defined date range. This is particularly useful for content creators, marketers, and analysts who want to track channel performance trends, understand audience engagement over time, and make data-driven decisions.
Practical examples include:
- Tracking daily views and watch time to identify peak engagement periods.
- Analyzing subscriber growth or loss over months.
- Grouping revenue metrics by device type or geography to optimize monetization strategies.
Properties
| Name | Meaning |
|---|---|
| Channel ID | The unique identifier of the YouTube channel for which analytics data is requested. |
| Start Date | The beginning date of the period for which analytics data should be retrieved. |
| End Date | The ending date of the period for which analytics data should be retrieved. |
| Metrics | The specific analytics metrics to include in the report. Options include: Views, Estimated Minutes Watched, Average View Duration, Subscribers, Likes, Comments, Shares, Revenue-related metrics (Estimated Revenue, Ad Revenue, Gross Revenue), Impressions, Annotation and Card performance metrics, Audience Watch Ratio, and more. |
| Dimensions | The dimensions by which to group the analytics data. Options include: Date (day, month, year), Video, Playlist, Channel, Age Group, Gender, Country, Device Type, Operating System, Browser, Traffic Source Type, Revenue Source Type, Ad Type, Subscribed Status, Playback Location Type, Annotation Type, Card Type, Sharing Service, Live or On Demand, Content Type, Elapsed Video Time Ratio. Default is "day". |
| 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 node outputs an array of JSON objects representing the analytics data retrieved from YouTube for the specified channel and parameters. Each object contains the requested metrics grouped by the selected dimensions over the specified date range.
The exact structure depends on the chosen metrics and dimensions but typically includes fields such as dates, metric values (e.g., views, estimated minutes watched), and dimension identifiers (e.g., country codes, device types).
No binary data output is produced by this operation.
Dependencies
- Requires a valid API key credential for the external YouTube analytics service provided via the "N8N Tools API".
- The node performs an initial validation request to the external API endpoint to verify subscription and API key validity.
- Proper configuration of the API URL and API key in the node credentials is necessary.
- The node uses internal helper classes to interact with the YouTube Analytics API.
Troubleshooting
- Invalid Subscription or API Key: If the node throws an error indicating invalid subscription or API key, verify that the API key credential is correctly configured and active.
- API Validation Failure: Network issues or incorrect API URLs can cause validation failures. Ensure network connectivity and correct API endpoint configuration.
- Missing Required Parameters: The operation requires
channelId,startDate,endDate, and at least one metric. Omitting these will cause errors. - Exceeding Max Results Limits: Requesting more than 1000 results may lead to errors; adjust
maxResultsaccordingly. - Empty or Incorrect Dimension/Metrics Values: Using unsupported or misspelled dimension or metric names may result in no data or errors.
- Continue on Fail Behavior: If enabled, the node will continue processing other items even if some fail, returning error details per item.