LiveWebinar
SchedulingConnect AI agents to LiveWebinar, a webinar, meeting, and virtual event platform. Agents schedule webinars, register attendees, read participation data, and manage and monitor the recorders behind a session.
What This Integration Enables
LiveWebinar is the only connector in this part of the catalog that can reach into an event that is happening right now, and that capability is what to design around. Most of the surface is ordinary lifecycle management, and it is complete. Create Webinar builds a permanent room, a scheduled one time event or an evergreen automated webinar, and returns the room URL. Update Webinar changes the name, start date, duration, agenda or entry password. List Webinars filters by scope so a flow can ask for scheduled events, evergreen webinars, permanent rooms or past events specifically, and Count Webinars By Type gives the same picture as a single number per type for a dashboard or a quota check. Get Embed Code returns the HTML for putting a room on your own site.
The registration side is where most flows start, and it distinguishes two populations that people routinely conflate. Registrants are the people who filled in the registration form: Add Registrant submits that form's fields, which have to match the field names configured on the webinar's own form rather than a fixed schema, and optionally sends a confirmation email in a chosen language. Confirm Registrant manually approves a pending registrant where the webinar requires it, and Resend Access Link puts the invitation back in front of somebody who lost it. Participants are the people who joined or were added to the room, which is a different set, and Generate Personal Access Link creates a unique join URL for a named person and adds them as a participant with an optional role such as presenter. Sessions are the individual runs of a room, each with its own attendance, and List Session Participants is what makes attendance per run readable rather than aggregated across every time the room was opened.
Then there is the live surface. Start Recording begins capturing the active session and returns the recorder instance, Stop Recording finalises an in progress capture, and Get Recording Status reports whether a recorder is recording, processing or finished with its output details. List Recordings returns the recorders for a room with their status. Note the shape of this: the connector manages recorders and reads their status and output details, and it is not a media download surface, so a flow that needs the finished file works from what the recorder reports rather than expecting the asset to come back through an action. Stop Active Session ends the currently active session for all participants. Delete Webinar, Delete Registrant, Delete Session and Delete Webhook are all documented as permanent.
One thing to be precise about, because the action names invite the wrong assumption. This connector ships no triggers. It does expose webhook management as actions: List Webhooks, Get Webhook, Create Webhook, Update Webhook and Delete Webhook create and maintain LiveWebinar subscriptions that forward a chosen event type to a target URL of your choosing, using the HTTP method you specify. Those are outbound configuration calls into LiveWebinar. They do not register a FlowRunner endpoint, they do not deliver anything into a flow, and no LiveWebinar event starts a flow through this connector. The delivered payload shapes are not documented publicly, which is why no trigger is offered rather than one being guessed at. Reactive behaviour is built on scheduled polling of List Sessions, List Session Participants and Get Recording Status.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Registration that closes the loop with the form that captured it
A demand generation team runs a monthly webinar and the registration form lives on their own site. When somebody submits it, the agent calls Add Registrant against the scheduled webinar, submitting the registration field values keyed to the field names configured on that webinar's form rather than a generic payload, and requests the confirmation email in the language the form captured. It creates or updates the contact in HubSpot with the webinar they registered for. Where the webinar requires manual confirmation, the agent does not auto approve: it holds registrants matching the review criteria and calls Confirm Registrant only for the ones a person clears. A day before the session it calls List Registrants, compares against the contacts that have opened the confirmation, and calls Resend Access Link for the people who have not, which is a smaller and more useful nudge than mailing everybody again.
Attendance measured per run, not per room
An evergreen room is opened repeatedly and every report about it is wrong because the room aggregates. The agent calls List Sessions for the room, which returns each individual run with its own timing and status, then List Session Participants per session to read who attended that specific run. It joins that against List Registrants to separate the three populations a marketing team actually cares about: registered and attended, registered and did not attend, and joined without registering, which is what a shared access link produces. Each group goes to a different path in HubSpot, and the per session picture is appended to Google Sheets so the team can see whether the Tuesday run outperforms the Thursday one. Nothing is written to LiveWebinar in this flow, which is what makes it safe to run after every session automatically.
A room prepared and torn down around a customer event
A partner runs a joint session and needs a room that exists for exactly that purpose. The agent calls Create Webinar as a scheduled event with the start date, duration and agenda from the calendar invite, and an entry password. It calls Get Embed Code and posts the embed into the partner's landing page, and Generate Personal Access Link for each named presenter with the presenter role assigned, so nobody is sharing one link and hoping. It posts the room URL and the individual presenter links to the shared channel in Slack. Afterwards it calls List Sessions and List Session Participants to capture the attendance record and writes it out before anything is removed, because Delete Session takes the attendance and engagement data with it permanently. Only then, and only on a person's instruction, does anything get deleted.
Human-in-Loop Highlight
Stop Active Session is the gate, and it is the only action in this entire batch of scheduling and registration connectors that reaches into something that is happening at this second. It ends the currently active session of a room for every participant in it. Not a warning, not a countdown, not a request to the host: the event stops, mid sentence, for the speaker and for everyone watching. There is no resume, because a room reopened produces a new session with its own attendance record, so the analytics for the event you just cut off are now split across two sessions and the second one is the three people who rejoined. The reason an agent gets anywhere near this action is legitimate. A session overruns into the next booking on a shared room, a recording is still capturing and eating quota, an evergreen room was left open after a test. All of those are real, and all of them are also indistinguishable, through the API, from a session where the speaker is answering the last and most important question of the day. List Session Participants can tell the agent forty one people are still in the room. It cannot tell the agent what is being said to them. There is a safe half of this that needs no permission: Stop Recording finalises the capture so the recording is preserved and processed regardless of what happens to the room next, and that runs first, unattended. Then the agent stops and asks. It posts to the producer: "Room 'Q2 Product Deep Dive', session 88214, scheduled for 45 minutes and running 71. Get Recording Status shows the recorder still capturing, and I have stopped it so the recording is safe. List Session Participants shows 41 people still in the room, down from 96 at the peak. The room is booked again in 9 minutes. Stop Active Session ends it now for all 41, and reopening starts a new session with separate attendance. Stop it, or shall I message the host instead?" A person decides. That is the human-in-the-loop moment in live event operations: an agent can see the clock, the headcount and the calendar conflict, and only a person can judge what it costs to cut off a room full of customers.
Agent Capabilities
33 actionsWebinars
7- List Webinars Returns webinars, meetings and events with a scope filter for permanent rooms, scheduled events, evergreen automated webinars or past events, plus sorting and pagination.
- Get Webinar Returns one webinar's full configuration and data. The optional include parameter embeds related resources such as sessions, registrants, polls or presenters, so a single call can produce the whole picture of a room.
- Create Webinar Creates a room as permanent (always on), scheduled (a one time event with a start date) or evergreen (automated on demand), and returns the new webinar including its room URL.
- Update Webinar Changes only the fields supplied, commonly the name, start date, agenda or entry password. The action a reschedule runs through.
- Delete Webinar Permanently deletes a room and its configuration. This cannot be undone.
- Get Embed Code Returns the HTML embed code for a room, for placing it on an external site.
- Count Webinars By Type Returns counts grouped by type (permanent, scheduled, evergreen, past), for dashboards and quota checks without walking a list.
Registrants
6- List Registrants Returns the people who signed up through the registration form for a webinar, as distinct from the people who actually joined.
- Get Registrant Returns one registrant with their submitted form field values and confirmation status.
- Add Registrant Registers a person by submitting the webinar's registration form fields. The Registration Fields keys must match the field names configured on that webinar's own form, so read the form before building the mapping. Optionally sends a confirmation email in a chosen language.
- Confirm Registrant Manually confirms a pending registrant and grants them access, for webinars configured to require confirmation.
- Resend Access Link Resends the access link email to a registrant who did not receive or lost the original.
- Delete Registrant Removes a registrant and revokes their access. This cannot be undone.
Participants
2- List Participants Returns the participants associated with a room, meaning people who joined or were added, which is a different population from registrants.
- Generate Personal Access Link Creates a unique join URL for a named person, adds them as a participant and optionally assigns a role such as presenter or attendee. The right way to give each speaker their own link rather than circulating one.
Sessions
5- List Sessions Returns the individual runs of a room. Each time a room is opened it produces a session with its own attendance and engagement data, which is why room level reporting on a repeated webinar misleads.
- Get Session Returns one session with its timing and status information.
- List Session Participants Returns the people who attended one specific session, which is what makes per run attendance analysis possible.
- Stop Active Session Ends the currently active session of a room for all participants. There is no resume, since reopening the room creates a new session with separate attendance, which is why this runs behind an approval.
- Delete Session Permanently deletes a recorded session along with its attendance and engagement data. This cannot be undone, so export the attendance record before calling it.
Recordings
4- List Recordings Returns the recorders for a room with their status and output details.
- Start Recording Starts a recording on the active session and returns the new recorder instance.
- Stop Recording Stops an in progress recording by recorder ID, after which it is finalised and processed. The safe half of an overrun response, because it preserves the capture without touching the room.
- Get Recording Status Returns a recorder's current status, such as recording, processing or finished, with output details when available.
Account
4- Get Current Account Returns the authenticated account with profile, package and aggregate usage information. The include parameter embeds related data such as profile, Package or Aggregate.
- List Users Returns the sub-accounts belonging to the account, for multi user and agency setups.
- Get User Returns one sub-account by ID.
- Search Users Searches sub-accounts by a text phrase matched against name and email.
Webhooks
5- List Webhooks Returns the webhook subscriptions configured on the LiveWebinar account, each forwarding a chosen event type to a target URL. These are LiveWebinar's own subscriptions, not FlowRunner triggers.
- Get Webhook Returns one webhook subscription's configuration by ID.
- Create Webhook Creates a LiveWebinar webhook subscription that sends a chosen event type to a target URL of your choosing using the specified HTTP method. It subscribes an external endpoint you nominate and creates no FlowRunner trigger, so nothing delivered by it starts a flow through this connector.
- Update Webhook Changes an existing subscription's target URL, delivery method, subscribed event or enabled status.
- Delete Webhook Deletes a webhook subscription and stops delivery of its events. This cannot be undone.
Frequently Asked Questions
What can FlowRunner do with LiveWebinar?
FlowRunner agents can run List Webinars, Get Webinar, and Create Webinar in LiveWebinar, plus 30 more actions.
Does connecting LiveWebinar to FlowRunner require OAuth?
No. LiveWebinar connects to FlowRunner with session-based authentication, no OAuth flow required.
Can LiveWebinar trigger a FlowRunner workflow automatically?
LiveWebinar doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with LiveWebinar
$100 in credits. No card required. Connect in minutes.