n8n: Document Web Fetch and remove Scrape Single URL #3023

Parent epic: apify/integrations-team#114 · Contract: apify/integrations-team#115

Why?

sources/platform/integrations/workflows-and-notifications/n8n/index.md still documents the old action: line 164 reads "Scrape Single URL: Runs a scraper for a specified website and returns its content", with no mention of Web Fetch.

apify/n8n-nodes-apify#49 shipped in v0.8.0 (2026-09-22): the node has a Web Fetch operation under the Actors resource, and Scrape Single URL is now displayed as (Deprecated) Scrape Single URL.

This is the n8n line item of #2879, split out because the n8n implementation has landed while the other platforms have not. Removal of the old action is folded into this task per apify/integrations-team#117.

What?

Update sources/platform/integrations/workflows-and-notifications/n8n/index.md:

• Add Web Fetch to the ### Actors list under "Available Operations" (~L164)
• Remove the Scrape Single URL bullet and any remaining references to it on the page
• Document the Web Fetch inputs: url, formats, headers
• Do not document crawlerType — it does not exist on this operation
• Note that formats is multi-select and supersedes the old single-select outputFormat
• Refresh any screenshot where the operation list or field set is visible

⚠️ Note for the implementer: the operation is removed from the docs, but it is not yet removed from the node — v0.8.0 still lists (Deprecated) Scrape Single URL in the n8n UI with the description "This operation is deprecated and will be removed in a future release. Use the Web Fetch operation instead." Users on an existing workflow will still see it. If that gap is a problem, raise it on the parent before merging.

How?

The shipped field set, from nodes/Apify/resources/actors/web-fetch/properties.ts:

formats options as they appear in the UI: Markdown (clean markdown, best for AI agents and LLMs), HTML (raw HTML, best for programmatic processing), Text (plain text, no formatting), Links (deduplicated list of links found on the page, useful for crawl queues), Raw (original raw body, base64-encoded for binary content). Only the selected formats are returned — that is the point of the change.

Output is Web Fetch's envelope: the requested format keys plus fetch (loadedUrl, httpStatusCode, contentType, …) and metadata (title, description, canonicalUrl, openGraph, jsonLd, …).

Background on the Actor: apify/web-fetch.

apify/n8n-nodes-apify-content-crawler is a deliberate Website Content Crawler node and is out of scope.