If you want to use WebinarKit's Zapier integration, please go to Zapier.com in order to set up your Zaps. With our Zapier integration, you can trigger a Zap whenever someone registers for one of your events. You can also register someone for an event using the "New Webinar Registration" action.

Zapier Triggers

If you'd like to trigger another application whenever someone registers for one of your events, you'll need to use the "New Webinar Registration" trigger.

To get started, create a new Zap on Zapier.com.

When prompted to choose an app, search for WebinarKit and select it. For the event, choose "New Webinar Registration". On the next step, you'll need to authorize Zapier to access your WebinarKit account. Once you've given Zapier access, you'll need to choose a webinar that will trigger the Zap.

Once you've selected the webinar from your account, you'll be prompted to test the trigger to make sure the Zap is working correctly. Alternatively you can skip this step.

The final step is to connect your WebinarKit Zap to another application on Zapier. For example, you can choose to send the emails that register for your webinars to an email autoresponder/CRM application using this Zapier integration.

WebinarKit sends along whatever information the registrant provided (email, first name, last name, and phone number) along with the registrant's unique event link and the event date/time (in multiple formats).


Zapier Actions

If you'd like to register someone for one of your webinars when a different application is triggered on Zapier, you'll need to use the "New Webinar Registration" Action.

To get started, create a new Zap on Zapier.com.

Start by selecting WebinarKit as the app and "New Webinar Registration" as the action event. On the next step, select your WebinarKit account. After that, you'll need to select the webinar you want to register people for. Choose your webinar from the drop down, select the date and time you want to register the person for, and for the various other fields (first name, last name, email, etc...), select the data source (based on the data sent from the trigger app).

Please note: If you modify the date(s) of your event inside WebinarKit AFTER setting up your Zap, you must edit your Zap to ensure the "Webinar Time & Date" option is set to the correct time & date for your event.

Once you've finalized the field settings, continue through to test your Zap and that's it!

Regarding phone numbers: If you are passing along a phone number to WebinarKit via Zapier and you want WebinarKit to send text message reminders, you must provide the country code. For example, a US based phone number needs +1 at the beginning so that our system can build the full phone number that would look something like: +19171234567.

Many people have different setups so our system is flexible in how it handles receiving country codes and phone numbers via Zapier.

For example, you can pass the country code separately from the rest of the phone number by using the fields shown in the screenshot below. WebinarKit will combine the country code and the phone number when the Zapier Action is run.

Alternatively, if the phone number you are passing already has the country code, just leave the "Phone Number Country Code" field blank in Zapier and pass the formatted number into the "Phone Number" field as shown below.

Lastly, if the app you are using provides a 2 letter country code like "US" instead of "+1", you can use Zapier's Formatter app to convert the 2 letter country code and phone number into the proper format. Please see the screenshot below of what this would look like.


Regarding time zones: You can also pass a time zone into our Zapier actions.

This setting affects how the date/time of the event session is displayed for the registrant throughout built-in emails, text messages, as well as 3rd party integrations.

For example, if the event session is scheduled for 4 PM US Eastern Time (America/New_York), but the registrant is located in Los Angeles, you can pass "America/Los_Angeles" and the registrant's emails/texts/integrations will show the session date as 1 PM US Western Time.

For the full list of supported time zone values that can be passed into this field, please look at the "TZ identifier" column on the following Wikipedia page: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

Example values that can be given:

If left blank, the time zone defaults to UTC.