Skip to main content
Best answer

Stripe custom field not appearing in Zap


kwhitmore

I have a Stripe checkout page (see screenshot) that has “email”, “name on card”, and two custom fields for “first name” and “last name”. By default Stripe brings through “name on card” as “name” and we were using that with a splitter function in our zap. However, sometimes the name on card is just an initial .e.g “J Adams” so our CRM was bringing through “J” as the first name. 

We added First Name and Last Name to the Stripe checkout page however these two custom fields are not coming through to Zapier. I have loaded a new customer from stripe and it sees it in the test data in Stripe. Any help appreciated. I’ve tried recreating the zap from scratch and it’s not pulling through.

 

Best answer by SamBBest answer by SamB

Hey folks 👋

I checked on this end and I can see that Support created a new feature request for custom fields to be fully supported in the New Customer (Stripe) trigger but it hasn’t been implemented yet. We can’t make any promises around when it would be implemented by but everyone in the thread here has had their vote added to that feature request which will help to increase it’s priority. And it will allow us to send you all an email notification as soon as it’s been resolved.

In the meantime, it sounds as though @lockeyg was able to access the missing custom fields by triggering from a webhook notification for the new customer created events. If you’re interested in setting up that workaround, Stripe have a Using webhooks with subscriptions guide, and we have a Trigger Zaps from webhooks guide that you’ll want to reference. Please note, that Webhooks are an advanced feature that are only available to paid plans so may not be an ideal solution if you’re on a Free plan.

The other alternative as suggested by Ken would be to use the New Event Stripe trigger instead and select the customer.created event type to see if that trigger will also give access to the desired custom fields. 

@Zap-tmw - the New Customer trigger would only trigger when a new customer is created, it wouldn’t run for recurring customers making a new purchase. Perhaps you could trigger a Zap when a payment is made instead? I’d suggest checking out the New Charge or New Payment Stripe triggers. I couldn’t find any documentation on this end to confirm whether your custom fields would be available for those triggers but it may be worth testing it out on your side in case they are!

Thanks for everyone’s continued patience in the meantime.

View original
Did this topic help you find an answer to your question?

15 replies

ken.a
Forum|alt.badge.img+6
  • Zapier Staff
  • 6301 replies
  • July 3, 2023

Hi there @kwhitmore,

Welcome to the Community! 🎉

I did some digging into this, and it seems like custom fields are not yet supported by the Stripe integration. Also, I haven’t found any open feature request to support custom fields on the “New Customer” trigger.

I recommend reaching out to our Support team to have them create a feature request on your behalf. You can contact our Support team here: https://zapier.com/app/get-help

7cf4459bc2c0101f1790f9db385a8e46.png
(view larger)

Hopefully, this helps! 😊


lockeyg
  • New
  • 1 reply
  • August 1, 2023

I ran into a similar issue today. After swapping over to using the webhook from Stripe, I was able to see all of my custom fields.

 

 


John_DOE
  • New
  • 1 reply
  • August 14, 2023
lockeyg wrote:

I ran into a similar issue today. After swapping over to using the webhook from Stripe, I was able to see all of my custom fields.

 

 

Lockeyg, happy to hear that you managed to get it working. How did you swapped to using webhook from Stripe?


  • New
  • 3 replies
  • April 26, 2024

Hello @ken.a 
It’s been over 9months since the original post, 
I’m a new user running through the exact same issue, any news on this issue with the custom fields?
Thanks


ken.a
Forum|alt.badge.img+6
  • Zapier Staff
  • 6301 replies
  • April 26, 2024

Hi @Zap-tmw,

Unfortunately, there are no updates regarding the feature request. However, you can use might be able to use the “New Event” trigger for this and use the customer.created in the “Events Type” field to see if it’ll pull the custom fields you’re looking for.

I'll be keeping an eye out for your response!

 


  • New
  • 3 replies
  • April 30, 2024

Thanks, but doesn’t work as some of these customers are recurring customers from past purchases. 
So if I use “new customer” as a trigger, it might miss some new sales from recurring customers. 

it’s really strange to give the possibility to have custom fields, and not be able to retrieve the family name separately at all.
The problem has been around for a long time, many threads online and on here show it’s been a problem for years. How’s this not fixed yet? It’s not a major feature tbh & it’s essential for automations following up on sales. 

Looking forward for a fix on this asap, thanks.. 
 


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7274 replies
  • Answer
  • May 7, 2024

Hey folks 👋

I checked on this end and I can see that Support created a new feature request for custom fields to be fully supported in the New Customer (Stripe) trigger but it hasn’t been implemented yet. We can’t make any promises around when it would be implemented by but everyone in the thread here has had their vote added to that feature request which will help to increase it’s priority. And it will allow us to send you all an email notification as soon as it’s been resolved.

In the meantime, it sounds as though @lockeyg was able to access the missing custom fields by triggering from a webhook notification for the new customer created events. If you’re interested in setting up that workaround, Stripe have a Using webhooks with subscriptions guide, and we have a Trigger Zaps from webhooks guide that you’ll want to reference. Please note, that Webhooks are an advanced feature that are only available to paid plans so may not be an ideal solution if you’re on a Free plan.

The other alternative as suggested by Ken would be to use the New Event Stripe trigger instead and select the customer.created event type to see if that trigger will also give access to the desired custom fields. 

@Zap-tmw - the New Customer trigger would only trigger when a new customer is created, it wouldn’t run for recurring customers making a new purchase. Perhaps you could trigger a Zap when a payment is made instead? I’d suggest checking out the New Charge or New Payment Stripe triggers. I couldn’t find any documentation on this end to confirm whether your custom fields would be available for those triggers but it may be worth testing it out on your side in case they are!

Thanks for everyone’s continued patience in the meantime.


  • New
  • 3 replies
  • May 9, 2024

Hi, thanks for keeping us updating. 

These custom fields were crucial to the automation flow & databases inputs, so we’ve had to move our payments on a diff platform where we could collect these key custom fields, 

Thanks again!
 


  • New
  • 1 reply
  • June 28, 2024

(...)

The other alternative as suggested by Ken would be to use the New Event Stripe trigger instead and select the customer.created event type to see if that trigger will also give access to the desired custom fields. 

 

This does not work. Custom fiels are over no stripe trigger available.

Just change payment plattform, if you need these fields.


  • New
  • 3 replies
  • October 29, 2024

HI all Still no update on this ?? Why is an important thing like this not possible in Zapier? Any solution to get the custom fields also for recurring plans ?

Thank you


JammerS
Forum|alt.badge.img+6
  • Zapier Staff
  • 2188 replies
  • October 30, 2024

Hi @Torsten

 

We sincerely apologize, but we don’t have an update yet. Hence, you will receive an email once an update is available. I also added you to the feature request list so that you and everyone above will be added to the mailing list. Thank you.


  • New
  • 2 replies
  • November 13, 2024

I'm having the same issue with Zapier not picking up custom fields from a Stripe Checkout, any updates or solutions?


JammerS
Forum|alt.badge.img+6
  • Zapier Staff
  • 2188 replies
  • November 14, 2024

Hi @John22B,

 

We apologize for the inconvenience. Hence, I added you to the feature request list, and we’ll email you once an update is available. Thank you.


  • Beginner
  • 2 replies
  • February 3, 2025

How is this not fixed yet should be such an easy integration and has been a clear problem for over 2 years? Please can you add me to the list too to be notified when fixed (if ever)


JammerS
Forum|alt.badge.img+6
  • Zapier Staff
  • 2188 replies
  • February 5, 2025

Hi ​@willsola,

 

We really do apologize for the inconvenience. I’ve added your vote for this feature request, and we’ll notify you via email once an update is readily available. Thanks.