Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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.

Hello Zapier team,

I’m having an issue connecting Stripe to Glideapps via Zapier.
After a user completes a subscription checkout, the client_reference_id (used to identify the user in Glideapps) is not being pulled into the Zap trigger.

Without this field, the Zap cannot update the correct user record in Glide.

Here’s what I am trying to accomplish:

  • Capture a new successful subscription payment from Stripe.

  • Use the client_reference_id (sent during the Stripe checkout) to match and update the corresponding user record inside Glideapps.

Problem:
In the Zap editor, the client_reference_id is missing.
I can see other fields like customer email and payment status, but the client_reference_id does not appear to map or use.

Steps already checked:

  • Confirmed that client_reference_id is sent from the Stripe Checkout Session.

  • Tested the webhook payload manually; the client_reference_id exists in the payload.

  • Refreshed Zap trigger several times — field still missing.

Attachments:
(Attach a screenshot showing the Zap trigger screen where client_reference_id does not appear)

Thanks in advance for your help! 🚀

Hi there ​@Anderson Baumgartner,

Welcome to the Community! 🎉

Before we dig in further, could you try performing a “Replay Entire Zap” on the errored run? My hunch is that the Checkout Session Completed trigger may be firing too quickly for the Zap to capture the client_reference_id.

After replaying the Zap, please check if the run completes successfully. If it does, you may want to consider adding a Delay by Zapier step to give the Zap a bit more time to capture the client_reference_id before continuing.

You can learn more about “replay entire Zap” here: https://help.zapier.com/hc/en-us/articles/8496241726989-Replay-Zap-runs#h_01HPFJ7K8PAG1KRXND2G5PEWWD

Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!

 

.

Hi there ​@Anderson Baumgartner,

Welcome to the Community! 🎉

Before we dig in further, could you try performing a “Replay Entire Zap” on the errored run? My hunch is that the Checkout Session Completed trigger may be firing too quickly for the Zap to capture the client_reference_id.

After replaying the Zap, please check if the run completes successfully. If it does, you may want to consider adding a Delay by Zapier step to give the Zap a bit more time to capture the client_reference_id before continuing.

You can learn more about “replay entire Zap” here: https://help.zapier.com/hc/en-us/articles/8496241726989-Replay-Zap-runs#h_01HPFJ7K8PAG1KRXND2G5PEWWD

Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!

 

Hi,

Thank you very much for the suggestion!
I tested the "Replay Entire Zap" option as recommended and also added a "Delay by Zapier" step. Unfortunately, this still did not solve the issue.

Here’s what I observed:

  • When I manually test the Zap inside the Zapier editor (using Stripe’s test mode with fake cards), the client_reference_id appears correctly.

  • When I perform a real payment (outside of test mode), the client_reference_id does not appear in the data received by the Zapier trigger.

  • Therefore, the problem does not seem to be related to timing, but rather to a difference in how Stripe behaves between test and live environments.

I have already confirmed that the client_reference_id is correctly sent during the creation of the checkout session in Stripe.

Could you please help me understand why the client_reference_id disappears in the live environment and how I can resolve this?

Thank you in advance for your support and attention! 🚀

Hi ​@Anderson Baumgartner,

 

If you're experiencing issues with the Stripe integration in Zapier, particularly regarding the client_reference_id not appearing in the live environment, there are several key areas to investigate. First, ensure that webhook settings are correctly configured in test and live Stripe environments, as differences here can affect data transmission. Review Stripe logs to ensure the client_reference_id is set correctly during live checkout sessions. In Zapier, confirm that your Zap is triggering on the correct event type for both environments and that field mappings, especially for client_reference_id, are consistent. Also, verify that the correct API keys are being used and that the checkout session creation process includes the client_reference_id in live mode. To further troubleshoot, compare logs in both Stripe and Zapier to identify discrepancies. If the problem continues, contacting Stripe Support can help uncover environment-specific requirements or known issues.

I hope this helps. Please let me know if you have any more questions or issues.
 

Terms & Conditions