n8n Workflow: Weekly Web Page Archive to One PDF with PDFMint

Automatically archive a week of web pages into one dated PDF every Monday

This n8n workflow renders a predefined list of URLs to PDFs using PDFMint and then merges the successful results into a single, week-based archive PDF—plus a short summary of what was archived.

What this workflow does

• Runs on a schedule: triggers every Monday at 07:00 UTC.
• Loads the URL list: pulls the pages to archive and stops if the list is empty.
• Checks PDFMint credits: verifies there are enough credits for one PDF per page plus one merge operation.
• Builds a week-based archive filename: generates a dated, week-based archive name and file name.
• Renders each URL to its own PDF: uses PDFMint to convert each page.
• Ignores failed renders: pages that fail to render are dropped so one broken URL won’t fail the entire run.
• Merges into one archive PDF: if two or more PDFs succeeded, it merges them into a single dated PDF; if only one succeeded, it keeps that single PDF as the archive.
• Outputs a summary: returns a short string describing how many pages were archived and the resulting file name.

Use cases

• Maintain a weekly audit trail of important landing pages, policy pages, or release notes.
• Archive changing competitor or documentation pages on a consistent cadence.
• Run automated compliance-style snapshots without manually exporting PDFs.
• SaaS operations teams collect weekly “state of the web” records for reference and review.

Technical details

• Schedule trigger: runs every Monday at 07:00 UTC.
• PDFMint community node: renders pages and performs the PDF merge.
• Logic & flow control nodes: if, set, code, filter, split out, and sticky note.
• Setup: self-host n8n, configure the PDFMint node with a PDFMint API key credential, then update the “Set the pages to archive” step (URLs and optional base archive name).

Disclosure: I build and run PDFMint, the service this template calls. This is a self-submission.