How To Automate Stripe Payment Notifications With Zapier Easily 2026

From the Zaps builder, the first step block is labeled "1. New Payment" once you've selected Stripe as the App and New Payment as the Trigger event.

The setup panel on the right lists the App, Trigger event, and Account fields in order — each one has to be filled before you can move to testing. This is also where Zapier offers a Copilot option to configure the whole workflow automatically, but working through each step manually gives you more control over exactly what triggers the automation.

Click Sign In next to the Account field to authenticate. Zapier explains right on the panel that Stripe is a secure partner — your credentials are encrypted, can be removed at any time, and all connected accounts are manageable from one place. Once connected, this Stripe account becomes the source Zapier watches for the New Payment event you selected, and you won't need to reauthenticate it for other Zaps built on the same account.

Below the Stripe trigger, click the action block to choose what happens next. In this build, Gmail is selected as the action app, and clicking into the Action event field opens a searchable list of everything Gmail can do — Add Label to Email, Archive Email, Create Draft, Create Draft Reply, Create Label, and more, scrollable in a dropdown. The Stripe payment event supplies the data; the action step decides where that data goes and in what form.

Selecting Send Email from that list sets Gmail's action event and moves the step into a Configure stage, visible in the tab row above the setup panel: Setup, Configure, Test. The account shown is already connected — the same Gmail credentials Zapier uses across other Zaps tied to that inbox — so there's no separate sign-in needed here if you've authenticated Gmail before. From this point the Configure tab is where you'd build the actual message using data pulled from the Stripe trigger.

The Configure stage is where the notification actually takes shape — you pull fields from the Stripe trigger's test data, such as the customer's name, the charge amount, and the currency, and drop them into the email's subject and body as dynamic tokens. Because these are live references back to the trigger step rather than typed-in text, every new payment event fills in its own values automatically when the Zap runs for real. Keep the subject line short and specific, like a customer name and amount, since that's what someone will see first in a notification.

Before publishing, run a test on the Stripe trigger step to fetch a genuine payload from your account — Zapier needs at least one real or recent payment event to pull sample data from, which is also what lets you confirm the field names you're mapping actually match what Stripe sends. Testing the full Zap end to end, not just the trigger, catches formatting problems — like a currency showing as a raw number instead of a formatted amount — before a live customer payment triggers a broken-looking alert.