Zapier Automation: Never Walk Into a Session Having Forgotten the Last Commitment

What This Builds

With eight to twelve active clients on staggered fortnightly or monthly schedules, remembering exactly what each one committed to last time is a memory problem, not a coaching problem, and it undermines your credibility the moment it fails. This automation watches a tracking sheet you already keep and emails you a reminder a few days before each client's next session, quoting back their own last stated commitment so you walk in prepared instead of guessing.

Prerequisites

• A Zapier account, and comfort building a multi-step Zap that reads a spreadsheet and sends an email.
• A Professional plan ($29.99/month), because this Zap needs more than one step and Zapier's free tier only runs single-step Zaps.
• A Google account with a spreadsheet (or willingness to create one) where you already log or are willing to log each client's next session date and last commitment.
• Total ongoing cost for this build: $29.99/month for Zapier, on top of whatever Google Workspace plan you already pay for.

The Concept

Picture a standing assistant who reads your tracking sheet every morning and taps you on the shoulder only when something is actually due soon. That's what this Zap does. It doesn't touch your calendar or your practice platform. It watches one column (next session date) and one column (last commitment) in a spreadsheet, and when a session is close, it emails you a short reminder built from that row. Nothing happens on the days when nothing is due.

Build It Step by Step

Part 1: Set up the tracking sheet

Create a Google Sheet (or add a tab to one you already keep) with these columns:

Add a helper column E with this formula, which flags rows that are due for a reminder without duplicating one already sent:

=IF(AND(C2-TODAY()<=3, C2-TODAY()>=0, D2<>"Y"), "SEND", "")

This returns "SEND" when the next session is zero to three days away and no reminder has gone out yet, and stays blank otherwise. Test it with a few sample dates before wiring up the Zap: put tomorrow's date in one row and a date three weeks out in another, and confirm only the near-term row shows "SEND."

Part 2: Build the Zap

1. In Zapier, create a new Zap with a Schedule by Zapier trigger set to run once each weekday morning.
2. Add a Google Sheets: Lookup Spreadsheet Row(s) step (or Filter step after a full-sheet read) that pulls rows where column E equals "SEND."
3. Add a Formatter step if you want to clean up the commitment text before it lands in an email (trim whitespace, title-case the client code).
4. Add a Gmail: Send Email step addressed to yourself, using the client code and last commitment from the matched row in the subject and body. For example: Subject "Session prep: {{Client Code}}," Body "Next session in {{days}} days. Last commitment: {{Last Commitment}}."
5. Add a final Google Sheets: Update Spreadsheet Row step that writes "Y" into column D for the row you just processed, so it doesn't fire again tomorrow.
6. Turn the Zap on and test it with one real (but already-anonymized) row before trusting it with your full client list.

Part 3: Test and refine

Add a test row with tomorrow's date and a placeholder commitment, run the Zap manually from Zapier's test panel, and confirm the email arrives with the right client code and commitment text, and that column D updates to "Y" afterward. Run it a second time and confirm it does not send a duplicate for the same row.

Real Example: A Fortnightly Client List

Setup: A tracking sheet with eleven active clients, each on a fortnightly or monthly cadence, columns filled with client codes instead of names.

Input: The Zap runs every weekday at 7 a.m. On a Tuesday, two rows match: client "MK-4" has a session in two days with a last commitment of "practice delegating the vendor review to a direct report," and client "RT-1" has a session in three days with a commitment of "have the hard conversation with the peer who missed the deadline."

Output: Two emails land in the coach's own inbox before 7:15 a.m., each naming the client code and the exact commitment, so both sessions can be opened with "last time you said you'd..." instead of scrolling back through old notes.

Time saved: Removes the pre-session scramble of digging through notes to recall a commitment, and removes the risk of a session opening with no memory of it at all.

What to Do When It Breaks

• The Zap stops running and you don't notice → This is the failure that matters most because it's silent. Turn on Zapier's built-in "Zap is turned off" email alert in your account notification settings, and separately, glance at your Zap History page once a week. A Zap that silently stopped firing looks identical to a quiet week with no sessions due, until a client shows up and you have nothing prepared.
• The same reminder fires twice → Check that the final "mark as sent" step is actually running and writing to the right row. If the Zap errors out after the email step but before the update step, the row stays flagged as unsent and fires again the next day.
• A reminder fires for a session that already happened → Your Next Session Date column is probably stale. Build a habit of updating that column immediately after each session, or the whole automation drifts out of sync with reality.
• The formula shows "SEND" for a row you already handled manually → Overwrite column D to "Y" by hand. The Zap only trusts what's in the sheet.

Variations

• Simpler version: Skip Zapier entirely and set a recurring personal calendar reminder to scan the tracking sheet every Monday morning. Slower, but free and immune to silent automation failure.
• Extended version: Add a second branch that also flags a commitment deferred across three or more consecutive sessions, so you catch a pattern the way a practice-management platform's built-in tracking would.

What to Do Next

• This week: Build the tracking sheet and the helper formula, and test it with fake rows before connecting a real client.
• This month: Run it alongside your real caseload for a full cycle and confirm the reminder timing (three days out) actually gives you enough lead time.
• Advanced: Connect the same sheet to a second Zap that flags stalled commitments, rather than just upcoming ones.

A Note on Confidentiality

Every step this commitment text passes through, Google Sheets, Zapier's own systems, and Gmail, is a vendor boundary the client's coaching agreement almost certainly didn't anticipate by name. Two things matter here. First, Zapier's task history stores the data that moved through each step of a run, which means the client's commitment text sits in Zapier's own logs, not just in your sheet and inbox. Second, Zapier's task allowance counts every attempt, including ones that fail partway through, so a misconfigured filter that fires repeatedly on the same row burns your monthly allowance without sending a single useful reminder. Use a client code instead of a name in the sheet, keep the commitment phrase general rather than a verbatim quote from the session, and send the reminder only to your own inbox, never to the client automatically. If your Zapier plan or retention settings let you shorten task history retention, do that too.