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.
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
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
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.
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.
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.
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,
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.
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 ?
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.
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)
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.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More about cookies
Customize which cookies to allow
Marketing cookies
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Social media cookies
label
These cookies are set by a range of social media services that we have added to the site to enable you to share our content with your friends and networks. They are capable of tracking your browser across other sites and building up a profile of your interests. This may impact the content and messages you see on other websites you visit. If you do not allow these cookies you may not be able to use or see these sharing tools.
Analytics/performance cookies
These cookies enable the website to provide enhanced functionality and personalization, and allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. These cookies may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly and we will not know how you are using our site.
Functional cookies
label
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
Essential cookies
Always active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.