Video Content

Get video details

Get detailed information for a YouTube video including title, description, view count, likes, channel information, and more.

When to use this operation:

• Analyzing individual video performance metrics
• Gathering metadata for video databases
• Tracking video statistics over time
• Verifying video availability and status

Get Shorts Details

Get detailed information for a YouTube Shorts video including engagement metrics and short-form specific metadata.

When to use this operation:

• Tracking shorts-specific performance metrics
• Analyzing short-form content engagement
• Comparing shorts vs long-form video performance
• Extracting shorts metadata for databases

Download Thumbnail

Download video or shorts thumbnails in high quality. This operation uses the HTTP Request node to fetch the thumbnail image from the URL provided in the video details or shorts details response.

When to use this operation:

• Downloading thumbnails for content analysis
• Building thumbnail archives for research
• Analyzing thumbnail design patterns
• Creating visual reports with video thumbnails

Prerequisites

Before downloading thumbnails, you must first:

1. Retrieve video data using either:
   • Get video details operation (for regular videos)
   • Get Shorts Details operation (for shorts)
2. Extract the thumbnail URL from the response
3. Use an HTTP Request node to download the thumbnail

Configuration Steps

Step 1: Get Video/Shorts Data

First, add the NexLev node and retrieve the video or shorts details:

1. Add the NexLev node to your workflow
2. Under Resource, select Videos and Short
3. Under Operation, select:
   • Get video details for regular videos
   • Get Shorts Details for shorts
4. Enter the Video ID
5. Execute to retrieve the data

Step 2: Download Thumbnail

Add an HTTP Request node after the NexLev node:

1. Add the HTTP Request node

2. Configure the following parameters:

   • Method: GET
   • Authentication: None
   • Send Query Parameters: Toggle OFF
   • Send Headers: Toggle OFF
   • Send Body: Toggle OFF

3. In the URL field, use the following expression to reference the thumbnail URL:

For regular videos (Get video details):

{
  {
    $json["thumbnail"][4]["url"];
  }
}

For shorts (Get Shorts Details):

{
  {
    $json["thumbnail"][14]["url"];
  }
}

Step 3: Save or Process the Thumbnail

The HTTP Request node will return binary data. You can:

1. View the thumbnail in the n8n interface by clicking the Binary tab
2. Save to disk using a Write Binary File node
3. Upload to cloud storage (Google Drive, Dropbox, etc.)
4. Send via email or webhook

Response

Status Code: 200 OK

Response Type: Binary data (image/webp, image/jpeg, or image/png)

The response contains the raw image data with the following metadata:

{
  "data": {
    "fileName": "maxresdefault.webp",
    "directory": "vi_webp/xILOssyMh1k",
    "fileExtension": "webp",
    "mimeType": "image/webp",
    "fileSize": "40.1 kB"
  }
}

Response Fields:

• fileName - Name of the thumbnail file
• directory - Directory path on YouTube's CDN
• fileExtension - File extension (webp, jpg, png)
• mimeType - MIME type of the image
• fileSize - Size of the thumbnail file (human-readable)

Thumbnail Sizes and Quality

YouTube thumbnails are available in various sizes. Common thumbnail URLs include:

Example Workflow

Here's a complete workflow to download video thumbnails:

1. Manual Trigger node - Add video ID as input
2. NexLev node:
   • Resource: Videos and Short
   • Operation: Get video details or Get Shorts Details
   • Video ID: {{ $json.videoId }}
3. HTTP Request node:
   • Method: GET
   • URL: {{ $json["thumbnail"][14]["url"] }} (adjust index as needed)
4. Write Binary File node (optional):
   • File Name: {{ $json.videoId }}_thumbnail.webp
   • Destination: Your desired save location

Use Cases

• Content Creation: Download thumbnails for video analysis or content curation
• Archive Building: Save thumbnails alongside video metadata for documentation
• Design Inspiration: Collect high-performing video thumbnails for design reference
• Automated Reporting: Include video thumbnails in automated reports or dashboards
• Social Media: Reuse thumbnails for cross-platform content promotion
• Quality Control: Download thumbnails to verify video branding and consistency

Get Comments

Get comments for a YouTube video including comment text, author information, likes, and reply counts. Supports pagination via continuation tokens to retrieve additional comments beyond the initial response.

When to use this operation:

• Analyzing audience sentiment and feedback
• Tracking engagement patterns in comments
• Building comment databases for research
• Identifying influential commenters and discussions

Get Transcript

Get the complete transcript/captions for a YouTube video with timestamps, useful for content analysis, summarization, or accessibility purposes.

When to use this operation:

• Extracting video content for text analysis
• Creating searchable video archives
• Generating video summaries or highlights
• Making content accessible with captions

Get Bulk Transcript

Get transcripts for multiple YouTube videos in a single request, perfect for batch processing and analyzing large numbers of videos efficiently.

When to use this operation:

• Batch processing transcripts for multiple videos
• Building large transcript datasets efficiently
• Analyzing content across video collections
• Reducing API calls for transcript extraction

Configuration

1. Add the NexLev node to your workflow
2. Under Resource, select Videos and Short
3. Under Operation, select Get Bulk Transcript
4. Under Credential to connect with, select your NexLev account
5. In the Video IDs field, enter the YouTube video IDs separated by commas (e.g., 8bMh8azh3CY, mwKJfNYwvm8)

Use Cases

• Batch Content Analysis: Extract transcripts from multiple videos simultaneously for content analysis
• Video Comparison: Compare transcripts across multiple videos to identify patterns or similarities
• Research & Data Mining: Gather large datasets of video transcripts for research purposes
• SEO Optimization: Analyze transcript content across multiple videos to identify keyword opportunities
• Content Curation: Extract transcripts from entire video playlists or channels efficiently
• Translation Workflows: Batch process transcripts for translation services
• Accessibility Compliance: Extract transcripts from multiple videos for accessibility documentation
• Training Data: Collect transcript data for machine learning or AI model training

Best Practices

• Batch Size: Request transcripts for up to 10 videos at a time (maximum limit)
• Error Handling: Always check the success field for each video in the results array
• Retry Logic: Implement retry logic for failed videos with exponential backoff
• Data Validation: Verify that transcripts are available before making bulk requests
• Storage: Consider storing retrieved transcripts to avoid repeated API calls
• Processing: Process results asynchronously for large batches to avoid workflow timeouts
• Large Lists: For lists exceeding 10 videos, split them into multiple batch requests

Example Workflow

Here's a complete workflow to process bulk transcripts:

1. Manual Trigger node - Add list of video IDs
2. Code node - Format video IDs as comma-separated string
3. NexLev node:
   • Resource: Videos and Short
   • Operation: Get Bulk Transcript
   • Video IDs: {{ $json.videoIds }}
4. Code node - Process each transcript result
5. Split In Batches node - Process results in manageable chunks
6. Google Sheets or Database node - Store transcript data

Comparing Single vs Bulk Transcript Retrieval

Notes:

• The bulk transcript operation processes videos in parallel for faster results
• Each video in the results array follows the same structure as the individual Get Transcript operation
• Videos without captions will return success: false with an appropriate error message
• The total, successful, and failed counts help you track the overall success rate
• Auto-generated captions are indicated in the language title for each video
• URLs and encoded parameters in the response may vary based on the video's available languages
• Consider implementing pagination for very large lists by splitting them into multiple bulk requests

Get Subtitle

Get all available subtitle/caption information for a YouTube video, including subtitle URLs, language options, and translation languages. This operation retrieves metadata about available subtitles without downloading the actual subtitle content.

When to use this operation:

• Discovering available subtitle languages
• Planning multi-language content strategies
• Extracting subtitle download URLs
• Analyzing language coverage for videos

Use Cases:

• Multi-language Content: Retrieve subtitles in multiple languages for international audiences
• Accessibility: Extract subtitles to make video content accessible in different formats
• Content Translation: Identify available subtitle languages and translation options
• Subtitle Management: Build workflows to download and process subtitles for archiving
• Language Analysis: Analyze which languages are available for videos in your niche
• Automated Localization: Use subtitle URLs to fetch and translate content automatically

Get Bulk Subtitle

Get subtitle information for multiple YouTube videos in a single request, perfect for batch processing and analyzing subtitle availability across large numbers of videos efficiently.

When to use this operation:

• Batch checking subtitle availability
• Analyzing language coverage across video collections
• Planning localization strategies at scale
• Reducing API calls for subtitle metadata

Configuration

1. Add the NexLev node to your workflow
2. Under Resource, select Videos and Short
3. Under Operation, select Get Bulk Subtitle
4. Under Credential to connect with, select your NexLev account
5. In the Video IDs field, enter the YouTube video IDs separated by commas (e.g., mwKJfNYwvm8, Z4hVGCWH1Kc)

Use Cases

• Multi-language Analysis: Analyze subtitle availability across multiple videos for localization planning
• Content Accessibility Audit: Check which videos have subtitles and in what languages
• Batch Subtitle Extraction: Retrieve subtitle URLs for multiple videos to download in bulk
• Language Coverage: Determine language coverage across a video library or channel
• SEO Research: Identify videos with subtitles for better search optimization
• Translation Workflows: Build automated workflows to process subtitles in multiple languages
• Compliance Checking: Verify that videos meet accessibility requirements with proper subtitles
• Content Localization: Identify which videos need additional subtitle languages

Best Practices

• Batch Size: Request subtitle data for up to 10 videos at a time (maximum limit)
• Error Handling: Always check the success field for each video in the results array
• Retry Logic: Implement retry logic for failed videos with exponential backoff
• URL Expiration: Remember that subtitle URLs are time-limited and will expire
• Storage: Store retrieved subtitle metadata to avoid repeated API calls
• Processing: Process results asynchronously for large batches to avoid workflow timeouts
• Large Lists: For lists exceeding 10 videos, split them into multiple batch requests
• Translation Planning: Use the translationLanguages array to plan content localization

Example Workflow

Here's a complete workflow to process bulk subtitle data:

1. Manual Trigger node - Add list of video IDs
2. Code node - Format video IDs as comma-separated string
3. NexLev node:
   • Resource: Videos and Short
   • Operation: Get Bulk Subtitle
   • Video IDs: {{ $json.videoIds }}
4. Code node - Process each subtitle result and extract available languages
5. Split In Batches node - Process results in manageable chunks
6. Google Sheets or Database node - Store subtitle metadata

Comparing Single vs Bulk Subtitle Retrieval

Notes:

• The bulk subtitle operation processes videos in parallel for faster results
• Each video in the results array follows the same structure as the individual Get Subtitle operation
• Videos without subtitles will return success: false with an appropriate error message
• The total, successful, and failed counts help you track the overall success rate
• Auto-generated subtitles are indicated with "(auto-generated)" in the language name for each video
• Subtitle URLs are time-limited and will expire after the time specified in the expire parameter
• The translationLanguages array typically contains 100+ languages for translation options
• Consider implementing pagination for very large lists by splitting them into multiple bulk requests
• Use the HTTP Request node with the subtitle URLs to download actual subtitle content

Get RPM

Get Revenue Per Mille (RPM) data for a YouTube video. RPM represents the estimated revenue per 1,000 video views, providing insights into video monetization performance.

When to use this operation:

• Researching profitable content niches
• Analyzing monetization potential of video topics
• Comparing revenue across content categories
• Making data-driven content strategy decisions

Configuration

1. Add the NexLev node to your workflow
2. Under Resource, select Videos and Short
3. Under Operation, select Get RPM
4. Under Credential to connect with, select your NexLev account
5. In the Video ID field, enter the YouTube video ID you want to retrieve RPM data for

Use Cases

• Niche Research: Compare RPM across different video niches to identify profitable content areas
• Content Strategy: Analyze which types of videos generate higher RPM to inform content planning
• Competitor Analysis: Understand monetization potential of competitor videos
• Revenue Forecasting: Estimate potential earnings based on RPM and projected views
• Channel Optimization: Identify high-RPM topics to prioritize in content creation
• Market Analysis: Track RPM trends across different content categories
• Investment Decisions: Evaluate the monetization potential before creating similar content
• Performance Benchmarking: Compare your video RPM against industry standards

Best Practices

• Multiple Samples: Analyze RPM across multiple videos to identify patterns and trends
• Time Considerations: RPM can vary based on seasonality, ad demand, and viewer geography
• Niche Comparison: Compare videos within the same niche for more accurate insights
• Combined Analysis: Use RPM data alongside view counts and engagement metrics
• Regular Monitoring: Track RPM trends over time to identify changes in monetization
• Privacy Respect: Remember that RPM estimates are approximations, not actual creator earnings
• Content Planning: Use RPM insights to guide content strategy, not as the sole decision factor

Example Workflow

Here's a complete workflow to analyze video RPM:

1. Manual Trigger node - Add video ID as input
2. NexLev node:
   • Resource: Videos and Short
   • Operation: Get RPM
   • Video ID: {{ $json.videoId }}
3. Code node - Calculate potential revenue based on RPM and views
4. Google Sheets node - Log RPM data for tracking
5. Filter node - Identify high-RPM videos (e.g., RPM > $5)
6. Send Email node - Alert for high-performing niches