n8n
Web search and content collection for self-hosted n8n.
Bring web content into Zapier with Geonode’s app. Extract pages, discover URLs, crawl sites and run batches, then continue your Zap when a job completes. Pass results to your AI or business-app steps for research, summaries and record updates.
Connect web content to a Zap with Geonode’s private app: four actions, a job lookup and a completion trigger. Request a private invitation before configuring your first Zap.
Extract URL retrieves a page. Batch Scrape URLs processes a list. Crawl Site follows links within depth and page limits. Map URLs discovers links under a site.
Find Job by ID retrieves background status/results. Job Completed is a REST-hook trigger for extraction, batch or crawl completion. Keep the submitted job ID and wait for a terminal result before consuming content.
Use a form or spreadsheet trigger that provides a website URL, extract Markdown, then pass it to a separate AI step. Save the summary with its source URL in your destination app. Each downstream app requires its own connection.
Structured product fields and change detection need separate parsing and comparison steps. These are workflow ideas, not preconfigured or live-tested Zaps.
There is no verified public marketplace installation link. Source definitions have been reviewed, but deployed account access and live Zap execution were not tested.
This app provides native Zapier actions. For a compatible AI assistant use Geonode’s separate MCP server; web search is not an action in this Zapier source.
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.
Retrieve a job by its ID and continue your Zap when the job completes.
Take a website URL from a form or CRM trigger, extract its content, and pass it to a later Zap step for processing.
Start a bounded crawl and use Job Completed to continue processing when the background work finishes.
Send extracted Markdown to a separate AI step and store its summary alongside the source URL.
Private app access
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.
Collect web content and continue your Zap when jobs finish.