Make
Collect web content for Make.com agents and scenarios.
Bring web data into self-hosted n8n agents and workflows with Geonode’s community node. Extract pages, crawl sites, discover URLs, search the web and run batches. Use extraction and crawl completion triggers to continue your own AI processing, research or record-update steps.
Add extraction to a self-hosted n8n workflow with the Scraper API node, or start a workflow when an extraction or crawl finishes with Scraper API Trigger.
A successful node execution returns the extracted content. Connect that output to the next step in your workflow after checking it with a single URL.
For asynchronous extraction and batches, enable Wait for Completion where offered. For a crawl, start the crawl, then use Get Status with Wait for Completion enabled.
For event-driven workflows, use Scraper API Trigger with Extract Completed or Crawl Completed. Keep Verify Signature on. Activating the workflow registers its webhook URL; deactivating it removes that registration.
This is a self-hosted community node, not an n8n-verified Cloud integration. Update it through Settings → Community Nodes.
The node retries HTTP 429 and 5xx responses with increasing pauses, up to five total attempts, and respects Retry-After. Other errors stop the node and display the API message.
Get the full setup guide, authentication details and technical reference.
Extract page content as Markdown or HTML, with optional JavaScript rendering.
Run batch extraction and bounded website crawls as background jobs.
Discover website URLs before choosing which pages to extract.
Run web search jobs and inspect usage statistics.
Start follow-up workflows when extraction or crawling completes.
Extract source pages as Markdown, then connect your own chunking, embedding and storage nodes.
Start a bounded crawl and process the returned content after the job completes.
Use Scraper API Trigger to start follow-up processing for extraction or crawl completion.
Self-hosted n8n · Node.js 20.15+
Keep API keys on the server or in your client’s credential store. Usage is charged to your Geonode plan.
Check the key in the Geonode dashboard and send it using X-Api-Key. Keep it out of browser bundles, URLs and version control.
Respect the Retry-After response and your plan’s concurrency limits. Avoid automatically retrying a job submission when its outcome is unknown.
Web search and content collection for self-hosted n8n.