Find broken links and redirect chains from sitemaps with Slack reports
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 22 nodes and runs on a schedule (every week at 07:00) (plus 1 other trigger). Along the way it connects Slack.
How it runs
Trigger: On a schedule (every week at 07:00) (plus 1 other trigger).
- Settings (Edit Fields (Set)): sets 6 fields: sitemap, url_must_contain, max_pages…
- Fetch The Sitemap (HTTP Request): calls an HTTP API
- Read The Sitemap (Code): runs custom JavaScript code
- Is It An Index Of Sitemaps? (If): checks a condition and branches into true / false
- Fetch Each Child Sitemap (HTTP Request): calls an HTTP API
- Gather Every Page URL (Merge): merges the data from its input branches
- Read The Child Sitemaps (Code): runs custom JavaScript code
- Pick The Pages To Crawl (Code): runs custom JavaScript code
- Fetch Each Page (HTTP Request): calls an HTTP API
- Collect Every Link (Code): runs custom JavaScript code
…plus 9 more steps. See the full node list below.
Services it uses
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 (10)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Merge
n8n-nodes-base.merge - Data table
n8n-nodes-base.dataTable - Slack
n8n-nodes-base.slack - No Operation, do nothing
n8n-nodes-base.noOp
From the author
Quick overview This workflow runs weekly (or on demand) to crawl your sitemap, extract and deduplicate links from your pages, check each link’s HTTP response without following redirects, and post a summary of new broken links and redirect chains to Slack…