The bench for local operators · Import the week back How checkout works
All packsLeadOnboardingBookingCommsBillingReviewsContentOpsLandlordServiceFull system
Shop Floor Bench · booking / billing

Calendar + Email + Payment Sync

Booked time, confirmation email, payment status in one loop.

The job it closes

The job it closes

A booked hour that never matches the invoice is how weeks fall apart. This file watches Google Calendar and a payment webhook, writes the same Leads row, and emails the client on create, cancel, and paid.

Before / after

Before / after

Before: calendar, mail, and money live in three places. After: one row with a paid stamp and one client email.

01

What you import

Calendar created / updated / cancelled + Stripe or PayPal payment webhook → Leads stamp → client Gmail. Event gets LOC-PAID / LOC-SYNC so the file does not email twice.

n8n

02

What you need

n8n, Google Calendar, Gmail, Google Sheets, Stripe or PayPal webhook. No AI.

03

Setup time

35–50 minutes. Payment webhook mapping takes most of it.

Limits — trust before ticket

Limits — trust before ticket

Paid does not flip locked CRM status to completed. Does not SMS the client. Does not find the slot (that is WF9). Same payment_id will not write twice.

Breakdown

How this pack runs

Sync calendar, email, and payment (import this)

Video posting soon.

Two paths if you stall

Self-serve

START-HERE.pdf page 1. Credentials. First live node. Email hello@ if a node name moved.

Named install

Preferred implementation partner is listed on Partners. Other approved shops later. We do not hold the file hostage.

Next on this bench