Supadata

Access Supadata API to fetch YouTube and web data

Actions7

Overview

The Supadata node's "YouTube → Get Channel" operation retrieves detailed information about a specified YouTube channel. This is useful for workflows that need to fetch and process metadata about YouTube channels, such as automating reporting, monitoring channel statistics, or integrating channel data into dashboards.

Practical examples:

  • Automatically collect and store details of multiple YouTube channels for analytics.
  • Enrich CRM records with YouTube channel information based on user input.
  • Trigger notifications or actions when specific channel attributes change.

Properties

Name Type Meaning
Channel String The ID or URL of the YouTube channel. Accepts either the direct channel ID or full channel URL.

Output

The output is a JSON object containing details about the requested YouTube channel. While the exact structure depends on the Supadata API response, typical fields may include:

{
  "id": "UC_x5XG1OV2P6uZZ5FSM9Ttw",
  "title": "Google Developers",
  "description": "The Google Developers channel...",
  "publishedAt": "2007-08-23T00:34:43Z",
  "thumbnails": {
    "default": { "url": "...", "width": 88, "height": 88 },
    "medium": { "url": "...", "width": 240, "height": 240 },
    "high": { "url": "...", "width": 800, "height": 800 }
  },
  "statistics": {
    "viewCount": "123456789",
    "subscriberCount": "1000000",
    "videoCount": "500"
  }
}

Note: Actual fields may vary depending on the Supadata API.

Dependencies

  • Supadata API: Requires access to the Supadata API service.
  • API Key: You must configure valid Supadata API credentials in n8n under the name supadataApi.

Troubleshooting

Common issues:

  • Invalid Channel ID/URL: If the provided channel identifier is incorrect or malformed, the node will return an error such as "Channel not found" or "Invalid channel ID". Double-check the input format.
  • Missing Credentials: If Supadata API credentials are not set up in n8n, you may see authentication errors like "401 Unauthorized" or "Missing API key".
  • API Rate Limits: Excessive requests may trigger rate limiting from the Supadata API, resulting in errors like "429 Too Many Requests".
  • Network Issues: Connectivity problems can cause timeouts or "Network Error" messages.

How to resolve:

  • Ensure the "Channel" property contains a valid YouTube channel ID or URL.
  • Verify that your Supadata API credentials are correctly configured in n8n.
  • If rate-limited, reduce request frequency or contact Supadata support for higher limits.
  • Check your network connection if you encounter connectivity errors.

Links and References

Discussion