Resources · Zapier integration

Livestorm Zapier integrationAutomate Livestorm with Zapier.

The Livestorm Zapier integration covers the full life of a webinar: 7 triggers, 8 actions and 2 searches. Registrations, attendance, replays, sessions and events can all start or receive a Zap, and every trigger fires instantly.

See the 17 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Livestorm Zapier integration actually does

Livestorm is a platform for webinars and online events. Zapier, the service that connects your apps without code, can react to what happens around those events, such as a registration or a no-show, and can create, reschedule or remove events, sessions and registrants for you.

Three results come up most. A second chance for no-shows: Registrant Didn't Attend starts a Zap the moment a session ends, and Create Registrant puts that person on the next session. A follow-up that matches what people did: Registrant Attended and Registrant Watched Replay separate live attendees from replay viewers, so each group gets the message that fits. A calendar that runs itself: Create Session and Update Session schedule or move sessions from another tool, without opening Livestorm.

Every one of the seven triggers is instant: Livestorm tells Zapier as soon as the event happens, so even on the free plan nothing waits for a timed check.

What Zapier does not do here: it does not touch the content of a session, such as polls, chat messages or questions, beyond switching those tabs on or off on an event. And Remove Event takes every session of the event with it, so it is no tool for tidying one date. For another platform's take on the same app, see our Livestorm Make integration page.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, each explained once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap, like a new registrant. Once the Zap is switched on, Zapier waits for that event.
Action
What the Zap does once started: create, update or remove something. Livestorm offers eight of them on Zapier.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance of your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer set by your plan. An instant trigger is pushed by the app the moment the event happens.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and quietly stops it otherwise.
Search step
A step that looks up something that already exists, such as a session, so the next steps can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter, a search or a second action makes it one, and it needs a paid plan.
Cost

What a Livestorm Zap really costs

Livestorm is not a premium app: the free plan accepts it. Zapier counts tasks, and only successful actions are billed.

  • Livestorm premium appNo, free plan works
  • Livestorm triggers7, all instant
  • Free plan100 tasks per month
  • Search or filterMakes the Zap multi-step

The seven triggers never cost a task, however many people register or attend. Each action that goes through is one task; a failed one is not counted. The free plan gives 100 tasks a month, in Zaps of two steps. As every Livestorm trigger is instant, the interval grid below does not slow them down, even for free. The limit sits elsewhere: finding a session before registering someone, or filtering who gets a follow-up, adds a step. A search or a filter turns the Zap multi-step, which means a paid plan.

Connect

Connect your Livestorm account to Zapier

  1. 01

    Add the connection

    In Zapier, open Apps and click + Add connection. In the dialog, type Livestorm in the search box and pick it from the list of results right under the box.

  2. 02

    Sign in to Livestorm

    Click Add connection. A new tab opens on Livestorm: sign in with the account that runs your events, so the Zap sees the same events and sessions you do.

  3. 03

    Grant access

    Allow Zapier to access that Livestorm account. The connection then joins your Apps list and is reused by every Zap that listens to Livestorm or writes into it.

First Zap

Your first Livestorm Zap, step by step

GoalWhen someone misses a session, register them for another session of the same event, and stop when the event has no other session.

  1. 01

    Create the Zap and choose the trigger

    Create a Zap, pick Livestorm and Registrant Didn't Attend. Test it: Zapier brings back the three most recent no-shows, so you build on a real one.

  2. 02

    Find the next session

    Add Livestorm again with Find Session, listed under SEARCH. Set the Event field to the event of the no-show. This search makes the Zap multi-step, so paid.

  3. 03

    Decide what happens if nothing is found

    Leave Successful if no search results are found? on its default if an event with no other session should stop the Zap there, with nobody registered.

  4. 04

    Register the person

    Add Create Registrant. Map the Event from the trigger and the Session from the search step, then test and check the registration in Livestorm.

  5. 05

    Publish

    Click Publish to switch the Zap on. Only no-shows from sessions ending after that moment are handled; earlier ones are not picked up.

Triggers

The 7 Livestorm triggers

7 events start a Zap when something happens in Livestorm, and 7 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Registrant

Instant trigger

In Zapier“Triggers when a new participant register for an Event”

Starts the Zap each time someone signs up for one of your events. It is the earliest signal you get from a future attendee.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a SaaS marketing team that wants every webinar sign-up added to its CRM as a lead, with the event name attached.
Watch out
it only catches registrations made after the Zap is published; people already signed up stay outside.
2

Registrant Attended

Instant trigger

In Zapier“Triggers when a registrant attended an Event Session that just ended”

Fires for each registrant who attended a session, once that session has just ended. It tells you who really showed up live.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a sales team that calls only the people who sat through the product demo, while the session is still fresh.
Watch out
it waits for the end of the session, so do not expect it while the webinar is still running.
3

Registrant Didn't Attend

Instant trigger

In Zapier“Triggers when a registrant didn't attend an Event Session that just ended”

Runs for each registrant who did not attend a session that has just ended. The mirror of the previous trigger, and often the more useful one.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an online course creator who sends the replay link to no-shows, or registers them for the next session.
Watch out
if the person later watches the replay, that is a separate event, covered by Registrant Watched Replay.
4

Registrant Watched Replay

Instant trigger

In Zapier“Triggers when a registrant has watched an replay of an Event Session”

Goes off when a registrant has watched the replay of a session. It catches the people who came late, on their own schedule.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a training company that wants replay viewers moved to a separate nurture list from live attendees.
Watch out
whether registrants can reach the recording is an event setting, Recording public?, that Create Event and Update Event both carry.
5

Session Created

Instant trigger

In Zapier“Triggers when a session is created”

Reacts when a new session is created on one of your events. Each new date of a recurring webinar shows up here.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a community manager who wants each new session posted in the team chat as soon as it is scheduled.
Watch out
a Zap on this trigger that runs Create Session sets itself off again and again, and burns your tasks fast.
6

Session Ended (People Included)

Instant trigger

In Zapier“Triggers when an Event Session ends and returns the people of the session”

Fires when a session ends and brings back the people of that session with it. One run per session, not one per person.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an events lead who wants one summary per session posted to a shared sheet, rather than a line per attendee.
Watch out
if you need one action per person, the attended and didn't attend triggers fit better.
7

Session Started

Instant trigger

In Zapier“Triggers when an Event Session starts”

Triggers the moment a session of an event starts. Useful for anything that should happen while people are joining.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a support team lead who wants a we are live message sent to the internal channel so colleagues can join and answer questions.
Watch out
it says nothing about who joined; attendance comes only once the session ends.
Actions

The 8 Livestorm actions

Livestorm gives you 8 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Event

Action

In Zapier“Creates a new Event”

Creates a whole new event in Livestorm, with its title, owner, status and a dozen required settings for recording, registration pages and the chat, questions and polls tabs.

When to use it
an agency that launches the same webinar format for each client from a project tool.
Watch out
the owner needs the host role, and you choose whether the event stays a draft or goes live.
2

Create Registrant

Action

In Zapier“Registers someone for a specific Event Session”

Registers a person for a specific session of an event. You pick the event, then the session, both required.

When to use it
a partner program that signs up every new partner to the onboarding webinar without asking them to fill in a form.
Watch out
the session is a required field, so when the trigger only gives the event, a Find Session step before it supplies one.
3

Create Session

Action

In Zapier“Schedules a new Session to an Event”

Schedules a new session on an existing event. It needs the parent event, a date and a timezone.

When to use it
a coach who adds a new date to a recurring masterclass each time a slot is booked in another tool.
Watch out
the date must use the ISO-8601 format, and any timezone written inside it is ignored; set it in the timezone field.
4

Remove Event

Action

In Zapier“Removes an Event along with all its Sessions”

Deletes an event from Livestorm together with all of its sessions, in a single step.

When to use it
rarely, for instance when a cancelled product launch should take its whole webinar series down with it.
Watch out
every session of the event goes too; to drop just one date, use Remove Session instead.
5

Remove Registrant

Action

In Zapier“Removes a Session Registrant”

Takes a person off a session, using their email address and the event they were registered for.

When to use it
a sales team that unregisters a prospect from the discovery webinar when the deal is marked lost in the CRM.
Watch out
the email must be the one used at registration, or the right person is not found.
6

Remove Session

Action

In Zapier“Cancels or removes an Event Session”

Cancels or removes one session of an event, leaving the event and its other sessions in place. You point to the event, then the session.

When to use it
a trainer who cancels a date when the matching room booking is dropped in the calendar.
Watch out
the field asks which session should be canceled, so map the exact session and not just the event.
7

Update Event

Action

In Zapier“Updates an existing Event”

Changes the settings of an existing event: whether it shows on the company page, recording, replay access, registration pages and the chat, questions and polls tabs.

When to use it
a marketing ops lead who turns the replay public for all events once a campaign closes.
Watch out
only the event is required, and you find it with a search inside the field; every other setting is optional.
8

Update Session

Action

In Zapier“Reschedules an Event Session”

Reschedules an existing session to a new date and timezone. You pick the session, then give the new date and its timezone, all three required.

When to use it
a speaker coordinator who moves the webinar when the speaker changes the date in the shared planning tool.
Watch out
same rule as Create Session, an ISO-8601 date with the timezone set in its own field.
Searches

The 2 Livestorm searches

2 search steps look for data that already exists in Livestorm, so a later step can use it.

A search step looks something up in Livestorm so the next step can use it. Both sit under the SEARCH heading at the bottom of the action list, and three settings decide what happens when the result is not what you expected.

1

Find Session

Search

In Zapier“Find an existing Session.”

Looks up an existing session within an event, so a later step can register someone or reschedule it. The event is required.

When to use it
before Create Registrant, when the trigger tells you the event but not which session to use.
Watch out
an event with several sessions returns several matches; decide with the multiple-results setting which one you keep.
2

Find People

Search

In Zapier“Find Participant or Team Member.”

Finds a participant or a team member linked to an event, filtered by the event ID, which is required.

When to use it
checking whether a contact is already part of an event before a Zap registers them a second time.
Watch out
it wants the event ID, not its title, so map the ID from an earlier step.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps after it are skipped. Switched on, the Zap carries on without a result.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Livestorm offers no such variant on Zapier, so you will not see it on these two searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on.
When it breaks

When the Livestorm Zap breaks

Zapier links no help article to Livestorm and publishes no app-specific limit. What breaks comes from the field rules of the actions and from Zapier's general behavior.

The triggers are instant, so delays are rarely the issue. Most failures come from a date in the wrong format, a missing role, or an action that does more than expected. For general error hunting, our Zapier troubleshooting page goes further.

  • The session date is refused

    Create Session and Update Session only accept ISO-8601 dates. A date written the way your calendar shows it will not go through.

  • The session lands at the wrong hour

    Any timezone written inside the date is ignored. The session timezone field decides, so set it explicitly on every run.

  • The owner cannot create the event

    Only team members with the host role can create events. If the owner picked in Create Event lacks it, the step cannot succeed.

  • All sessions vanished

    Remove Event removes the event along with all its sessions. To drop one date, Remove Session is the action you wanted.

  • The Zap keeps creating sessions

    A Zap that starts on Session Created and runs Create Session triggers itself again with each new session, and burns through tasks fast.

  • Past registrants are ignored

    A Zap only reacts to what happens after it is published. Existing registrants and ended sessions are not picked up; that is a separate job.
Need help

Need help automating Livestorm with Zapier?

A person reads every message.

FAQ

Livestorm Zapier integration: frequent questions

01Is the Livestorm Zapier integration free?
Yes, for simple Zaps. Livestorm is not a premium app, so the free plan accepts it, with 100 tasks a month and Zaps of two steps: one trigger and one action. That covers a lot, like adding every new registrant to a list. A search to find a session, a filter, or a second action makes the Zap multi-step, and that requires a paid plan. This page quotes no price, since the grids change often.
02How many tasks does a Livestorm Zap use?
The seven Livestorm triggers cost nothing, whatever the number of registrations or sessions. Each action that completes successfully is one task, and a failed one is not counted. In a Zap that finds a session, then registers someone, then updates your CRM, each successful action after the trigger counts on its own. Session Ended (People Included) runs once per session, which keeps the count low when you only need one summary.
03Is the Livestorm integration real time?
Yes, for all seven triggers. Each one is instant: Livestorm tells Zapier as soon as a registration, an attendance, a replay view or a session change happens, and the Zap starts right away. The plan intervals, 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise, only apply to polling triggers, so they do not delay these. Attendance triggers still wait for the session to end, by design.
04What do you need to connect Livestorm to Zapier?
A Livestorm account with access to the events you want to automate. In Zapier, open Apps, click + Add connection, pick Livestorm, sign in in the tab that opens and grant access. To create events, the owner you pick needs the host role in Livestorm. The connection is then reused by every Livestorm Zap, so you only do this once per account you want to use. Nothing else is needed on the Zapier side.
05Why does Create Session put the session at the wrong time?
Because of how the date is read. Create Session and Update Session only accept ISO-8601 dates, and they ignore any timezone written inside that date. The timezone comes only from the Session timezone field. If you map a date with a timezone attached and leave that field to a default, the session lands at another hour. Set the timezone field on purpose, and test once with a real date before publishing.
06What if the Livestorm operation that is needed does not exist?
Zapier exposes seven triggers, eight actions and two searches for Livestorm, and that is all. There is nothing to read chat messages, poll answers or questions from a session, for instance. If the job you have in mind is outside that list, check what the other platforms expose for Livestorm, or what Livestorm can do on its own side, before building a workaround that depends on a missing operation. A short test on one real event shows quickly whether the route holds.
07Zapier, Make or n8n for Livestorm?
Decide on criteria, not on a ranking. If you mainly react to registrations and attendance, the seven Livestorm triggers on Zapier are all instant, so they start straight away even on the free plan. If your flows need a search, a filter or several actions, count them, since on Zapier that means a paid plan. And check the operation list: Zapier gives seven triggers, eight actions and two searches here, nothing on chat, polls or questions. Compare that list with what the other two expose before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations