n8n web scraping workflows break when target sites change their HTML. The HTTP Request node fetches raw HTML, the HTML Extract node parses it with CSS selectors, and one class name change breaks the entire flow. Replacing the scraping nodes with a search API call returns structured JSON that never changes format regardless of how the target site updates its frontend.
Why n8n Scraping Breaks
n8n's built-in scraping approach chains HTTP Request, HTML Extract, and Function nodes. Each CSS selector is hardcoded to the site's current DOM structure. Google changes its SERP layout every few weeks. Amazon rotates product page templates. YouTube updates its video card format. Each change requires manual selector updates, and the workflow silently returns empty data until someone notices.
The Search API Replacement
// n8n Function node — replaces HTTP Request + HTML Extract chain
const API = "https://api.scavio.dev";
const API_KEY = $env.SCAVIO_API_KEY;
// One path per platform; each returns its own list field
const PLATFORMS = {
google: { path: "/api/v2/google", body: q => ({ query: q }), list: d => d.organic_results },
youtube: { path: "/api/v1/youtube/search", body: q => ({ search: q }), list: d => d.data.results },
amazon: { path: "/api/v1/amazon/search", body: q => ({ query: q }), list: d => d.data.products },
walmart: { path: "/api/v1/walmart/search", body: q => ({ query: q }), list: d => d.data.products },
reddit: { path: "/api/v1/reddit/search", body: q => ({ query: q }), list: d => d.data.results },
};
const platform = PLATFORMS[$input.first().json.platform || "google"];
const response = await fetch(API + platform.path, {
method: "POST",
headers: {
Authorization: `Bearer ${API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify(platform.body($input.first().json.searchQuery)),
});
const data = await response.json();
// Structured JSON — no CSS selectors, no DOM parsing
return (platform.list(data) || []).slice(0, 10).map((r, i) => ({
json: {
title: r.title,
url: r.link || r.url,
snippet: r.snippet || "",
position: r.position || i + 1,
}
}));Multi-Platform in One Node
One API key and one request shape cover Google, YouTube, Amazon, Walmart, and Reddit. Each platform has its own path, so the lookup table above is all the routing you need. An n8n workflow that previously needed 5 different scraping chains (each with custom selectors) now uses one Function node with a platform variable. When YouTube changes its layout, your workflow keeps working.
Cost Comparison
n8n Cloud starts at $24/month for 2,500 executions. Each Scavio search is 1 credit, so 500 daily searches (about 15,000 a month) fit the $100/month plan's 28,000 credits. Self-hosted n8n is free but requires server maintenance. For most automation workflows running 50-200 searches per day (1,500-6,000 a month), the $30/month plan's 7,000 credits cover the search side, plus whatever n8n hosting costs. This replaces both the scraping infrastructure and the maintenance time spent fixing broken selectors.
When Scraping Still Wins
If you need data from pages that are not search results (internal dashboards, authenticated pages, specific product detail pages), direct scraping is still necessary. Search APIs return search result data, not arbitrary page content. For page extraction, tools like Firecrawl ($16/month for 3,000 credits) or Apify ($49/month) are better suited.
Decide Whether You Have a UI Problem or a Data Problem
Before choosing any tool, separate the two things people mean by "browser automation" in n8n, because they have different answers and the wrong pick is expensive.
UI automation means the workflow has to act on a page: log in, click through a multi-step flow, fill and submit a form, dismiss a modal. There is no API substitute. You need a real browser, and Browserless or a self-hosted Playwright container behind an HTTP Request node is the standard shape.
Data extraction means you only want values off a page, and the browser is incidental. Here a browser is the expensive answer. You inherit captcha handling, fingerprint and stealth patches, proxy rotation, and a permanent maintenance tax, all to obtain data that a structured endpoint returns as JSON.
The tell is simple: if you could get the same values from a JSON response, you have a data problem and you should not be running a browser at all.
The common n8n failure is building a full browser-automation stack, complete with captcha solving and residential proxies, for what was fundamentally a data pull, then wondering why the workflow breaks every week. Each of those layers is a component that can fail independently, and they all fail on someone else's schedule.
Rule of thumb for the mixed case: use a structured API for everything it covers, and reserve the browser for the specific steps that genuinely require clicking. Most workflows that start out "we need browser automation" end up with one browser node and five API calls.