Fetch website content with HTTP request and Apify Web Fetch
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 7 nodes and runs manually, when you click “Execute workflow”. It uses only n8n's built-in nodes.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Set Input Parameters (Edit Fields (Set)): sets 2 fields: Url List, Apify Token
- Fetch URL with HTTP request (HTTP Request): calls an HTTP API
- Fetch URL with Apify (HTTP Request): calls an HTTP API
- Prepare HTTP Result (Edit Fields (Set)): sets 1 field: Result
- Prepare Apify Result (Edit Fields (Set)): sets 1 field: Result
- Aggregate: combines items into one
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (4)
- Manual Trigger
n8n-nodes-base.manualTrigger - Aggregate
n8n-nodes-base.aggregate - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest
From the author
Quick overview This workflow fetches web page content by trying a direct HTTP request first and falling back to Apify Web Fetch when needed, then normalizes the outputs and aggregates the results into a single dataset. How it works 1. Starts when you run the…