← All flows

⚡ HTML Heading Outline Export

On a weekly schedule, downloads one configured HTML page and exports its H1–H6 outline as a Markdown file for IA and docs review — a fresh snapshot each run, not a diff.

Site auditsBeginner · Copy and use. No edits needed.FreePublished Nov 4, 2026
Free

n8n workflow JSON.

Download JSON

What it does

Docs and site editors often want a clean heading outline of a help center article or landing page without opening DevTools. Point this workflow at one HTTPS HTML URL; each run writes a fresh Markdown outline of H1–H6 text in document order.

This is a snapshot export, not a comparison against last week. It does not read XML sitemaps, does not ping uptime, does not parse RSS, does not watch campaign spreadsheets, and does not store prior runs in static data.

Steps after import

  1. Schedule Trigger — Wednesdays 10:00 in the n8n timezone.
  2. Page config — set page_url to the HTML document you want outlined.
  3. HTTP Request — downloads the page as text.
  4. Code — walks heading tags in order, records level + visible text (tags stripped), skips empty headings, and builds a nested Markdown outline.
  5. Convert to File — attaches heading-outline.md to the execution.

Catalog credentials stay empty. Add delivery nodes yourself if needed.

Practical notes

  • Works best on relatively clean HTML. Heavy client-rendered apps may return a shell without headings.
  • Duplicate heading text is kept; the outline preserves order rather than uniquing.
  • Script and style tag contents are stripped before heading extraction.
  • One page per workflow; duplicate the workflow for more URLs.

Required nodes

  • Schedule Trigger
  • Edit Fields (Set)
  • HTTP Request
  • Code
  • Convert to File

Credentials

None. This flow runs without any credentials.

Our JSON never contains credentials, credential IDs or webhook URLs. You connect your own after import.

Import steps

  1. Download the JSON file above.
  2. In n8n, open a new workflow, then open the Workflow menu in the canvas header and choose Import from File…. You can also paste the JSON straight into the editor.
  3. Check the settings in each node (URLs, schedules, recipients) and change them to your own.
  4. Click Execute workflow once to test, then click Publish so schedules and webhooks run in production. Full guide.

Test log

No recorded test runs yet. We only list a tool under “Tested on” after a real run passes, with the date and model.