Zapier Automation: Assemble Your QBR and Partner Performance Report Automatically

What This Builds

Every quarter, someone has to pull each partner's pipeline, revenue, and activity numbers out of the CRM or PRM and turn them into a QBR deck. This automation does the pulling and the first-draft formatting for you. A scheduled Zap pulls the last 90 days of partner-sourced pipeline and revenue data, drops it into a Google Slides or Docs template, and asks Claude to write a first-pass summary paragraph. You still add the narrative judgment. The blank-page and copy-paste work goes away.

Prerequisites

• Professional Zapier plan ($29.99/month): multi-step Zaps with a formatter step need a paid tier
• Pro Claude subscription ($20/month) for API access through Zapier's Claude integration, or a Claude account you paste into manually if you skip the API step
• A Google Workspace account (included in most business plans) with a QBR template already built in Slides or Docs
• Whatever your company already pays for CRM or PRM access. Check with your RevOps or IT team for the current plan tier before you build the report pull, since custom report fields sometimes require an upgraded seat
• Total new ongoing cost for this build: the Zapier and Claude line items above, on top of tools you already pay for

The Concept

Think of this Zap as a research assistant who shows up every Friday before your QBR week, pulls the same numbers you'd pull yourself, and leaves a rough draft on your desk. It does not replace the QBR conversation. It replaces the hour you spend exporting spreadsheets and retyping them into slide boxes.

Build It Step by Step

Part 1: Set the trigger

In Zapier, create a new Zap and choose Schedule by Zapier as the trigger. Set it to run monthly if you review pipeline that often, or a few days before each quarter's QBR window if you only need the pull four times a year. Name the Zap something specific, like "QBR data pull, partner accounts," so it is identifiable later in your Zap history.

Part 2: Pull the partner data

Add an action step for your CRM or PRM (Salesforce, HubSpot, or your PRM's Zapier integration, whichever holds partner pipeline records). Use a "Find Records" or "Search" action filtered to partner-sourced opportunities, with a date filter for the last 90 days. Map the fields you actually report on: partner name, pipeline value, closed-won revenue, deal count, and stage.

Part 3: Turn the numbers into a draft narrative

Add a Claude step (Zapier's Claude integration, or a webhook to the Claude API if your plan does not include the native app). Feed it the pulled records with a prompt like:

You are drafting the data section of a quarterly partner review. Here is
this partner's pipeline and revenue data for the last 90 days: {{data}}.
Write two short paragraphs: one summarizing pipeline movement, one
summarizing revenue against the same period last quarter if available.
Flag anything that looks like a meaningful change, up or down. Do not
invent numbers that are not in the data. Write plainly, no marketing tone.

Part 4: Drop it into the template

Add a Google Slides or Google Docs action that duplicates your QBR template and inserts the pulled numbers and the Claude-drafted paragraphs into the marked placeholder fields. Name the output file with the partner name and quarter so it is easy to find.

Part 5: Route it for review, not for sending

Point the finished file at a folder only you and your manager can see, not a shared partner-facing drive. Add a final Zapier step that sends you a Slack or email notification that the draft is ready. Nobody outside the company sees this draft until you have reviewed and edited it by hand.

Real Example: Meridian Data Partners, Q3 QBR

Setup: Zap scheduled to run the second Friday of each quarter-end month, pulling from Salesforce opportunities tagged "Partner Source: Meridian Data Partners."

Input: 14 partner-sourced opportunities, $340K in pipeline, two closed-won deals worth $58K combined over the quarter.

Output: A duplicated Google Slides deck with the numbers already in the data slide, plus a Claude-drafted paragraph noting pipeline grew 22% quarter over quarter and flagging that one large opportunity had sat in the same stage for 45 days. You read the draft, confirm the stalled deal against what you actually know about that account, and rewrite the flag into a specific talking point before the QBR call.

Time saved: Cuts data assembly and first-draft narrative from roughly 2-4 hours down to 30-45 minutes of review and rewriting per partner.

What to Do When It Breaks

• The Zap runs but the report comes back empty → your CRM report filter probably changed, or a field got renamed during a CRM update. Open the Zap's task history, check the raw data returned by the Find Records step, and re-map any renamed fields.
• Claude's summary states a number that is not in the source data → tighten the prompt to explicitly forbid inference beyond the provided fields, and always treat the narrative paragraph as a draft to fact-check against the raw numbers, never as the number of record.
• The scheduled run silently stops firing → this is the failure you will not notice until you are missing a draft the week of your QBR. Set a calendar reminder for the day after each scheduled run to confirm the output file actually landed in the folder, and check Zapier's own Zap history page monthly for any run marked as an error, since a failed CRM authentication or an expired API key will quietly stop the Zap without any other warning.
• The Google Slides template placeholders shift or get deleted → the insert step will either fail or drop data into the wrong slide. Lock the template's structure and keep a backup copy before editing it.

Variations

• Simpler version: Skip the Claude narrative step and have the Zap deliver a raw data export to a Google Sheet instead. You write the summary by hand, but the pull itself is still automated.
• Extended version: Add a second Claude step that compares this quarter's numbers against the last three quarters (pulled from a running Google Sheet log) and flags multi-quarter trends, not just quarter over quarter.

What to Do Next

• This week: Run the Zap once manually and compare its output against a report you pull by hand, to confirm the field mapping is accurate before you rely on it.
• This month: Extend the same Zap to your other top partner accounts by duplicating it with a different CRM filter for each.
• Advanced: Feed the resulting quarterly data into the weekly pipeline digest build described in a companion guide, so both reports draw from a single consistent data pull.

Advanced guide for Business Development Manager professionals. These techniques use more sophisticated AI features that may require paid subscriptions.