How to snapshot your HubSpot pipeline weekly and track changes in Google Sheets

Why snapshot your pipeline?

HubSpot shows you the current state of your pipeline, but not how it looked last week or last month. Without historical snapshots, you can't answer critical questions like "Are we building pipeline fast enough?" or "How much pipeline slipped this quarter?"

Most RevOps teams spend 30-45 minutes every Monday morning manually pulling pipeline numbers into a spreadsheet. That's 25+ hours per year on copy-paste work that should take zero human effort. Worse, manual snapshots are inconsistent — different people pull different numbers, and someone always forgets a week, leaving gaps in the data.

A weekly snapshot to Google Sheets gives you:

• Week-over-week trend data for pipeline value and deal count
• Historical stage distribution for conversion analysis
• A simple chart showing whether pipeline is growing or shrinking
• A consistent, gap-free record that doesn't depend on anyone remembering to pull numbers

How it works

Every approach in this guide follows the same pattern:

1. Trigger on a weekly schedule (usually Monday morning)
2. Fetch pipeline stages from HubSpot to map stage IDs to human-readable labels
3. Search for all active deals in the pipeline, paginating through results
4. Aggregate metrics — total pipeline value, deal count, and per-stage breakdowns (count and value)
5. Append a row to Google Sheets with the date and all metrics

The result is a growing spreadsheet where each row is one week's snapshot, making it trivial to build trend charts and spot week-over-week changes.

What you'll need

Which approach should I use?

• n8n (recommended) if you want the most straightforward setup. The Code node handles aggregation in a few lines, and the Google Sheets node appends the row natively. Free self-hosted or $24/mo cloud.
• Zapier if your team already uses Zapier. Requires the Professional plan ($30/mo) for Code by Zapier and Webhooks. Works well for pipelines under 100 deals.
• Make if your team already uses Make. The visual aggregator modules handle per-stage breakdowns without code, though many stages mean many modules.
• Code + Cron if you want zero ongoing cost and full control. The script runs via cron or GitHub Actions. Best for teams with a developer who can maintain it.
• Claude Code if you want on-demand snapshots — before a board meeting, after a big push, or alongside your regular schedule. The agent adapts to ad hoc requests like "snapshot just the Enterprise pipeline."

Select an approach below to see the full step-by-step guide.