Supadata

Access Supadata API to fetch YouTube and web data

Overview

The Supadata node's "YouTube → Get Video" operation retrieves detailed information about a specific YouTube video. By providing either the video ID or the full URL, users can fetch metadata such as title, description, channel details, statistics, and more. This is useful for workflows that need to enrich data with YouTube video details, automate content management, or analyze video performance.

Example scenarios:

  • Automatically extract video details when a new YouTube link is added to a database.
  • Enrich CRM records with YouTube video metadata for marketing analysis.
  • Validate and log YouTube video information in automated reporting pipelines.

Properties

Name Type Meaning
Video String The ID or URL of the YouTube video. Accepts both direct video IDs (e.g., dQw4w9WgXcQ) and full URLs (e.g., https://www.youtube.com/watch?v=dQw4w9WgXcQ). This identifies which video to retrieve details for.

Output

The node outputs a JSON object containing the details of the requested YouTube video. While the exact structure depends on the Supadata API response, typical fields may include:

{
  "id": "dQw4w9WgXcQ",
  "title": "Video Title",
  "description": "Full video description...",
  "channelId": "UC_x5XG1OV2P6uZZ5FSM9Ttw",
  "channelTitle": "Channel Name",
  "publishedAt": "2020-01-01T00:00:00Z",
  "statistics": {
    "viewCount": "123456",
    "likeCount": "7890",
    "commentCount": "456"
  },
  "thumbnails": {
    "default": { "url": "..." },
    "medium": { "url": "..." },
    "high": { "url": "..." }
  }
  // ...other metadata fields
}
  • The output does not include binary data; all information is returned as structured JSON.

Dependencies

  • Supadata API: Requires access to the Supadata service, which acts as a proxy to fetch YouTube data.
  • API Credentials: You must configure the supadataApi credential in n8n for authentication.
  • Internet Access: The node needs outbound internet connectivity to reach the Supadata API.

Troubleshooting

Common issues:

  • Invalid Video ID/URL: If the provided video identifier is incorrect or the video does not exist, you may receive an error like "Video not found" or similar.
  • Missing Credentials: If the supadataApi credential is not set up, the node will fail with an authentication error.
  • API Quotas/Rate Limits: Excessive requests may be throttled by the Supadata or underlying YouTube API.
  • Network Issues: Connectivity problems between n8n and Supadata will result in request failures.

Error handling:

  • If "Continue On Fail" is enabled, errors are returned in the output as { "error": "Error message" }.
  • Otherwise, the workflow execution stops and displays the error message.

Links and References

Discussion