New Subscription

Callum Updated by Callum

Set up the SupaPass Trigger

  1. Choose app and event: Select “New Subscription” as the Trigger Event.
  1. Choose account: select the account you want to use.
Top Tip: Don’t forget to name each connection clearly - we suggest using the app’s name as the connection name!
  1. Set up trigger: Under the Zap Name field give your Zap a name - make it descriptive so you can find it easily in the logs inside your SupaPass account dashboard e.g. “New Subscription”
WARNING: Leave the Receive Historic Data On First Trigger field set to “False” - there’s a warning note underneath explaining why. We recommend only changing this if you are familiar with using Zapier and don’t have many historic users to pull into your CRM.
  1. Test Trigger: Click continue, just to check everything is working. If not, check all the previous steps carefully, and if the problem persists contact us at

Set Up The Action To Your CRM of Choice

  1. Once again select the “Add/Update Subscriber in Mailchimp” (or your CRM’s equivalent), connect to your CRM account as described above.
  2. Set up action: Select your audience as before. The New Subscription trigger offers more fields that you could consider using as tags. Again you can see a full list under the “Custom” tab in the dropdown when clicking on the tag field. 
  3. Select Email Address under the Subscriber Email field - it is mandatory.
  4. Under the Tag(s) field we recommend using these 4 fields as tags: 
    1. Product Name
    2. Coupon Code
    3. Free Trial
      Coupon Code and FreeTrialApplied will only appear as tags in your CRM if the use has a code or a free trial applied to their subscription, keeping your CRM interface clutter free.
    4. Payment Provider
      Payment Providers are coded as follows : ‘S’ = Stripe; ‘A’ = Apple, ‘G’ = Google and show you where your users made their subscription from (Web, iOS and Android apps respectively).

You do not have to assign first name or any user-related data - if the New Subscription trigger is firing, your user is already in your CRM!

When you are finished setting up the action should look like this.

Test and turn on!

How did we do?

Update User

End Subscription