Resources · Make integration

Livestorm Make integrationAutomate Livestorm with Make.

Your webinar ends, and the follow-up should already be moving. The Livestorm Make integration gives you 19 modules: 6 instant triggers, 10 actions and 3 searches. This page shows how to link your account and build a first working scenario.

Try the Livestorm integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Livestorm Make integration do for you?

The Livestorm Make integration links your Livestorm account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Livestorm then tells Make when an event starts, ends or gets a new registrant, and Make can create, update or look up events, sessions and people for you.

Registrations that fill themselves. Leads who sign up in a form, a shop or a spreadsheet can land in your webinar with Create a Registrant. Nobody copies emails from one tab to another anymore.

A no-show follow-up that never gets forgotten. Watch Registrant not Attended fires after a session for each person who missed it. Send the replay, create a sales task, or tag the contact in your CRM.

An event calendar that stays in sync. When Watch Event Published sees a new event, Make can push it to your website, a Slack channel or a shared sheet. Update an Event and Update an Event Session handle the changes in the other direction.

What Make does not do here: every Livestorm trigger is instant, so there is no scheduled trigger to sweep past events. Anything outside the 19 listed modules goes through Make an API Call, with the same connection. If you are weighing both tools for this kind of flow, the n8n vs Make comparison lays out the criteria. New to the editor? The Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect Livestorm to Make?

  1. 01

    Generate a Livestorm API token

    In Livestorm, open Account Settings, then the Integrations tab. Scroll to the bottom, click the Public API card and generate a new token. Pick the scope permissions your scenario needs, then copy the token shown on screen.

  2. 02

    Add a Livestorm module in Make

    Log in to Make, add any Livestorm module to your scenario and click Create a connection. A connection is your Livestorm account linked to Make once, then reused by every Livestorm module. The Connection name field is optional.

  3. 03

    Paste the credentials and save

    Enter the token you copied, or follow the on-screen instructions if Make offers the OAuth2 route instead. Once saved, Make can read your events and sessions, and the module fields start offering them in lists.

First scenario

Your first scenario: register sign-ups from another app in Livestorm

GoalWhen a lead signs up in another app, Make registers that person in your Livestorm event.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. The first module is the app where your sign-ups arrive: a form tool, a CRM or a spreadsheet.

  2. 02

    Set up the source module

    Search that app by name, pick the module that watches new entries, and click Create a connection to link the account. Each new entry becomes a bundle, one item that flows to the next module.

  3. 03

    Add Create a Registrant

    Click the + on the right of the first module, search Livestorm and pick Create a Registrant. Connect your Livestorm account, choose the event from the list, then map the person's details from the first module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received, then check in Livestorm that the test person shows up as a registrant.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default, 1 minute at the lowest on paid plans) and switch the scenario on. Each module run counts as one operation on your plan.

Triggers

Livestorm triggers: what starts your scenario

6 modules start a scenario when something happens in Livestorm. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Livestorm as soon as it happens.

Livestorm1Watch Event End

Watch Event End

Instant trigger

In Make“Triggers when one of your events has ended.”

Watch Event End starts your scenario as one of your Livestorm events finishes, so the after-event work begins while the talk is still fresh for everyone.

How it fires
instant, Livestorm calls Make through a webhook as soon as the event ends. No schedule to set.
When to use it
a recap task for the host, a message in the team channel, or a survey sent once the webinar is over.
Watch out
it reports the event, not each attendee. For per-person follow-ups, the two registrant triggers below are the better fit.
Livestorm2Watch Event Published

Watch Event Published

Instant trigger

In Make“Triggers when a new event has been published.”

Get a signal the moment a new event goes live in Livestorm, and let Make spread the news wherever your audience looks: a website listing, a newsletter draft, a Slack post.

How it fires
instant, Livestorm calls Make through a webhook as soon as the event is published.
When to use it
your marketing team publishes events in Livestorm and wants the promotion to start without a second round of copy and paste.
Watch out
when you add it, Make asks you to click Create a webhook before the connection. That webhook is the address Livestorm calls.
Livestorm3Watch Event Start

Watch Event Start

Instant trigger

In Make“Triggers when one of your events has started.”

This one reacts when an event goes live, which makes it the right hook for anything that should happen during the session rather than before or after it.

How it fires
instant, Livestorm calls Make through a webhook as soon as the event starts.
When to use it
alert the sales team that the demo is live, post a "we are on air" message on your community, or log the start in a reporting sheet.
Watch out
the scenario has to be switched on before the event begins. A scenario left off simply misses the start.
Livestorm4Watch New Registrants

Watch New Registrants

Instant trigger

In Make“Triggers when a new person has registered for one of your event sessions.”

Every new sign-up for one of your event sessions becomes a bundle in Make, ready to be copied into your CRM, your email tool or a lead sheet.

How it fires
instant, Livestorm calls Make through a webhook as soon as someone registers.
When to use it
your sales team wants webinar leads in the CRM without exporting a list after each event.
Watch out
each registrant runs the whole scenario once, and every module counts an operation. A popular webinar can use more operations than you expect.
Livestorm5Watch Registrant not Attended

Watch Registrant not Attended

Instant trigger

In Make“Triggers when a registrant has not attended the session after it's end.”

Catch the people who signed up but never showed, right after the session ends, and give them a second chance to watch.

How it fires
instant, Livestorm calls Make through a webhook as soon as the session ends and a registrant is marked absent.
When to use it
send the replay link, add the contact to a nurture list, or create a call task for a rep who wanted that lead in the room.
Watch out
it fires once per missing person, not once per session. Build the scenario for a single contact and let Make repeat it.
Livestorm6Watch Registrants Attended

Watch Registrants Attended

Instant trigger

In Make“Triggers when a registrant has attended the session after it's end.”

Here you get the list of real attendees, one by one, once the session is over. It is the cleanest signal of interest your webinar produces.

How it fires
instant, Livestorm calls Make through a webhook as soon as the session ends, for each registrant who attended.
When to use it
move attendees to a warmer stage in your CRM, send a thank-you with the slides, or notify the account owner.
Watch out
if you also run the not attended trigger, keep them in two separate scenarios. On the Free plan, that already uses both active scenario slots.
Modules

Livestorm actions and searches in Make

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

Livestorm1

Create an Event

Action

In Make“Creates a new event.”

Spin up a new Livestorm event from another tool, so the webinar exists as soon as the idea is approved elsewhere.

When to use it
a row marked "approved" in your content planning sheet, or a project card moved to "scheduled", should create the matching event.
Watch out
sessions are handled separately. To add a time slot, follow up with Create an Event Session.
Livestorm2

Create an Event Session

Action

In Make“Creates a new session for the specfied event.”

Adds a session to an event that already exists, which is how one webinar gets several time slots or a replay date.

When to use it
right after Create an Event in the same scenario, or when a trainer confirms an extra slot in your booking tool.
Watch out
the module needs the event to attach to. Map the event ID from the previous module instead of typing it by hand.
Livestorm3

Create a Registrant

Action

In Make“Creates a new registrant.”

Signs a person up for your event without them ever opening the Livestorm registration page, which keeps one clean list of attendees.

When to use it
customers who ticked "join the onboarding webinar" at checkout, or leads coming from a partner form.
Watch out
run it once with Run once and a test address first. A mapping mistake here lands straight in a real attendee list.
Livestorm4

Delete an Event

Action

In Make“Deletes an event specified by ID.”

Removes an entire Livestorm event by its ID. Useful to keep your account tidy when an event is cancelled in the tool where you plan it.

When to use it
a webinar marked "cancelled" in your project board should disappear from Livestorm too.
Watch out
a delete cannot be undone from Make. Put a filter before the module so only the intended event reaches it.
Livestorm5

Delete an Event Session

Action

In Make“Deletes an event session specified by ID.”

Drops a single session and leaves the rest of the event in place. That is the lighter option when only one time slot falls through.

When to use it
a speaker cancels one date, but the other sessions of the series still go ahead.
Watch out
pick this one rather than Delete an Event whenever other sessions must survive. Check the session ID with Search Sessions first.
Livestorm6

Get a Person

Action

In Make“Retrieves a single person by ID.”

Fetches one person's full Livestorm record from an ID you already have, handy when the trigger does not pass along everything the next modules need.

When to use it
just after Watch New Registrants, to enrich a CRM contact before creating it.
Watch out
this module needs an exact ID. If you only have a name or an email, start with Search People instead.
Livestorm7

Make an API Call

Action

In Make“Performs an arbitary authorized API call.”

Reaches any endpoint of the Livestorm API through your existing connection. It is the way out when none of the other ready-made modules does what you need.

When to use it
a Livestorm feature has no ready-made module and your scenario still needs to read or change it.
Watch out
you write the request yourself, so keep the Livestorm API documentation open beside the editor.
Livestorm8

Remove a Registrant

Action

In Make“Removes a registrant specified by ID.”

Takes a registrant off your event by ID, so your attendee count reflects who actually plans to come.

When to use it
a customer asks to unsubscribe in your support tool, or a refund is issued for a paid workshop.
Watch out
this is not Delete an Event Session. The session stays in place, only this one person leaves it.
Livestorm9

Update an Event

Action

In Make“Updates an event specified by ID.”

Changes an existing event by ID, so one edit in your planning tool is enough and Livestorm follows.

When to use it
a title or description rewritten in your content calendar should flow to the live event page.
Watch out
the module works from the event ID. Search Events finds it when your planning tool only knows the title.
Livestorm10

Update an Event Session

Action

In Make“Updates an event session specified by ID.”

Adjusts one session of an event without touching the others. That is handy when only a single slot moves.

When to use it
a trainer shifts one date in the booking tool and the matching Livestorm session should follow.
Watch out
you need the session ID, not the event ID. Search Sessions finds it when your other tool does not store it.
Livestorm11

Search Events

Search

In Make“Searches for events or lists them all.”

Looks through your Livestorm events, or lists them all, and returns each match as its own bundle.

When to use it
building a public events page, or finding the right event ID before an update.
Watch out
a search can return zero, one or many results. Every module placed after it runs once per event found.
Livestorm12

Search People

Search

In Make“Searches for participants or members or lists them all.”

Finds participants or team members in your Livestorm account, which is how you turn a name or an email from another tool into a usable record.

When to use it
before Get a Person or Remove a Registrant, when your source app has no Livestorm ID.
Watch out
with no filter, the module lists everyone. Narrow the search, or the next modules will burn operations on each result.
Livestorm13

Search Sessions

Search

In Make“Searches for sessions or lists them all.”

Returns the sessions that match your search, or the full list, one bundle per session.

When to use it
you need the session ID for Update an Event Session or Delete an Event Session and only know the event.
Watch out
a series with many dates gives many bundles. Add a filter to keep the one session you mean to change.
Need help

Need help automating Livestorm with Make?

A person reads every message.

FAQ

Livestorm and Make: common questions

01Is the Livestorm Make integration free?
Yes, on the Make side. Livestorm is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. You still need an active Livestorm account of your own, and its pricing is set by Livestorm, not by Make.
02What is needed to connect Livestorm to Make?
An active Livestorm account and either an API token or an OAuth2 access token. To get the token, open Account Settings in Livestorm, go to the Integrations tab, click the Public API card at the bottom and generate a new one. Choose the scope permissions your scenario needs and copy the token shown on screen. In Make, add a Livestorm module, click Create a connection and paste it. For an instant trigger, click Create a webhook first.
03Do the Livestorm triggers in Make react instantly?
Yes. All six Livestorm triggers are instant: Livestorm calls Make through a webhook as soon as the event happens, whether an event is published, starts, ends, gets a new registrant, or closes with attendees and absentees. You do not wait for a polling interval. In the editor, instant triggers carry a lightning badge instead of a clock. The scenario has to be switched on to receive these calls, and each run still counts operations on your plan.
04What if a Livestorm module is missing in Make?
Use Make an API Call. It reuses your Livestorm connection and can call any endpoint of the Livestorm API, so you are not limited to the ready-made modules. You write the request yourself, which means reading the Livestorm API documentation. Also note that the Make documentation for this app carries a warning: it was generated with AI from the official Livestorm documentation and may contain mistakes, so double check any detail that matters before relying on it.
05Make or n8n for Livestorm automations?
It depends on what you already use. On Make, Livestorm comes with 19 ready modules, including 6 instant triggers, plus Make an API Call for the rest, and it works from the Free plan. The same app often has an n8n node as well. Compare the modules each tool offers for your exact flow, the editor your team is comfortable with, and how each plan counts usage. No tool wins by default: the right choice is the one where your scenario needs the fewest workarounds.
Same platform

Other docs you might need on this stack.

Browse all integrations