Zapier lets you connect Livestorm to hundreds of other web services. Automated connections called Zaps, set up in few minutes without any code required, can automate your day-to-day tasks and build workflows between apps that otherwise wouldn't be possible.
Each Zap has a Trigger, where your information comes from and which causes one or more Actions in other apps, where your data gets sent automatically.
IN THIS ARTICLE
Set up Zapier With Livestorm
Setting up Zapier with Livestorm is very easy. No need to code, just follow these steps:
1Sign up on Zapier(or Log in if you already have an account).
2After you've logged in, click on MAKE A ZAP on the left menu.3On the Trigger section, search for Livestorm as an App Event and select it.4Then choose a Trigger Event (you can change it later), click on Continue and then Sign in to Livestorm.5A window will open asking for the Zapier Token to access your Livestorm account.6Click on Click here to get your Zapier token on your Livestorm account.
(or go to your Livestorm Dashboard > Account Settings > Integrations > Zapier)7Copy the Zapier token, paste it on Zapier and click on Yes, Continue.
You only need to add the Zapier token once.
8You're now good to create your first Zap!
Create Your First Zap
Let's now create a Zap to connect Livestorm with another app of your choice, automate a workflow and save you time!
- 1
- On your Zapier landing page, click on MAKE A ZAP.
- 2
- Name your zap at the top left corner.
- 3
- Choose a trigger with Livestorm as an App & the Trigger Event you want, and click on Continue.
A trigger is an event that starts a Zap with a specific app. You can only choose 1 trigger per Zap. The trigger tells the Zap "when" to begin doing something.
We provide the following triggers with Livestorm app:
- New Registrant
- Event Published
- Session Started
- Session Ended
- Registrant Attended
- Registrant Didn't Attend
- Registrant Watched Replay (also applies for on-demand events)
- New Session Added (also applies when a new published event is created from scratch)
- 4
- Choose your Livestorm account ( or sign in to set up your Livestorm account with Zapier) and Continue.
- 5
- Test trigger to make sure the trigger works correctly and Continue.
- 6
- Now you get to select the action you want for your Zap with an App Event and an Action Event.
An action is a task that a Zap performs after it's triggered. The action tells the Zap "what" to do. You can add as many actions as you need in a Zap.
7Test and Continue to check if your action is working properly.8Finally, Turn on Zap! You're Zap is now ready! 🎉In this example, we're showing you how to create a new Spreadsheet Row in Google Sheets whenever someone registers for an event on Livestorm.
Zap Examples
You might wonder what Zaps would be useful with Livestorm as there are plenty of options. We provide the following actions:
- Create Event
- Update Event
- Remove Event
- Create Session
- Update Session
- Remove Session
- Find Session
- Create Registrant
- Remove Registrant
- Find people (for a specific event or session)
Here are a few examples to give you some ideas of workflows that you could set up:
- From Livestorm to Others Apps
| Trigger App | Trigger Event | Action App | Action Event |
| Livestorm | New Registrants | Google Sheets | Create Spreadsheet Row(s) |
| Livestorm | New Registrants | Hubspot | Create Contact |
| Livestorm | Session Started/ Ended | Slack | Send Channel Message |
| Livestorm | Event is Published | Google Calendar | Create Calendar |
- From Others Apps to Livestorm
| Trigger App | Trigger Event | Action App | Action Event |
| HubSpot | New Form Submission | Livestorm | Create Registrant |
| Typeform | New Entry | Livestorm | Create Registrant |
| Google Sheets | New Spreadsheet Row | Livestorm | Create Registrant |
With Zapier, you can also bulk import registrants from another source, use your own landing page to register attendees, host paid/private events, track conversions on your registration pages, and much more!
Debug Your Zaps
If you're missing data or your Zap didn't run as expected, it's often due to a misconfiguration. You will need to debug your Zap to make it work again from your Zap History.
- 1
- Go to your Zap History that runs a log of your tasks.
- 2
- Click on Zap runs.
- 3
- Filter your Zaps by Status to see which ones weren't successful.
- 4
- Click on the Zaps that are listed and check the Data in & Data Out.
-
- 5
- You'll find the error in the history of the Zap and will be able to Edit This Step to fix it.
