About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Stripe: Unexpected test data for Checkout Session Completed trigger

  • 27 November 2023
  • 4 replies
  • 77 views
cdwyer
Userlevel 1
Badge

The Stripe trigger for Checkout Session Completed should, in my mind, only include `CheckoutSession` objects where the `status` is complete. Currently trying to update a Zap with this trigger, and all the test records have a `status` of open and a `payment_status` of unpaid. Maybe a bug? 🤔

Setup is kinda impossible, since none of the test records have the right fields populated (as they’re all incomplete). TIA for any help you can offer, here!

 

 

4 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @cdwyer 

Good question.

I can confirm I’ve seen the same results when testing.

Try completing a successful checkout sessions, then click the button to [Find new records].

Also, you can submit feedback/feature request to Zapier Support to be logged: https://zapier.com/app/get-help

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
ken.a
Userlevel 7
Badge +6

Hi there @cdwyer,

I’m jumping in to see if I can help!

Looking at the API documentation of Stripe the “status” data also includes “open”. Maybe Stripe includes Pending or Incomplete Sessions as well.

https://stripe.com/docs/api/checkout/sessions/retrieve

d5d741866f9a36ac7acea9364a372da9.png
(view larger)

Hopefully, this helps.

cdwyer
Userlevel 1
Badge

Hi there @cdwyer,

I’m jumping in to see if I can help!

Looking at the API documentation of Stripe the “status” data also includes “open”. Maybe Stripe includes Pending or Incomplete Sessions as well.

https://stripe.com/docs/api/checkout/sessions/retrieve

d5d741866f9a36ac7acea9364a372da9.png
(view larger)

Hopefully, this helps.

Yep, that’s correct! But by definition, I would have expected the Checkout Session Completed trigger to automatically ignore/filter out Open, Incomplete, etc. sessions from the test data. Not a huge deal, just felt like a bug or small oversight.

ken.a
Userlevel 7
Badge +6

Hi @cdwyer,

I completely agree that the Checkout Session Completed trigger should not include incomplete sessions or have an option to not include them.

I’d recommend reaching out to our Support Team to create a feature request on your behalf. You can reach our Support Team here: https://zapier.com/app/get-help

In the meantime, you might be able to filter out those incomplete sessions by adding a filter step to your Zap. You can learn more about Filter by Zapier here: https://help.zapier.com/hc/en-us/articles/8496276332557-Add-conditions-to-Zaps-with-filters

Hopefully, this helps! 

 

Reply


Terms & Conditions