Archive a Daily Full-Page Screenshot to Drive
Keep a visual history of any page — your homepage, a competitor's landing page, a status board — without lifting a finger. Schedule by Zapier fires on your cadence, the native Rendex Capture Screenshot action renders the page full-page, and a Google Drive or Dropbox step files it under a dated name. No code, no browser to babysit, free tier.
Last updated 2026-07-21
The Problem
Plenty of pages are worth keeping a record of over time — how your marketing site looked before a redesign, a competitor's evolving pricing page, a compliance page you need dated snapshots of. But nobody remembers to screenshot the same URL every day, and doing it by hand is exactly the kind of repetitive chore that gets dropped after a week. Rolling your own scheduled capture means a cron job, a headless browser, and somewhere to store the files — infrastructure for what should be a set-and-forget task.
The Solution
Zapier's Schedule by Zapier trigger handles the cadence, and the native Rendex Capture Screenshot action handles the render — no cron, no browser, no code. Point the action at a URL, turn on Full Page, and Rendex returns the image as a file; the next step files it in Google Drive or Dropbox under a filename stamped with the date. Set it once and it quietly builds a dated visual archive of the page. It runs on the free 100 renders a month, which comfortably covers a daily capture of a handful of pages.
How the Workflow Runs
On a schedule
Schedule by Zapier fires the Zap on your cadence — daily, weekly, or monthly — with no page or trigger app required.
Rendex — Capture Screenshot
The native action renders the target URL full-page in a real browser and returns the image as a file — no code, no browser to run yourself.
Archive with a date
A Google Drive or Dropbox step files the image under a dated filename, building a browsable visual history of the page over time.
Input → Rendered Output
Rendered by Rendex
What You Need
- A Rendex API key — the free tier includes 100 renders/month with no card required.
- A Zapier account with the Rendex app connected (search "Rendex", add your key once).
- A Schedule by Zapier trigger set to your cadence (daily, weekly, or monthly).
- A destination step: Google Drive or Dropbox to file the dated image.
What This Recipe Uses
Set-and-forget schedule
Schedule by Zapier fires the Zap daily, weekly, or monthly with no trigger app to wire — the cadence is the trigger.
Full-page, real-browser render
Full Page captures the entire scrollable page in a real browser — fonts, lazy-loaded images, and all — so each snapshot is the whole page, not a viewport crop.
Dated archive in Drive
Name the upload from the run date so the destination folder becomes a browsable timeline of the page rather than a pile of overwritten files.
One credit per capture
Each scheduled screenshot is a single Rendex render, so a daily capture of a few pages sits well inside the free 100/month — no infrastructure and no per-run browser cost.
Build It
# Zapier — action config (no code)
Trigger: Schedule by Zapier — Every Day at 6am
Action: Rendex — Capture Screenshot
Source Type: URL
URL: https://yoursite.com
Output Format: PNG
Full Page: true
Next: Google Drive — Upload File
Folder: /Archive/yoursite
File: {{ Rendex: File }}
Filename: yoursite-{{ zap_meta_human_now }}.png# On each scheduled run the action submits this async, polls the job,
# and returns the finished image as a file for the Drive step.
curl -X POST https://api.rendex.dev/v1/screenshot \
-H "Authorization: Bearer rdx_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://yoursite.com",
"format": "png",
"fullPage": true,
"async": true
}'
# => { "data": { "jobId": "job_..." } } → poll GET /v1/jobs/{jobId} until completed.100 free API calls/month — no credit card required. Get your API key and start building.
Reach for this when you want a record of how a page changes over time, not an alert the moment it does. A daily or weekly capture of your own site catches regressions and documents a redesign; the same on a competitor's landing or pricing page builds a research archive you can scrub through later; a dated snapshot of a policy or status page is a lightweight compliance trail. The whole thing is set-and-forget because Schedule by Zapier owns the timing and the Rendex action owns the render — you never run a cron or a browser. Full Page is the setting that matters: you're archiving the whole page, not a viewport crop. The one detail worth getting right is the filename — stamp it with the date (and the page name if you're archiving several) so the Drive folder reads as a timeline instead of a stack of overwrites. If instead you want to be pinged only when the page actually changes, that's Rendex Watch's job, not a scheduled capture — pair the two if you want both a record and an alert. It runs on the free tier for a modest set of pages.