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.

Hi nice people!

Let’s start by saying that I have searched for this specific question, but couldnt find my answer (yet).

Some context to start with:
I am using a sign up form on a website, which redirects to a Stripe Payment link after submitting the form. The Stripe Payment link consists of a Stripe Subscription that automatically charges the user each year (using iDeal as a payment method). This all works like a charm.

What do I want to achieve with Zap(s):
Create a Zap that sends a unique welcome email the FIRST time a user gets successfully charged for their subscription. BUT, and here is where I struggle, send another DIFFERENT email the next year the user gets (automatically) charged again. And the same thing the year after that year, etc. etc.

So what it comes down to is: how can I recognise if a successful Stripe charge for a Stripe subscription is a first time charge, or a second time, or third etc etc?

 

Hope you can help me out!

Cheers, Matt

​@Mattieman 

I am not sure it is possible. Access to the Stripe API isn’t that hard with the API Request block. The hard part is trying to get enough information to make it useful for you. 

If the payment link isn’t linked to a subscription it won’t record the information needed. Payment links don’t always create customers or save useful information. Well certainly not on the Stripe account I was looking at. 

You could look at when the client record was created and convert the unix time into something understandable and use that as a rough guess. But that depends on whether the links, customers and subscriptions are connected or not. 

It may be better to start from scratch and add the clients into a CRM or spreadsheet on first purchase and use that as a check in the following years. It may be easier to do it manually to start off checking inside stripe to see if there are records of payments. 

The data is probably there it’s just whether or not we can get at it.

Hi ​@Mattieman 

Probably makes sense to log the data into one of these apps to use as a lookup table for using in the automations:

  • Airtable
  • Zapier Tables
  • GSheets


Idea being to log each of the charges for a subscription, so you can get a count of subscription charges to determine how many subscription cycles a customer has done.

In Stripe for a Customer’s Subscriptions there are UNIX timestamps that can be used to see when then Subscription was created and the period start/end, which could be used to help your logic.
 

 

Reply


Terms & Conditions