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!
+14Hi
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
+6Hi there
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
Hopefully, this helps.
Hi there
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
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.
+6Hi
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!
Hey,
Yeah - just to reiterate, there the action is just built wrong.
I believe that the intention is to mimic exactly the Stripe event checkout.session.completed, which when viewing this event in Stripe, it does not fire on anything but completed sessions.
It’s crazy that this hasn’t been fixed after over a year. I’ve got a zap with Checkout Session Completed, and zapier still fires fires on this trigger when a checkout session is Created, not Completed. It’s totally mislabelled, or totally built wrong.
Please can someone escalate this issue as without robust testing and technical knownledge, this may not be noticed.
Thanks
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
