n8n Landing Page Swipe File: Snapshot Site to S3 + Sheets

Turn landing pages into a swipe-file snapshot—automatically (Snapshot Site → S3 + Google Sheets, with Slack alerts)

This n8n workflow accepts landing page URLs via webhook, uses Snapshot Site to generate a full-page capture and extract key copy/metadata, then archives the screenshot to Amazon S3 and appends a ready-to-use swipe-file record into your Google Sheets. If the page can’t be captured (errors, blank pages, or CAPTCHA/bot-gates), it sends a Slack alert instead.

What this workflow does

• Receives a POST webhook with a landing page url plus optional source and notes.
• Analyzes each page with Snapshot Site to produce a full-page capture and extract structured elements such as copy structure, metadata, topics, a summary, and quality signals/readability.
• Handles capture failures: if Snapshot Site returns an error, it posts a Slack message for the submitted URL.
• Detects unreadable pages: checks the analysis for blank-page or CAPTCHA/bot-gate indicators and notifies Slack instead of filing.
• Creates a swipe-file entry (headline/subheads, metadata, summary, topics, readability score) and generates a dated S3 object key and archive URL.
• Downloads and uploads the capture image to Amazon S3, then appends the completed record as a new row in the Google Sheets “Swipe File” tab.

Use cases

• Build a continuously updated SaaS landing page swipe file for competitive research.
• Archive and catalog screenshots for marketing copy audits with an auditable storage link (S3 URL).
• Monitor capture reliability at scale—use Slack alerts when pages are blocked or unreadable.

Technical details

• n8n nodes/services used: Webhook, if, set, code, Snapshot Site (via n8n-nodes-snapshot-site community node), AWS S3, Slack, and Google Sheets.
• Requires: Snapshot Site API credentials, AWS S3 bucket + base URL/key prefix in the code step, and Google Sheets OAuth + the target spreadsheet where the “Swipe File” sheet headers match the appended fields.