n8n

Overview

n8n is a workflow automation platform — you build workflows by connecting nodes on a canvas, with the option to drop into JavaScript/Python code nodes whenever you need custom logic. The official ScrapingBee node for n8n lets you call any ScrapingBee API endpoint as a step in a workflow: scrape pages, extract structured data, search Google / Amazon / Walmart / YouTube, or send prompts to ChatGPT.

Prerequisites

You need:

• An n8n account — n8n Cloud, or a self-hosted instance
• A ScrapingBee account and an API key from your dashboard

Setup

Connect ScrapingBee to n8n once, then reuse the connection across all your workflows.

1. Sign in to n8n. From the What do you want to build? screen, click Build a workflow to open the editor.
2. On the empty canvas, click Add first step... (or + in the top right) to open the Nodes panel, then search for ScrapingBee and select it.
3. On the Node details panel, click Install node — the ScrapingBee node isn't bundled with n8n by default, so it needs a one-time install before you can configure it.
4. Once installed, pick an action (e.g. Scrape using HTML API). The node opens with its Resource (e.g. HTML API) and Operation (e.g. GET) already set, and a Credential field showing "No credentials yet."
5. Click Set up credential next to the Credential field. n8n opens a ScrapingBee account dialog.
6. Paste your ScrapingBee API key into the API Key field, leave Allowed HTTP Request Domains as All, and click Save.
7. Fill in the remaining parameters (e.g. URL for Scrape using HTML API), then click Execute step to test it, or activate the workflow to run it on its trigger.

The credential is now saved in your n8n instance and available to every ScrapingBee node in any workflow — you won't need to re-enter the API key next time.

Available actions

The ScrapingBee node exposes 12 actions, grouped below by capability. Each wraps a ScrapingBee endpoint and appears in n8n under the label shown in the Action column. Follow the Underlying API link on any row for the full parameter reference.

ScrapingBee has no triggers — it only exposes actions, so it can't start a workflow on its own. Pair it with a trigger node like On a Schedule or On a Webhook call (n8n suggests both directly in the node picker).

Scraping

Search and AI

E-commerce

YouTube

There's also a Get usage data action that returns your current credit balance, max concurrency, and plan limits — useful for adding a usage check to a workflow or alerting when credits run low. It maps to the ScrapingBee usage endpoint.

Example workflows

Two starting points showing how the ScrapingBee node combines with other n8n nodes:

Price-drop alerts

• Trigger the workflow On a Schedule (e.g. every morning).
• Run Get product information using AMAZON PRODUCT API (or the Walmart equivalent) with your tracked ASIN/product ID to pull the current price.
• Add an IF node that only continues if the price is below your target.
• Send yourself a Slack message, email, or Telegram alert.

Sync scraped data to Google Sheets

• Trigger on a schedule or webhook, ideally with rows read from a Google Sheets node (e.g. a list of URLs).
• Run Scrape using HTML API against each URL.
• Map the response fields into a second Google Sheets node to append or update a row.
• New rows added to the source sheet get enriched automatically on the next run — no code, no cron.

Credits and limits

Each ScrapingBee action consumes ScrapingBee credits at the same rate as the underlying API call — n8n adds no surcharge. Get SERP data using GOOGLE SEARCH API costs whatever the Google API costs; Scrape using HTML API with premium_proxy: true costs whatever the HTML API costs with that flag. See credit costs for the exact per-endpoint pricing.

n8n Cloud plans are priced by workflow executions — each workflow run counts as one execution regardless of how many nodes it contains. Self-hosted n8n has no per-execution charge from n8n at all; you only pay for the infrastructure you run it on.

The HTML API actions (Scrape, Send POST request, Send PUT request) accept premium_proxy, stealth_proxy, custom_google, and country_code parameters for geo-targeted and anti-bot scraping. Start without either proxy flag. If the site blocks you, retry with premium_proxy: true. If you're still blocked, escalate to stealth_proxy: true. The ladder goes cheap → expensive, so only step up when you need to.

Troubleshooting

Credential fails to save

n8n couldn't validate the API key against ScrapingBee. Copy the key fresh from app.scrapingbee.com/account/manage/api_key — make sure there's no surrounding whitespace — and paste it again.

A scrape returns empty or blocked content

The target site is blocking ScrapingBee's default scraper. For the HTML API actions, enable premium_proxy: true first; if still blocked, escalate to stealth_proxy: true. Each step up costs more credits — see credit costs.

Resources

• ScrapingBee integrations on n8n — marketplace listing and available operations
• ScrapingBee dashboard — manage your API key, view usage, upgrade your plan
• Knowledge Base — searchable troubleshooting articles