Migrate Your Zaps from Livestorm v1 to v2

Our Livestorm connector with Zapier has improved. We've launched a new version of it. đŸŽ‰

Your old Zaps still work at the moment but you will have to migrate them from our Livestorm v1 to v2 by March 15th, 2022. You can see if your Zap uses the Livestorm v1 if there's a " DEPRECATED" mention next to Livestorm.

After March 15th, 2022, your Zaps won't work anymore if you haven't migrated them from Livestorm v1 to v2.

In order to migrate your Zaps, you need to change all the information that implies Livestorm data and which is used in the Trigger and in the Action of your Zap.

There's nothing complicated and we're going to show you how to do it step by step. You can also contact our support team if you have any questions on help@livestorm.co. They will be very happy to help you. đŸ˜€

IN THIS ARTICLE


Migration Video Tutorial

In this video, we're going to show you how to migrate a Zap that creates a spreadsheet row in Google Sheets when there's a new registrant to an event. 

Your Zap might not be configured exactly the same way or connected with the same app but the principle is the same.

1
Copy your Zap to migrate it to Livestorm v2. 
2
Take a look at the current configuration and keep it in mind.
3
Change the Trigger app with the new Livestorm v2.
4
Set the Trigger Event to New Registrant.
5
Choose your Livestorm account (or + Connect a new account).
6
Set up the new Trigger to match the previous one.

If you want to take into account every session of the event, leave the "Filter By Session" field empty, otherwise choose a specific session.

7
Set up the new Action to match the previous one.
8
Rename your old Zap and turn it off.
9
Rename your new Zap.
10
Your Zap is good to go now! đŸŽ‰

Migrate the "New Registrant" Trigger

We're going to show you here how to migrate a Zap that creates a spreadsheet row in Google Sheets when there's a new registrant to an event. 

Your Zap might not be configured exactly the same way or connected with the same app but the principle is the same.

1
Copy your Zap to migrate it to Livestorm v2. 

2
Take a look at the current configuration and keep it in mind.
3
Change the Trigger app with the new Livestorm v2.
4
Set the Trigger Event to New Registrant.
  • BEFORE

  • AFTER

5
Choose your Livestorm account (or + Connect a new account).
6
Set up the new Trigger to match the previous one.

If you want to take into account every session of the event, leave the " Filter By Session" field empty, otherwise choose a specific session.

  • BEFORE

  • AFTER

7
Set up the Action to match the previous one.
  • BEFORE

  • AFTER

8
Rename your old Zap and turn it off.

9
Rename your new Zap.

10
Your Zap is good to go now! đŸŽ‰

Migrate the "Webinar Ends" (With Line Items Support) Trigger

We're going to show you here how to migrate a Zap that creates spreadsheet rows in Google Sheets all at once when an event ends.

Your Zap might not be configured exactly the same way or connected with the same app but the principle is the same.

1
Copy your Zap to migrate it to Livestorm v2. 

2
Take a look at the current configuration and keep it in mind.
3
Change the Trigger app with the new Livestorm v2.
4
Set the Trigger Event to Session Ended.
  • BEFORE

  • AFTER

5
Choose your Livestorm account (or + Connect a new account).
6
Set up the Trigger.

Select All at once in the "Include Participants" field.

7
Set up the Action to match the previous one.
  • BEFORE

  • AFTER

8
Rename your old Zap and turn it off.

9
Rename your new Zap.

10
Your Zap is good to go now! đŸŽ‰

Migrate the "Webinar Ends" Trigger

We're going to show you here how to migrate a Zap that sends a Slack message when a specific event ends.

Your Zap might not be configured exactly the same way or connected with the same app but the principle is the same.

1
Copy your Zap to migrate it to Livestorm v2. 

2
Take a look at the current configuration and keep it in mind.
3
Change the Trigger app with the new Livestorm v2.
4
Set the Trigger Event to Session Ended.
  • BEFORE

  • AFTER

5
Choose your Livestorm account (or + Connect a new account).
6
Set up the Trigger.

Select One by One in the "Include Participants" field.

7
Set up the Action to match the previous one.
  • BEFORE

  • AFTER

8
Rename your old Zap and turn it off.

9
Rename your new Zap.

10
Your Zap is good to go now! đŸŽ‰

Migrate the "Webinar Starts" Trigger

We're going to show you here how to migrate a Zap that sends a Slack message whenever an event starts.

Your Zap might not be configured exactly the same way or connected with the same app but the principle is the same.

1
Copy your Zap to migrate it to Livestorm v2. 

2
Take a look at the current configuration and keep it in mind.
3
Change the Trigger app with the new Livestorm v2.
4
Set the Trigger Event to Session Started.
  • BEFORE

  • AFTER

5
Choose your Livestorm account (or + Connect a new account).
6
Set up the Trigger.

Leave the  "Filter by Event" field when you want to target every event and not a specific one.

7
Set up the Action to match the previous one.
  • BEFORE

  • AFTER

8
Rename your old Zap and turn it off.

9
Rename your new Zap.

10
Your Zap is good to go now! đŸŽ‰

Migrate the "Webinar is Published" Trigger

We're going to show you here how to migrate a Zap that sends a Slack message when an event is published.

Your Zap might not be configured exactly the same way or connected with the same app but the principle is the same.

1
Copy your Zap to migrate it to Livestorm v2. 

2
Take a look at the current configuration and keep it in mind.
3
Change the Trigger app with the new Livestorm v2.
4
Set the Trigger Event to Event Published.
  • BEFORE

  • AFTER

5
Choose your Livestorm account (or + Connect a new account).
6
Set up the Trigger.

The "Filter By Event Title" field should be empty.

7
Set up the Action to match the previous one.
  • BEFORE

  • AFTER

8
Rename your old Zap and turn it off.

9
Rename your new Zap.

10
Your Zap is good to go now! đŸŽ‰
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.