← All posts

Send one-off emails when someone books or pays and a weekly newsletter

Second Brain OSAug 19, 2026
Send one-off emails when someone books or pays and a weekly newsletter

Most people struggle with writing email because they haven't figured out when to send them.

All beecause nobody ever handed them a clean mental model for it.

The model is called event-driven, and you and I should spend two minutes on it, because once it is clear, every email decision in your business becomes obvious.

Here is where it comes from in this system. The Second Brain OS Website Operator wires the forms so every Lead and Purchase fires as an event, forwards those events to a sheet or webhook of your choosing, and carries an email skill that writes the sending script for you, from the one-off booking confirmation to the weekly newsletter. What that unlocks is an email setup with no email tool: the right message goes out the moment someone books or pays, from your own Gmail with its own reputation, and the newsletter goes to contacts your CRM has already scored as worth writing to.

What "event-driven" means

Think of a hotel bell on the front desk.

The receptionist does not check the lobby every five minutes to see whether someone has arrived. Guests ring the bell, and the ring triggers the response.

No ring, no response. The bell is the event.

Event-driven email works the same way. An event happens, an email gets sent.

This is called event driven email or transactional email. And it's completely different from marketing emails like your weekly newsletter (which we'll get to in a second!)

Your funnel already rings the bell

Here is the good news: in this system, the bells ring themselves.

Two events matter most.

A Lead event fires when someone declares themselves:

  • Fills a form.
  • Starts a chat with your receptionist.
  • Books a call.

Their details land in your CRM as a contact.

A Purchase event fires when someone pays: through a Tally form with Stripe attached, or for any product you sell.

Every Lead and Purchase on your website is captured and dispatched automatically, with the person's details attached.

And to my earlier point, if you know when to send an email it's a lot easier to write the email. Filled a form your ebook A lead magnet? Purchased a 1:1 consultation? You know what to do.

And that automation you setup doesn't have to be limited a single email. You can send a sequence with 24 hour delays in between or a single email with a follow up after a few days. Sky is the limit to what that automation looks like.

Now back to the two kinds of email

Transactional emails answer an event.

A Lead fires, and a "thanks, here's what happens next" goes out. A Purchase fires, and the receipt and access details go out.

One event, one email/email sequence, immediately, to one person.

Marketing emails do not wait for an event.

Newsletters, weekly tips, offers: sent on your schedule, to everyone who opted in (and ideally is still interested).

Different triggers, different rhythm, and, as you are about to see, different sending advice.

Deliverability is the whole game

Before the how, the thing that outranks everything else: an email that lands in spam did not happen.

Deliverability lives and dies on your domain's reputation. The technical trio (SPF, DKIM, DMARC) plus a history of real people opening mail from your address.

The safest reputation you own is the one attached to your everyday Google Workspace or Gmail account, built over years of ordinary correspondence.

This is why there is no black-box email sender bundled into the system. Every option below sends from infrastructure whose reputation you control.

That is the principle; the rest is plumbing.

Transactional, option 1: Google Sheets + Apps Script

You already know your receptionist can post captured data to a Google Sheet mid-chat, and Lead and Purchase events can land in a sheet the same way.

Google Sheets comes with Apps Script, Google Workspace's built-in scripting studio.

A short script watches the sheet for new rows and sends an email through your own Gmail whenever one appears. New booking row, confirmation email. New payment row, receipt.

No third-party tool, no subscription, sender reputation fully yours.

And you do not have to write the script: the Website Operator will.

Transactional, option 2: Zapier + Google Sheets + Gmail

Prefer clicking to scripting?

Zapier is an automation service that connects apps with "when this, do that" rules, no code involved.

The rule here is one line: when a new row appears in the sheet, send a Gmail.

You assemble the email template in Zapier's editor and stay entirely inside tools you already use. It costs a Zapier plan at volume, and it takes about ten minutes to set up.

Same shape as option 1, different trade: money for convenience.

Marketing: your CRM plus your own Gmail

For the weekly newsletter, the list is not something you build.

It already exists: your CRM holds every lead your receptionist and forms have ever captured.

This is where MCP earns an introduction. MCP is a standard that lets an AI assistant connect directly to your actual tools, with your permission, and act on them.

With it, your assistant pulls the audience using the Second Brain OS CRM tools, drafts the newsletter with you, and sends it through your own authenticated Gmail connection.

The weekly send becomes one conversation: "pull everyone who became a lead this month and send them this."

From your address, with your reputation, to people who actually know who you are.

Scaling up: forward events to an email platform

When volume outgrows Gmail, you do not rebuild anything. You redirect the events.

Every Lead and Purchase event can be forwarded, to any destination you choose.

Point it at a dedicated event-driven email platform (ActiveCampaign, Bento, Klaviyo, customer.io, Dittofeed, Loops, Brevo, etc) and those tools receive your events natively, because events are the language they are built on.

They give you journeys triggered by events ("purchase, then a five-email onboarding sequence") plus scheduled campaigns, in one place.

Transactional and marketing, driven by the same bells your funnel was already ringing.

Unsubscribe is part of deliverability, not an afterthought

One more piece, and it belongs in this post precisely because of the deliverability section above.

Google and Yahoo now require bulk senders to offer a working, one-click unsubscribe.

An email without one is an email asking to be marked as spam, and every spam mark chips away at the domain reputation you have been carefully protecting.

So the system treats unsubscribe as a first-class event. Every email the system sends carries an unsubscribe link.

One click, no forms, no "manage your preferences" page: the person lands on a short confirmation page, and their contact record in the CRM is marked as opted out.

You can still send them transactional emails, against lead and purchase events. They just don't want your weekly newsletter and any other marketing emails you send out.

From that moment, the contact-pull that builds your newsletter audience filters them out. The risk of accidentally emailing someone who asked you to stop is now much less!

There is a resubscribe path too, the same mechanism in reverse, for the person who opted out in a hurry and wants back in to your weekly newsletter.

The quiet benefit: a clean list of people who actually want your emails is itself a deliverability asset. Senders with low complaint rates land in inboxes.

P.S. Don't think of unsubscribe as the enemry; it is actually a self-healing function that keeps your email list clean and saves you from being marked as a known spammer.

The takeaway

Events fire whether or not you use them.

Start free: a sheet, a script, your own Gmail. Let the same events carry you to a dedicated platform when the volume asks for it.

The bell was ringing all along. Now something answers it.

A note on prices: every price in this series is the price inside its funnel, where each purchase unlocks the next. Bought on its own, outside the funnel, the same product can cost up to 30% more.

Next up: updating your products without touching the website code.

That was Part 13 of 24.

Next: Update your products, company details and team without touching the website code