FetchSERP

Interact with the FetchSERP API

Overview

This node integrates with the FetchSERP API to perform various web data retrieval operations. Specifically, the "Scrape Webpage" operation allows users to scrape content from a specified webpage by sending query parameters to the API. This is useful for extracting raw HTML or structured data from websites without needing to build custom scrapers.

Common scenarios include:

  • Extracting product details or pricing information from e-commerce sites.
  • Gathering news articles or blog content for analysis.
  • Collecting metadata or SEO-related information from webpages.

For example, a user might provide a domain or URL as a query parameter to retrieve the full HTML content of that page for further processing in an automation workflow.

Properties

Name Meaning
Query Parameters (JSON) JSON object specifying query parameters for the scraping request (e.g., {"domain":"example.com"}).

Output

The node outputs an array of items where each item contains a json field holding the response from the FetchSERP API for the scrape request. The structure of this JSON depends on the API's response but generally includes the scraped webpage data such as HTML content or extracted elements.

If the API returns binary data (not indicated here), it would be included accordingly, but this node primarily handles JSON responses representing webpage content.

Dependencies

  • Requires an API key credential for the FetchSERP service.
  • The node makes HTTP requests to the FetchSERP API endpoint (https://www.fetchserp.com/api/v1/scrape).
  • Proper configuration of the API key credential within n8n is necessary for authentication.

Troubleshooting

  • Unknown operation error: If the operation name is incorrect or unsupported, the node will throw an error indicating the unknown operation. Ensure the operation is set exactly to "scrape_webpage".
  • Invalid JSON in Query Parameters: If the "Query Parameters (JSON)" input is not valid JSON, parsing will fail. Verify the JSON syntax before running.
  • API Authentication errors: If the API key is missing or invalid, the node will receive authorization errors. Confirm the API key is correctly configured and active.
  • Network or API errors: Any HTTP request failure will cause the node to error out unless "Continue On Fail" is enabled, in which case the error message will be returned in the output JSON under an error property.

Links and References

Discussion