Supadata

Access Supadata API to fetch YouTube and web data

Actions7

Overview

The Supadata node's "Web" resource with the "Scrape URL" operation allows you to scrape data from a specified web page by providing its URL. This is useful for extracting content or metadata from public websites directly within your n8n workflows, enabling automation scenarios such as:

  • Collecting product information from e-commerce sites.
  • Extracting article text or metadata from news pages.
  • Gathering structured data from any accessible web page.

Example use cases:

  • Automatically monitor and extract prices from competitor websites.
  • Aggregate headlines from multiple news sources.
  • Pull contact details from company profile pages.

Properties

Name Type Meaning
URL String The URL of the web page to be scraped. This should be a valid, publicly accessible web address (e.g., https://example.com).

Output

The output will be a JSON object containing the scraped data from the provided URL. The exact structure of this JSON depends on the response from the Supadata API, but typically it may include fields such as:

  • title: The title of the web page.
  • description: Meta description or summary.
  • content: Main textual content extracted from the page.
  • url: The original URL that was scraped.
  • Additional metadata or structured data if available.

Note:
If an error occurs during scraping, and "Continue On Fail" is enabled, the output will contain an error field with the error message.

Dependencies

  • Supadata API: Requires access to the Supadata API service.
  • API Key: You must configure the supadataApi credentials in n8n for authentication.
  • Network Access: The n8n instance must be able to reach both the Supadata API and the target URLs to be scraped.

Troubleshooting

Common Issues:

  • Invalid URL: If the provided URL is malformed or inaccessible, you may receive an error such as Invalid URL or Failed to fetch.
  • Authentication Error: If the Supadata API key is missing or incorrect, errors like 401 Unauthorized or Invalid credentials may occur.
  • Blocked by Target Site: Some websites may block automated scraping, resulting in errors like 403 Forbidden or empty content.
  • API Limits: Exceeding rate limits on the Supadata API may result in 429 Too Many Requests.

Error Handling:

  • When "Continue On Fail" is enabled, errors are returned in the output as { "error": "<error message>" }.
  • Otherwise, the workflow execution will stop on error.

Links and References

Discussion