Easy Tech TutsHow To Automate Stripe Payment Notifications With Zapier Easily 2026
By Impran M NLast checked against official docs
Checking a Stripe dashboard on a loop to catch new sales is a habit worth automating away. Zapier can watch your Stripe account for payment events and fire off a notification through another app the moment one happens, so your team hears about revenue in real time instead of on a refresh cycle.
This guide builds that Zap from scratch: choosing Stripe as the trigger, connecting the account, and wiring up an action step that sends the alert. It also covers two things Zapier's own quickstart doesn't spell out clearly: the Stripe connection needs a paid Stripe plan, and why the payment amount can show up as a raw five- or six-digit number instead of a price.
Before you start
- A Stripe account on a paid plan, with administrator permissions (Zapier's Stripe connection requires both)
01Start a new Zap and choose Stripe as the trigger
From the Zap builder, the first step block is labeled "1. New Payment" once Stripe is selected as the App and New Payment as the Trigger event.
Stripe also offers New Charge, Failed Payment, New Customer, and several subscription and invoice triggers from the same dropdown; New Payment and New Charge both fire instantly now, since Zapier converted them from a polling check to real-time webhooks. The setup panel on the right lists App, Trigger event, and Account in order, and each one needs a value before testing becomes available. Zapier also offers a Copilot option that can build much of this workflow from a plain-language description, but working through each step by hand gives more control over exactly what triggers the automation and what the message ends up saying.
02Connect your Stripe account
Click Sign In next to the Account field to authenticate. Two constraints aren't obvious from the panel itself: Zapier's Stripe integration only works with an activated Stripe account on a paid plan, and the account needs administrator permissions; a free Stripe signup or a restricted team-member login won't complete the connection.
Stripe also requires separate connections for live-mode and test-mode data, so building against sandbox payments before going live means connecting Stripe twice, once for each mode. Once connected, this account becomes the source Zapier watches for the trigger event selected in step one, and there's no need to reauthenticate it for other Zaps built on the same account.
03Add an action step and pick the app
Below the Stripe trigger, click the action block to choose what happens next. In this build, Gmail is the action app; 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.
The Stripe payment event supplies the data. The action step decides where that data goes and in what form, and it doesn't have to be Gmail: Slack, Microsoft Teams, SMS, or any other app Zapier supports can sit in this slot instead.
04Configure Send Email as the action
Selecting Send Email from that list sets Gmail's action event and moves the step into a Configure stage, shown in the tab row above the setup panel: Setup, Configure, Test. The account shown is already connected, using the same Gmail credentials Zapier uses across other Zaps tied to that inbox, so no separate sign-in is needed if Gmail has been authenticated before. From here, the Configure tab is where the message gets built using data pulled from the Stripe trigger.
05Map Stripe's data into the message, and fix the amount format
The Configure stage is where the notification takes shape. Pull fields from the Stripe trigger's test data, such as customer name, charge amount, and currency, and drop them into the email's subject and body as dynamic tokens.
These are live references back to the trigger step, not typed text, so every new payment fills in its own values when the Zap runs for real. One field needs an extra step before it's readable: Stripe sends amount data in the smallest unit of the currency, so a $1,970.00 charge arrives as 197000, not as a formatted price. Insert a Zapier Formatter step between the trigger and the action, use its Currency or Divide option on the amount field, and map that output into the message instead of the raw number.
06Test before publishing
Run a test on the Stripe trigger step to fetch a genuine payload from the account; Zapier needs at least one real or recent payment event to pull sample data from, and this is also what confirms the field names being mapped match what Stripe sends. Test the full Zap, not only the trigger.
This is what catches a formatting problem like the raw-cents amount before a live customer payment sets off a broken-looking alert. If the trigger is connected to test-mode Stripe data, switch it to the live-mode connection before turning the Zap on.
When it doesn't work
The notification shows a raw number like 197000 instead of $1,970.00
Why: Stripe sends amount fields in the smallest currency unit (cents for USD), not as a formatted decimal amount.
Fix: Add a Zapier Formatter step between the trigger and the action, apply its Currency or Divide-by-100 option to the amount field, and map the formatted result into the message instead of the raw field.
Stripe won't complete when connecting a new account
Why: Zapier's Stripe integration requires an activated Stripe account on a paid plan with administrator permissions; a restricted or free-tier Stripe login can't finish the connection.
Fix: Sign in with a Stripe account that has a paid plan and admin rights, or ask whoever administers the Stripe account to complete the connection.
The Zap fires on test payments but never on real ones, or the other way around
Why: Stripe live-mode and test-mode data each need their own Zapier connection; a Zap built against one won't see events from the other.
Fix: Check which connection the trigger step is using under the Account field, and reconnect with the correct Stripe mode.
Frequently asked questions
Does this only work with Slack or Teams for notifications?
No. The action step can be any app Zapier supports. This build uses Gmail's Send Email action, but the same Stripe trigger works with Slack, Teams, SMS, or any other notification app connected as the action step.
Why does my notification show a number like 197000 instead of $1,970.00?
Stripe sends the amount field in the smallest unit of the currency (cents for USD), not as a formatted price. Add a Zapier Formatter step between the trigger and the action, apply its Currency or Divide-by-100 option to the amount field, and map the formatted result into the message.
Do I need a paid Stripe plan to connect it to Zapier?
Yes. Zapier's Stripe integration requires an activated Stripe account on a paid plan with administrator permissions; a free Stripe account can't complete the connection.
Do I need to test the Zap before turning it on?
Yes. Testing the Stripe trigger pulls a real payload so field mappings can be checked, and testing the full Zap catches formatting issues, like the raw amount problem above, before a live payment sets off a broken alert.
Can I trigger notifications for failed payments instead of successful ones?
Yes. Failed Payment is a separate instant trigger in the same dropdown as New Payment, alongside triggers for new customers, subscriptions, disputes, and refunds.
Sources and last check
Click path and screens come from a Zap build recorded in July 2026. Trigger names, the paid-plan and admin-permission requirement for connecting Stripe, and the cents-versus-formatted-amount behavior were re-checked against Zapier's official Stripe documentation in September 2026. That check added the paid-plan requirement and the formatting fix this guide previously left unexplained.
About the author
Impran M N
I've been hooked on technology for as long as I can remember — especially the new tools and AI apps that seem to land every other week. Easy Tech Tuts is where I write up whatever I've just worked out: I do the task in the real product, record the screen, and turn it into the guide I wish I'd found first.
