What is the primary function of the n8n ScrapingBee node?
The ScrapingBee node allows you to automate web scraping tasks directly within your n8n workflow. This powerful node sends requests to the ScrapingBee API, handling complex tasks like bypassing geo-blocking or CAPTCHAs, and fetching the desired data.
How do I set up the required API key for this Integrations?
Configuration is managed through the Credentials section in n8n. When you add the ScrapingBee node to your workflow, you create or select a credential set where you input your ScrapingBee API key, securing the Integrations.
Can the ScrapingBee node handle advanced scraping options like JavaScript rendering?
Yes, this node supports advanced parameters offered by ScrapingBee, including enabling JavaScript rendering (necessary for modern single-page applications) and specifying geo-location or proxies, making it a highly versatile node.
How does a workflow trigger the scraping process using this node?
The ScrapingBee node is executed when triggered by a preceding node in the workflow, such as an HTTP trigger or a standard scheduled cron node. It receives input data (e.g., URLs) and processes the scraping request as an action node, initiating the data retrieval.
What is the typical data output format provided by the ScrapingBee node?
The node returns the scraped content as structured JSON data, usually including the raw HTML or the extracted text/data, which can then be seamlessly passed to subsequent nodes for further processing, analysis, or Integrations.