This guide walks you through how to connect SupaPass Webhooks to Zapier, allowing you to automate workflows between SupaPass and thousands of third-party apps like Mailchimp, ClickFunnels, and more.
đ What Youâll Need Before You Start
Before you can start using this guide, there a few things you require to have:
You will need the Webhooks addon, which you can access via the addon screen in your dashboard.
âYou need a Zapier account with Premium access to use the Webhooks trigger. If you don't have a Zapier account yet, click here to set one up
Now let's dive into the steps you need to complete, to get your SupaPass Webhook working with Zapier.
Step 1: Create a Zap with Webhooks by Zapier
Youâll start in Zapier by setting up a new automation in Zapier, known as a âZap.â The first part of the Zap is the trigger - what starts the automation. In this case, the trigger will be a webhook from SupaPass.
Click âCreate Zapâ.
For the trigger app, search for and select Webhooks by Zapier.
then select the trigger event: Catch Hook.
đĄ Good to know Catch Hook gives you a unique webhook URL where SupaPass will send data.
Step 2: Copy the Zapier Webhook URL
Zapier gives you a unique URL to receive data from SupaPass. Youâll need to copy this URL and paste it into your SupaPass dashboard so the two platforms can communicate.
Zapier will now generate a unique URL.
Click Copy.
Step 3: Add the Webhook to SupaPass
Now youâll tell SupaPass where to send its data - the URL you copied from Zapier. Youâll also select which events (like a subscription update or a user profile change) should trigger the webhook.
Go to your SupaPass Admin Dashboard.
Navigate to Integrations â Webhooks.
Click âCreate Webhookâ.
Paste the Zapier webhook URL into the Endpoint field.
Select the events you want to listen to. Examples are:
User Profile Created
User Profile Updated
Subscription Created
Subscription Updated
Subscription Cancelled
đ§ Tip: Even if youâre not using all events right now, itâs helpful to collect them for future use.
Step 4: Trigger a Test from SupaPass
Zapier needs a sample of real data from SupaPass to understand the structure of the webhook. In this step, you'll send a test so Zapier can pull that data into your Zap.
In SupaPass, after creating your webhook, click âTestâ.
Zapier (which is listening) will catch the test data.
Step 5: Review the Webhook Payload in Zapier
This step helps you understand what data SupaPass is sending. Youâll see user information, subscription data, and more - which you can use to power automations.
In Zapier, the test data should now show.
Open the payload to view all available fields. Examples are:
payload.user.email
payload.user.first_name
payload.subscriptions
payload.user.consent.marketing
â (Use this to respect marketing opt-ins)
payload.user.notification_preferences
Any custom fields (if enabled)
đĄď¸ Key Rule: Always check consent.marketing before initiating marketing automation in tools like Mailchimp.
To continue click on âcontinue with selected recordâ
Step 6: Connect to a Third-Party App
Now that the trigger is set up and Zapier is receiving data from SuapPass, we need to connect it with the third-party app or tool where you require to do something with that data. For these instructions we are using Mailchimp as an example, but the instructions should apply to any app or tool that you select in the list that Zapier offers.
Add an Action to your Zap.
Choose your app (e.g., Mailchimp).
Screenshot placeholder - webhooks to zapier - connect to mailchimp
Then select an event, in this example we will âAdd/Update Subscriberâ.
Then select an account to connect it to (your account details should already be available to select). And click continue.
In the next settings screen, select a value for the audience
Then continue to map SupaPass fields to the Mailchimp fields (or whatever tool you selected):
Mailchimp Field | SupaPass Field |
Email Address | payload.user.email |
First Name | payload.user.first_name |
Last Name | payload.user.last_name |
Phone Number | payload.user.telephone |
Address Info | payload.user.address.* |
Date of Birth | payload.user.custom_fields.date_of_birth (optional) |
â ď¸ Caution: Avoid sending sensitive data unless absolutely necessary (like Date of Birth).
Step 7: Test and Publish Your Zap
Now youâll test everything to make sure the automation is working as expected. Once you're happy, youâll publish and activate your Zap.
Run a test to make sure the data flows correctly.
If successful, click âPublish Zapâ.
Make sure your Zap is turned on!
Tips & Resources
Use filters in Zapier to distinguish between new, renewed, and ended subscriptions based on the end_at timestamp in the payload.
Explore SupaPassâs custom fields to enrich your data and personalize automations.
You can use this setup to connect SupaPass to thousands of apps on Zapier.
đNeed Help?
SupaPass Webhooks live under Integrations in the Admin Dashboard.
Make sure youâve connected your Zapier account to SupaPass before testing.
You can reach out to our Success team by starting a chat đŹin the bottom right corner.
FAQ
What is a webhook, and why do I need one?
What is a webhook, and why do I need one?
A webhook is a way for SupaPass to send real-time data (like when a user subscribes or updates their profile) to another service â like Zapier. You need it if you want SupaPass to automatically trigger actions in tools like Mailchimp, Google Sheets, CRMs, etc.
Do I need a paid Zapier account to use webhooks?
Do I need a paid Zapier account to use webhooks?
Yes. The Webhooks by Zapier feature requires a Zapier Premium account.
Where do I find the webhook URL in Zapier?
Where do I find the webhook URL in Zapier?
When you create a new Zap with the trigger set to âWebhooks by Zapier â Catch Hookâ, Zapier will generate a unique webhook URL. This is the URL you copy and paste into the SupaPass Webhooks section.
đ Zapier â Create Zap â Webhooks by Zapier â Catch Hook â Copy URL
What events can I listen to in SupaPass?
What events can I listen to in SupaPass?
You can choose to receive webhook data for events like:
User Profile Created
User Profile Updated
Subscription Created
Subscription Updated
Subscription Cancelled
You can select multiple events when setting up your webhook in the SupaPass dashboard.
My Zapier test isn't showing any data â what should I do?
My Zapier test isn't showing any data â what should I do?
Make sure to:
Click "Test" on the webhook in the SupaPass dashboard.
Ensure the webhook is saved and enabled.
Wait a few seconds for Zapier to receive the test data.
If you still donât see data, double-check that:
You used the correct Zapier webhook URL.
The SupaPass webhook includes events with data (e.g., not empty test users).
Youâre viewing the âTest Triggerâ step in Zapier.
What fields are included in the webhook data?
What fields are included in the webhook data?
The webhook payload includes:
User Info: name, email, address, phone
Subscription Info: start and end dates
Consent Info: marketing opt-in status
Notification Preferences
Custom Fields (if youâve set them up in SupaPass)
đ Most of this data is nested under payload.user and payload.subscriptions.
How do I make sure I only send marketing emails to users who opted in?
How do I make sure I only send marketing emails to users who opted in?
Check the field:
âpayload.user.consent.marketing
Only send marketing messages if this field is true. This helps you stay compliant with data privacy laws and respect your usersâ preferences.
How do I map SupaPass data to fields in another app (like Mailchimp)?
How do I map SupaPass data to fields in another app (like Mailchimp)?
Zapier will automatically show the available fields from SupaPass. You can map:
Email â
payload.user.emailFirst Name â
payload.user.first_nameLast Name â
payload.user.last_namePhone â
payload.user.telephoneAddress â
payload.user.address.line_1, etc.
Use the search bar in Zapierâs field mapping tool to quickly find what you need.
Whatâs the difference between consent.marketing and notification_preferences?
Whatâs the difference between consent.marketing and notification_preferences?
consent.marketing: Indicates if the user has agreed to receive marketing messages (â Use this to filter email campaigns)notification_preferences: Includes settings like email alerts and push notifications â more about in-app behavior.
Can I trigger different Zaps for different event types?
Can I trigger different Zaps for different event types?
Yes! You can either:
Create separate Zaps for different webhook events (e.g., one for
subscription.created, another forsubscription.updated)Or use Zapier filters to branch logic within a single Zap.
What if I want to filter data, like only acting on cancelled subscriptions?
What if I want to filter data, like only acting on cancelled subscriptions?
Use Zapierâs Filter step to check specific fields â for example:
payload.subscriptions[].ends_atis less than the current timestamp â subscription endedpayload.user.consent.marketingis true â user opted in
A dedicated guide is coming soon.








