n8n: Transition Guide from v1 to v2

​

Transition from v1 to v2

If you’re on n8n-nodes-scrapegraphai@0.x, this is your migration checkpoint. Before anything else, update the community node in n8n at Settings → Community Nodes → n8n-nodes-scrapegraphai → Update to 1.0.2 (or later). Your existing SGAI-APIKEY works as-is — no re-auth needed.

​

Method-by-method migration

Use this table to map old resources to the new ones. Details and field changes follow below. The resource picker at a glance — before (v1, 6 resources): After (v2, 7 resources):

​

Step-by-step rebuild

​

1. Markdownify → Scrape

Before: A dedicated Markdownify resource that always returned markdown. After: Use the Scrape resource with one Markdown format entry. Same job, more flexible — you can mix in HTML, Links, Summary, or Branding in the same call.

​

2. SmartScraper → Extract

Before (v1): Website URL + User Prompt, plus optional flat fields like Render Heavy JS and Number of Scrolls. After (v2): URL + Prompt, optional Schema (JSON) behind a Use JSON Schema toggle. All fetch knobs move into a single Fetch Config collection shared across every resource. Fetch Config also adds knobs that didn’t exist in v1: Stealth, Wait (Ms), Timeout (Ms), Country, Headers (JSON), Cookies (JSON).

​

3. SearchScraper → Search

Before: User Prompt + a few flat options. After: Query (the search string) plus optional Rollup Prompt for AI extraction across all fetched results, optional Schema (JSON) behind a toggle, and new fields like Time Range and Location (Country Code).

​

4. SmartCrawler → Crawl jobs

Before: A single synchronous SmartCrawler operation. After: Crawl is explicitly async. Start the job, then poll. Five operations are exposed: Start, Get Status, Stop, Resume, Delete. A typical chain in n8n:

1. Crawl → Start — returns a cronId
2. Wait node (~60s)
3. Crawl → Get Status — returns the pages[] array
4. (Optional) Split Out + History → Get — fetch full content per crawled page

See the full walkthrough on the n8n integration page.

​

5. Output shape

Downstream nodes (Set, IF, HTTP Request) that reference v1 paths like $json.result.markdown will break — v2 returns a different shape. The new node ships an Output parameter on every content-producing operation (Scrape, Extract, Search) with three modes: Simplified, Raw, Selected Fields. Pick Simplified when migrating — it’s the closest match to v1.

​

What else changed in v2

• New Fetch Config knobs that didn’t exist in v1: Stealth, Wait (Ms), Timeout (Ms), Country, Headers (JSON), Cookies (JSON)
• New resources: Monitor (cron + diff + webhook), History (look up past results by scrapeRefId), Credit (check usage)
• Async crawl model with five lifecycle ops instead of one synchronous call
• AI-Agent friendly — every content-producing op exposes Simplified / Raw / Selected Fields output modes
• Cleaner credentials test — n8n hits GET /api/credits to verify keys

​

Recommended path

1. Update the community node: Settings → Community Nodes → n8n-nodes-scrapegraphai → Update to 1.0.2 (or later)
2. Open each affected workflow — v1 ScrapeGraphAI nodes will surface as deprecated or fail to execute
3. Drop in fresh ScrapeGraphAI nodes and pick the matching v2 resource from the migration table
4. Re-map fields per the step-by-step rebuild above
5. Set Output to Simplified (closest to v1)
6. Test the node, fix downstream expressions, delete the v1 node

​

FAQ

• Will my workflows keep running until I touch them? Yes — until the next execution opens the v1 node, which then fails against the deprecated v1 API.
• Can I run v1 and v2 side-by-side? No — same package, version-pinned.
• Self-hosted vs n8n Cloud? Self-hosted: bump the version in Community Nodes. n8n Cloud doesn’t yet allow community nodes.
• I used Agentic Scraper — what now? Use Extract with Fetch Config → Mode = JS plus Stealth and Wait (Ms).

​

Related guides