Zapier Automation: Chain the Board Deck Pipeline End to End

What This Builds

Comp committee and board deck prep eats five to eight hours before every meeting: exporting numbers from the HRIS, pulling last quarter's spend, and turning both into a narrative a non-specialist board can follow. This automation fires the moment your team marks the quarter's data ready. It gathers every department's numbers, drafts an overview and a department-by-department narrative, drops both into a copy of your committee deck template, and emails you the link. The draft is waiting before you would otherwise have opened a blank slide.

Prerequisites

• A Professional plan with multi-step Zaps, filters and AI by Zapier available ($29.99/month)
• A Google account for Sheets, Slides and Gmail, free for personal use or your organization's paid Business Standard account
• A quarterly tracker spreadsheet your team already fills in ahead of each committee meeting
• A Google Slides committee template you are willing to add placeholder text to
• 45 minutes to prepare the tracker and template, 60 to 75 minutes to build and test the Zap

Total ongoing cost is the $29.99/month subscription. Google Sheets, Slides and Gmail add nothing new if your organization already runs on a Google account. Each run uses a handful of Zapier tasks, and a run that fails partway through still uses the tasks it spent before the failure.

The Concept

A deck built from a spreadsheet is really two problems stacked on top of each other: turning rows of numbers into sentences, and turning those sentences into slides. Zapier handles both, but not the way most people first try it.

The tempting design loops over the departments and adds one slide per department. Zapier's Google Slides app cannot do that. It has no action that adds a slide to an existing deck. What it can do is copy a template presentation and replace placeholder text such as {{overview}} anywhere in it. So this Zap gathers all the departments first, joins them into one block of text, asks the AI step for a few named sections, and fills those sections into a fresh copy of your template. No loop means no loop traps: exactly one deck and exactly one email per run.

Build It Step by Step

Part 1: Set up the tracker and the guard column

Give your tracker spreadsheet two tabs.

1. Departments tab with columns Quarter, Department, Headcount, Budget Variance, Spend Notes and Summary Line. Fill Summary Line with a formula that turns each row into one readable line, for example =B2&": headcount "&C2&", budget variance "&D2&". Notes: "&E2, and copy it down.
2. Deck Control tab with columns Quarter, Deck Status and Deck Link. Add one row per quarter. Deck Status takes the values "Not Ready," "Ready," "Building" and "Sent."

The Deck Status column is what stops this Zap from re-firing every time someone edits an unrelated cell. Google Sheets' "New or Updated Spreadsheet Row" trigger fires on changes to a row, so without a guard column and a step that updates it, one stray edit could start a second full deck build.

Part 2: Prepare the slide template

Open your committee template and make a copy for Zapier to use. Type these placeholders, curly braces included, into the text boxes where each section belongs:

• {{quarter}} on the title slide
• {{overview}} on a summary slide
• {{department_detail}} on a department slide with a large text box
• {{questions}} on a closing slide

Set the large text box to shrink text on overflow (Format options, then Text fitting), because the department section runs longer than a typical bullet slide.

Part 3: Build the trigger and the guard

1. Go to zapier.com, click + Create, then Zap
2. Trigger app: Google Sheets, event: New or Updated Spreadsheet Row. Select the tracker, the Deck Control worksheet, and set the trigger column to Deck Status
3. Action 1, app: Filter by Zapier. Only continue if Deck Status exactly matches "Ready." This stops runs on rows marked "Not Ready," "Building" or "Sent"
4. Action 2, app: Google Sheets, event: Update Spreadsheet Row. Set Deck Status to "Building" on the row that triggered this run, so a second edit before the Zap finishes cannot start a duplicate build

Part 4: Gather every department into one block of text

1. Action 3, app: Google Sheets, event: Lookup Spreadsheet Rows (Advanced). Search the Departments worksheet for rows where Quarter matches the Quarter from the trigger row. The step returns every matching row as a list
2. Action 4, app: Formatter by Zapier, event: Utilities, transform: Line-item to Text. Map the Summary Line list from Action 3 as the input and choose a new line as the separator. The output is one department per line

What you should see: in the test result, a single text field listing each department on its own line.

Part 5: Draft the sections with AI by Zapier

1. Action 5, app: AI by Zapier. Keep the built-in model, or pick the provider your organization has approved
2. Prompt:

Here is this quarter's compensation and benefits data, one department per line:

{{Line-item to Text output}}

Write three sections for a compensation committee deck. The audience is
board members who are not benefits specialists.

overview: three to four sentences on the overall budget position. Lead
with the total variance and the one or two departments that drive it.

department_detail: one short paragraph per department, in the order given.
Start each paragraph with the department name, lead with its variance,
then give the likely driver in plain language. Do not speculate about a
cause the notes don't support.

questions: three questions the committee is likely to ask, each with a
one-sentence suggested answer drawn only from the data above.

1. Under Output fields, add three text fields named overview, department_detail and questions, so later steps can map each section on its own

Part 6: Build the deck and close the loop

1. Action 6, app: Google Slides, event: Create Presentation From Template. Choose the template copy from Part 2, name the new file with the quarter (for example Comp Committee Draft Q3), and map each placeholder: quarter from the trigger row, and overview, department_detail and questions from Action 5
2. Action 7, app: Google Sheets, event: Update Spreadsheet Row. On the trigger row, set Deck Status to "Sent" and Deck Link to the new presentation's link from Action 6
3. Action 8, app: Gmail, event: Send Email. To yourself only, subject Board deck draft ready for review, body with the presentation link from Action 6

Part 7: Test end to end

1. Duplicate your tracker into a test copy with two or three sample departments and point the Zap at it
2. Mark the test quarter's Deck Control row "Ready" and run the Zap manually from the Zapier editor
3. Confirm one new presentation appeared with every placeholder filled, that the department section names each sample department, and that exactly one email arrived
4. Check that Deck Status now reads "Sent," then edit another cell on that row and confirm the Zap stops at the filter
5. Point the live Zap at your real tracker and turn it on

Real Example: The Week Before a Committee Meeting

Setup: The Departments tab holds six departments for the quarter. A teammate finishes the export on a Wednesday afternoon and marks the quarter's Deck Control row "Ready."

Input: The Zap picks up the change within a few minutes, gathers the six summary lines and sends them to the AI step as one block.

Output: A new presentation appears in Google Drive with the overview on slide two, a paragraph for each of the six departments on the department slide, and three likely committee questions at the end. One email arrives with the link, and the Deck Link column holds it for the rest of the team.

Time saved: What used to consume most of a day before a committee meeting (exporting, drafting, formatting) now leaves a rough draft waiting by the time you'd normally have just started pulling numbers. You still split the department section across slides, add charts and edit the wording, but the blank-page problem is gone.

Data sensitivity: Keep the tracker at the department level. If your HRIS export includes individual employee names, IDs or exact salaries, strip those columns before they ever reach this spreadsheet. Remember that the AI step is not the only place the data goes: Zapier records each step's input and output in your Zap history, so the department figures also sit in your Zapier account until that history ages out or you delete it. Department-level variance numbers are fine there. An individual's pay is not.

What to Do When It Breaks

• The Zap stops running and you don't notice until the week of the meeting → A quiet automation looks the same as a quiet week. Turn on Zapier's Zap health notifications, and put a recurring reminder on your calendar to check the Deck Status column two weeks before every committee meeting, whether or not an email arrived.
• A placeholder shows up unfilled in the new deck → The text in the template must match the field name in Action 6 exactly, braces included. Retype it in the template, because copied text sometimes hides formatting that breaks the match.
• The department section leaves out a department → Check that the missing row's Quarter value matches the trigger row exactly (a stray space is enough to break the lookup) and that its Summary Line formula is filled in.
• The Zap re-fires on a quarter you already sent → Someone reset Deck Status to "Ready," or the Update Spreadsheet Row step in Action 7 failed on the last run. Check the Zap history for that run.
• The narrative invents a reason for a variance → Tighten the Spend Notes on that row. The prompt only allows causes the notes support, so thin notes produce either vague or overconfident text.

Variations

• Simpler version: Skip the slides. Replace Action 6 with Google Docs' Create Document From Template and send yourself a written briefing memo instead of a deck. This suits a small committee that reads a memo in advance.
• Extended version: Add last quarter's variance as another column in the Summary Line formula, so each department paragraph can note the trend, not just the current number.

What to Do Next

• This week: Add the Deck Control tab and the Summary Line column to your tracker, and put the four placeholders into a copy of your template.
• This month: Build the full Zap and run it against test data for two committee cycles before you rely on it for a real meeting.
• Advanced: Save each finished deck into the vendor and compliance Claude Project so questions after the meeting can be answered from the same numbers that built the deck.

Advanced guide for compensation and benefits manager professionals. These techniques use more sophisticated AI features that may require paid subscriptions.