Easy Tech TutsHow to Connect Stripe With Webflow, Add & Integrate Easily 2026
By Impran M NLast checked against official docs
Webflow's Ecommerce plan connects to Stripe directly, through a Connect Stripe setting under Settings, Ecommerce, Payment. But that's only one of three real ways to link the two, and it's the one with the most setup.
If you just need to take payments for a service, a digital product, or a single item, Stripe's own Payment Links or Buy Button work with any paid Webflow site plan and skip Ecommerce entirely. Neither of those touches your site's content, though.
If you want a Stripe event, a new charge or a completed checkout, to update something on the page (a recent-purchases list, a member directory), you need a third piece connecting the two: an automation tool like Zapier, with Stripe as the trigger and Webflow's CMS as the action. This guide walks through that Zapier route in detail, since it needs the most explaining, and closes with a comparison of when to reach for Payment Links or the Buy Button instead.
Before you start
- A Stripe account and a Webflow site (Zapier's free plan is enough for the automation itself)
- For the native alternative described below: a paid Webflow site plan (Basic or higher), since Payment Links and the Buy Button don't work on Webflow's free Starter plan
01Get your Stripe account ready
Log into Stripe and you land on the account home screen. A fresh or sandbox account opens in Test mode, shown as a banner across the top confirming you're experimenting safely instead of processing real charges.
Stripe also prompts you to verify your email before anything else, with Open Gmail and Resend buttons right on the dashboard. The Get Started panel below offers no-code paths for sending invoices or creating subscriptions.
Further down sit your publishable and secret API keys, both prefixed pk_test_ and sk_test_ while you're in test mode. Those are the credentials any external tool, Zapier included, will eventually need.
02Create a new Zap with Stripe as the trigger
In Zapier, start a new Zap and search for Stripe as the app for step one. Choosing an event here (a new charge, a successful payment, a new customer) defines exactly what has to happen in Stripe before anything fires in Webflow. This is the piece Webflow has no visibility into unless you're using its native Ecommerce checkout, which is why an automation route like this one exists at all.
03Add Webflow as the action app
Add a second step and search for Webflow, which opens a setup panel asking for an Action event, then an account you authorize by clicking Sign In. Webflow's actions through Zapier center on CMS items: creating, updating, publishing, or finding a collection entry, since Zapier works through Webflow's CMS API, not its payments layer.
That distinction matters. This path lets a Stripe event update your site's content. It doesn't process a card, and it isn't a substitute for Webflow's own Ecommerce Stripe connection.
04Authorize both accounts
Click Sign In on the Webflow step to open its OAuth screen and grant Zapier access to your site, the same way you authorized Stripe on the trigger step. Zapier stores both connections, and you can revoke either one at any time from your connected accounts settings. Neither app hands its credentials to the other directly.
05Map the fields and test
Once both apps are connected, map the data from the Stripe trigger (customer email, payment amount, product name) into the corresponding fields on the Webflow action, such as a CMS collection's text or number fields. Run Zapier's test step to confirm a sample Stripe event produces the expected update in Webflow before trusting the automation with real traffic.
06Publish the Zap
Once the test step comes back clean, switch the Zap from Draft to Published using the control in the top right. This exact setup, one Stripe trigger and one Webflow action, fits inside Zapier's free plan: 100 tasks a month, unlimited Zaps, capped at one trigger plus one action per Zap.
From publish on, whatever Stripe event you chose will push through to Webflow automatically: showing recent purchases, updating a member directory, or triggering a thank-you page update, all without touching Webflow's own checkout. One thing to check afterward: Webflow's Create Item and Update Item actions can save to either the draft or the live version of a collection item. If the Zap runs successfully but nothing changes on the published site, confirm the action is set to update the live version, or publish the collection in Webflow after the Zap runs.
| Method | What it does | Webflow plan needed | Best for |
|---|---|---|---|
| Stripe Payment Links | A hosted Stripe checkout page, linked from a button or link on your page | Any paid Site Plan (Basic and up) | Services, one-off sales, subscriptions, no on-site cart needed |
| Stripe Buy Button | A branded Stripe-hosted checkout embedded on the page through a code Embed element | Any paid Site Plan (Basic and up) | A styled on-page button instead of a plain link |
| Zapier automation (this guide) | A Stripe event creates or updates a Webflow CMS item | Any plan with CMS collections, plus a Zapier account | Reacting to Stripe events elsewhere on the site, not for collecting the payment itself |
Webflow's own Ecommerce plan, with a native cart and checkout, is a fourth option and isn't covered in this guide.
When it doesn't work
A live payment fails even though the same flow worked in test mode
Why: Stripe requires identity verification, business details, and a linked bank account before it processes real charges; test mode skips all of that.
Fix: In the Stripe Dashboard, click the bell icon and resolve any outstanding requirements before testing with a real card.
The Zap runs successfully, but the Webflow site doesn't change
Why: Webflow's Create Item and Update Item actions can write to the draft version of a CMS collection instead of the published one.
Fix: Check whether the Zap action is set to update the live version, or publish the collection in Webflow after the Zap runs.
Zapier won't let you add a third step to the Zap
Why: The free plan limits a Zap to one trigger and one action.
Fix: This guide's setup already fits inside that limit. To add a step, such as also posting to Slack, you need a paid Zapier plan.
Frequently asked questions
Does this replace Webflow's native Ecommerce Stripe integration?
No. Webflow's Ecommerce plan connects to Stripe directly for a full cart and checkout. This guide's Zapier route is for sites without Ecommerce that still want content to react to Stripe events; it works through Webflow's CMS, not its payments system.
I just want to accept a payment, not update my site's content. Do I need Zapier?
No. Stripe's own Payment Links or Buy Button connect to any paid Webflow site plan directly, without Ecommerce or Zapier. See the comparison table above.
Is my Stripe login information stored inside Zapier or Webflow?
No. Both connections use each platform's own OAuth authorization screen, so your Stripe and Webflow credentials are never entered into Zapier directly.
What can a Webflow action do in response to a Stripe event?
Typically it creates, updates, publishes, or finds a CMS collection item, since that's what Webflow exposes through Zapier. It can't process a payment or modify your checkout page.
How do I test this safely before going live?
Keep your Stripe account in Test mode, which uses pk_test_ and sk_test_ prefixed keys, and run Zapier's built-in test step on each part of the Zap before switching it on.
Does this cost anything?
Zapier's free plan covers this exact setup: one trigger, one action, 100 tasks a month. You'd only need a paid Zapier plan to add a third step to the same Zap.
Sources and last check
The Zap walkthrough and both screenshots come from a session recorded in July 2025. Re-checked in September 2026 against Webflow's own blog post on Stripe Payment Links and the Buy Button, and against Zapier's help center for its free-plan limits. That check added the two native, Zapier-free methods this guide previously didn't mention, confirmed this exact automation fits inside Zapier's free tier, and added the draft-versus-live CMS item gotcha.
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.
