Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
This template implements a recursive web crawler inside n8n. Starting from a given URL, it crawls linked pages up to a maximum depth (default: 3), extracts text and links, and returns the collected...
n8n-nodes-base.stickynote, n8n-nodes-base.webhook, n8n-nodes-base.splitinbatches, n8n-nodes-base.if, n8n-nodes-base.html, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.merge
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Le Nguyen.
Original n8n.io sourceThis template implements a recursive web crawler inside n8n. Starting from a given URL, it crawls linked pages up to a maximum depth (default: 3), extracts text and links, and returns the collected content via webhook.
Webhook Trigger
Accepts a JSON body with a url field.
Example payload:
{ "url": "https://example.com" }
Initialization
url, domain, maxDepth = 3, and depth = 0. pending, visited, queued, pages).Recursive Crawling
Depth Control & Queue
maxDepth to prevent infinite loops Data Collection
url, depth, content) into pages[] pending = 0, combines resultsOutput
combinedContent (all pages concatenated)pages[] (array of individual results)Import Template
Load from n8n Community Templates.
Configure Webhook
Run a Test
Send a POST with JSON:
curl -X POST https://<your-n8n>/webhook/<id>
-H "Content-Type: application/json"
-d '{"url": "https://example.com"}'
View Response
The crawler returns a JSON object containing combinedContent and pages[].
maxDepth
Default: 3. Adjust in the Init Crawl Params (Set) node.
Timeouts
HTTP Request node timeout is 5 seconds per request; increase if needed.
Filtering Rules
www treated as same-site) mailto:, tel:, javascript: ~10 minutes (import → set webhook → test request)
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Domain-specific web content crawler with depth control & text extraction |
|---|---|
| Complexity | advanced |
| Nodes | 18 |
| Categories | Document Extraction |
| Author | Le Nguyen |
| Published | 23 Sept 2025 |
Use the JSON export at /data/workflows/8852/8852.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
This template implements a recursive web crawler inside n8n. Starting from a given URL, it crawls linked pages up to a maximum depth (default: 3), extracts text and links, and returns the collected...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction use case.