Skip to main content

Hey All,

Good Morning - hope you are doing well today. I have a question/scenario where I was wondering maybe if I can your feedback on what I am trying to achieve.

I currently have two Zaps:
 

 

 

Customer Registation:


Successful Payments:


 
The scenario for the two zaps is that when a customer fills out an Airtable form via shareable link, a record is added to the airtable database table, then a Stripe Payment Link is created, and then shared with that customer to the email they used when completing the airtable form. 

Once the payment has been successful, that customer should then receive another email mentioning they are now a registrant of Zoom meeting via Zoom. Zapier automation will automatically register the customer once successfully paid for the program/event. 

 

As the backstory, the overall flow is that I have a list of different programs/events on my website that I want customers to sign up for. This is how I thought about using Zapier automation instead of building something from scratch to interact with both Stripe’s API and Zoom API. So on each of the event listed on the website, there is currently a shareable Airtable link that captures data.

Is there a way to determine the Stripe product in my case events, because there is a different price for the different events eg: Coding for Beginners , price would be $20. 

On a technical level, I want to be able to something a little more robust in terms of making it more dynamic so that Zapier  knows which program or event matches the Stripe product created, and also assign that customer to the correct related Zoom meeting as a registrant ?

 Any thoughts on how I can achieve this ?

Hi @davalgregory 

Good question.


If you need help with the below, then consider hiring a Certified Zapier Expert: https://zapier.com/experts/automation-ace

 

You can use Airtable as a Lookup Table to make the Zaps dynamic:

 

The idea would be to create a relationship of the product/event to Stripe Payment Link and the Zoom Event.

 

Generally you’ll need to use the internal IDs (e.g. Zoom Meeting ID) for each app as part of creating the lookup table.

 

In Airtable you’ll want to create a relational structure, so that records can be linked across Tables.

For example, you’ll want these Tables:

  1. Signups
  2. Products/Events
  3. Stripe Payment Links

Stripe Payment Links would be linked to Products/Events.

Products/Events would be linked to Signups.

Therefore, you can derive that for a Signup with Product/Event ABC, it should use Stripe Payment Link XYZ.

 

You may need to use Airtable Automations to be assist.

 

If you have a set # of products/events, then you shouldn’t need to create a new Stripe Payment Link for each new record in Airtable.

 

Instead create 1 Stripe Payment Link per product/event, then use additional tracking parameters.

 

Stripe Payment Links can include UTM parameters for tracking additional data points: https://stripe.com/docs/payment-links/url-parameters

 

That way when a successful Stripe Payment happens it will include the metadata of the tracking parameters.

 

You can use that to then find the Airtable record, which will indicate the Zoom Meeting ID to use.