React the moment a payment comes in

A customer pays. Seconds later they've got a warm thank-you, they're saved to your client list, and you've got a one-line heads-up — all without you touching anything.

What you'll build — An app-event trigger on Stripe's Checkout completed event that starts a short routine: thank the customer, save or update them in your client list, and drop you a note about the sale. You build it by describing it to your Personal Assistant — no webhook to paste, no code.
Who it's for — Anyone taking payments through Stripe who wants the follow-up handled the instant money lands, not whenever they next check.
Time & plan — About 15 minutes. You'll need any plan that includes an agents budget, and you'll connect Stripe (via a secret key) and, for the thank-you email, Gmail. Each fire draws from your agents budget.

Start from the built-in template

The Personal Assistant's Tasks tab ships a Payment thank-you flow starter (in the automation examples). Click it to open a Personal Assistant chat with the request pre-written — the walkthrough below is what happens next. Or type it yourself.

Ingredients

#	You'll switch on	Where	Needed for
1	The Personal Assistant agent	Built in to the Agents section	Builds the routine and the trigger for you
2	Stripe connector	Connect from the chat — paste a Stripe secret key	Watching for completed checkouts
3	Gmail connector (or another email app)	Connect from the chat	Sending the thank-you
4	Your client list	Built in (Sales Platform), or a CRM like Pipedrive/HubSpot	Saving the customer
5	One app-event trigger	The agent adds it for you	Firing the routine on every paid checkout

Stripe connects with a key, not a sign-in

Every other app connector is a one-click sign-in. Stripe is the exception — it asks you to paste a secret key from Stripe's Developers → API keys. A restricted key with only the permissions you need works too, and it's safer. Keep the key private.

Steps

1. Open the Payment thank-you flow starter

Open Agents → open the Personal Assistant → Tasks tab, and click Payment thank-you flow. It opens a chat with the request filled in:

I want a follow-up flow for new Stripe payments. When a customer completes a checkout, send them a short thank-you email, save or update them in my client list, and drop me a one-line note about the sale…

Send it.

2. Answer the setup questions

The assistant asks what it needs before building anything:

Agent: Two things first — what should the thank-you email say (tone, and anything specific like a discount code or a link)? And where do you track customers: your MyChatBot client list, or a CRM like Pipedrive or HubSpot?
You: Keep it warm and short — thank them by name, confirm the order, and link to our help center. Track them in my MyChatBot client list.

3. Connect Stripe (and email) right in the chat

The routine needs Stripe and an email app, so the assistant shows connect cards in the conversation:

Agent: I'll need Stripe to watch for payments and Gmail to send the thank-you. Connect these and I'll continue.

Click Connect on the Stripe card. Instead of a sign-in, a paste-your-API-key prompt opens. In Stripe, go to Developers → API keys, create (or copy) a key — a restricted key with read access to checkout/customers plus permission to read events is plenty — and paste it in.
Click Connect on Gmail and approve the popup.
Click Continue.

Both are now connected account-wide and switched on for this agent.

Connecting an app right from the chat — Stripe asks for a secret key instead of a sign-in

4. Let it pick the real Stripe event

Here's the part worth watching: the assistant doesn't guess which Stripe event to use — it checks what's actually available. Stripe exposes several events an automation can react to:

Stripe event	Fires when
Checkout completed	A customer completes a Stripe checkout and pays
Invoice paid	An invoice is paid
New subscription started	A customer starts a subscription
Payment failed	A payment attempt fails
Subscription cancelled	A subscription is cancelled

For "a customer paid," the right one is Checkout completed. All Stripe events here are instant — they reach your routine within moments, no polling delay.

Agent: Stripe gives me five events to choose from. For a completed purchase I'll use Checkout completed (it's instant). Sound right?
You: Yes.

5. Understand what the routine will (and won't) do on its own

The assistant builds a short routine and explains the safety model up front — this is the important bit:

Read the payment and save/update the customer in your client list — these run on their own.
Notify you with a one-line note about the sale.
The thank-you email touches a real customer, so it sits behind an approval gate. That means each fire pauses and shows you the exact email before it sends — you tap Approve and it goes.

Hands-off vs. approve-each-time — your call

The gate is there because an ungated routine step physically can't message the outside world — that's what keeps automations safe. You have two honest options:

Keep the gate and approve the first weeks of thank-yous with one tap each, until you trust it.
Drop the email step entirely and let the routine just log the sale and notify you (fully hands-off), sending thank-yous yourself.

Tell the assistant which you want.

6. Sample it with a test payment before it goes live

Before a single real customer is touched, run one test through it. In Stripe's test mode, complete a checkout (Stripe's test card 4242 4242 4242 4242 works). Then watch the trigger's conversation appear in your chats:

A conversation named after your trigger opens. The routine reads the test payment, saves the test customer, notifies you — and pauses on the "Your approval is needed" card showing the drafted thank-you email.

Read the draft. If the tone or details are off, tell the assistant to adjust the routine, then run another test. When the sample looks right, you're live — every real completed checkout now fires it.

A trigger keeps its own thread

Every fire runs in the trigger's own conversation (named after the trigger), so all its history stays in one place. Ask your assistant "what has my Stripe trigger done lately?" any time.

Make it yours

Log the sale to a sheet. Connect Google Sheets and add a step: "also add a row to my revenue sheet — date, customer, amount." An instant, hands-off revenue log (that step is read-and-write to your own sheet, no customer contact, so it needs no gate).
Different moment, different flow. Point the trigger at Invoice paid for recurring billing, or build a second trigger on Payment failed that pings you to chase it.
Route to a CRM instead. If your customers live in Pipedrive or HubSpot, connect that app and the save-customer step writes there instead of the MyChatBot client list.
Watch the limits. An account can have up to 10 triggers, and each fires at most 12 times an hour — extra events wait for the next hour. Fine for most shops; something to know if you get a sudden rush. See Triggers → limits.

React the moment a payment comes in ​

Ingredients ​

Steps ​

1. Open the Payment thank-you flow starter ​

2. Answer the setup questions ​

3. Connect Stripe (and email) right in the chat ​

4. Let it pick the real Stripe event ​

5. Understand what the routine will (and won't) do on its own ​

6. Sample it with a test payment before it goes live ​

Make it yours ​

See also ​