Due to GDPR regulations this is the most important Zap to set up - if you have any Zaps that add user’s data to your CRM you MUST also have an active Delete User Zap connected to your SupaPass account. You as the data Controller are legally responsible for the secure storage, handling, and transmission of your user’s personal data, not SupaPass. On receiving a right to be forgotten request you must comply and remove the user from your CRM as well as from the SupaPass database. This Zap must remain connected and active.
Set up the SupaPass Trigger
Choose app and event: Select “Delete User” as the Trigger Event.
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!
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. “End 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.
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 email@example.com
Set Up The Action To Your CRM of Choice
Under Choose app & event select “Unsubscribe Email” (or your CRM’s equivalent), then connect to your CRM account as described above.
Set up action: Select your audience as before. Click on the Subscriber Email field and select Email Address.
That’s it! You can test, and then turn on your Zap!