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, specifically supporting operations such as retrieving playlist details. The "Get Playlist" operation allows users to obtain metadata about a specific YouTube playlist by providing its ID or URL. This is useful for scenarios where you want to automate the collection of playlist information for content management, analytics, or integration into other workflows.

For example, you could use this node to:

  • Automatically gather playlist titles, descriptions, and other metadata for reporting.
  • Feed playlist data into a CMS or database.
  • Trigger downstream processes based on playlist content updates.

Properties

Name Meaning
Playlist The ID or full URL of the YouTube playlist you want to retrieve details for.

The "Playlist" property accepts either the raw playlist ID (e.g., PLlaN88a7y2_plecYoJxvRFTLHVbIVAOoc) or the full playlist URL (e.g., https://www.youtube.com/playlist?list=PLlaN88a7y2_plecYoJxvRFTLHVbIVAOoc).

Output

The output is a JSON object containing the details of the requested YouTube playlist. The exact structure depends on the Supadata API response but typically includes fields such as:

  • Playlist title
  • Description
  • Number of videos
  • Playlist thumbnails
  • Other metadata related to the playlist

The node outputs this data as JSON in the json field of each item. There is no binary data output for 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 Playlist ID or URL: If the playlist identifier is incorrect or malformed, the API may return an error or empty result. Ensure the playlist 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 be throttled by the Supadata API. Implement retry logic or reduce request frequency if encountering rate limit errors.
  • Network Issues: Connectivity problems can cause request failures. Check network status and proxy settings if applicable.

Links and References

Discussion