Supadata

Access Supadata API to fetch YouTube and web data

Actions7

Overview

This node integrates with the Supadata API to fetch detailed information from YouTube and web sources. Specifically, for the YouTube - Get Video operation, it retrieves detailed metadata about a specific YouTube video by its ID or URL. This is useful when you want to enrich workflows with video details such as title, description, statistics, or other metadata without manually visiting YouTube.

Common scenarios:

  • Automatically fetching video details for content curation or analysis.
  • Enriching marketing or social media automation workflows with video metadata.
  • Integrating YouTube video data into reporting dashboards or databases.

Example:
Given a YouTube video URL or ID, the node returns structured information about that video, which can then be used downstream in your workflow for further processing or decision-making.

Properties

Name Meaning
Video The ID or full URL of the YouTube video to retrieve details for. Example: dQw4w9WgXcQ or https://www.youtube.com/watch?v=dQw4w9WgXcQ

Output

The output is a JSON object containing detailed information about the specified YouTube video. The exact structure depends on the Supadata API response but typically includes fields such as:

  • Video title
  • Description
  • Channel information
  • View count
  • Like count
  • Upload date
  • Duration
  • Other metadata related to the video

The output is returned as an array of JSON objects (usually one per input item), suitable for further processing in n8n workflows.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Supadata API via an API key credential configured in n8n.
  • Internet access to call the Supadata API endpoints.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Invalid Video ID or URL: If the provided video identifier is incorrect or malformed, the API may return an error or empty result. Ensure the video ID or URL is valid.
  • API Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
  • Rate Limits: Excessive requests might trigger rate limiting by the Supadata API. Consider adding delays or reducing request frequency.
  • Network Issues: Connectivity problems can cause request failures. Check network status and proxy settings if applicable.
  • Error Messages: The node throws errors with messages from the API. If "video not found" or similar appears, verify the video exists and is publicly accessible.

Links and References

Discussion