Best answer

Stripe custom field not appearing in Zap

  • 2 July 2023
  • 7 replies
  • 583 views

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.

 

icon

Best answer by SamB 7 May 2024, 14:48

View original

7 replies

Userlevel 7
Badge +6

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! 😊

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.

 

 

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?

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

Userlevel 7
Badge +6

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!

 

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.. 
 

Userlevel 7
Badge +11

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.

Reply