--- title: "Livestorm Integration" description: "Connect AI agents to Livestorm webinars. Agents create and list events, browse scheduled sessions, register people by email, and pull registrants and attendees for CRM follow-up and attendance reporting." url: https://flowrunner.ai/integrations/livestorm date_modified: 2026-08-04T10:04:16-07:00 --- # Livestorm [Scheduling](https://flowrunner.ai/integrations/category/project-management-productivity) Connect AI agents to Livestorm webinars. Agents create and list events, browse scheduled sessions, register people by email, and pull registrants and attendees for CRM follow-up and attendance reporting. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 7 actions · API key · available [Livestorm website](https://livestorm.co/) · [Platform Documentation](https://developers.livestorm.co/reference) · Capability data verified 2026-07-27 1. A new lead requests the product webinar through a form on the site 2. List Events finds the webinar event, and List Sessions pulls its upcoming occurrences 3. The agent picks the next session with open capacity in the lead's likely timezone 4. Register Person enrolls the lead by email, folding their name and form answers into registration fields 5. A confirmation with the join link goes out, and the registration logs to the CRM record 6. After the session, the sales owner reviews the attended-versus-registered list and decides who gets a call versus a nurture sequence 7. The agent executes the split: attendees route to sales follow-up, no-shows get the replay sequence ## What This Integration Enables A webinar is a lead-generation machine with two conversion points: getting the right people registered before it runs, and getting attendance data into follow-up after it ends. Both are timing problems, and timing problems are agent problems. This connector gives FlowRunner agents the full Event to Session to People hierarchy: create and list events, browse scheduled sessions with start times and room links, register people by email with custom field answers, and pull registrants and attendees with their attendance status and registration answers. The operating principle: speed on the way in, judgment on the way out. Registering an interested lead ten minutes after they ask is pure win. Deciding which attendees deserve a sales call is a read on human intent, and it stays with a human. - Register new leads for the next upcoming session the moment they express interest - Sync registrants and attendees into CRMs, sheets, and email tools, split by attendance - Create events from campaign launches and external forms - Report registration and attendance counts across the whole webinar program The registration field answers are the underused asset here. List People returns not just who registered but what they said at registration: role, company size, the question they want answered. Piped into the CRM alongside attendance, those answers turn a webinar list into segmented follow-up, because "attended and asked about pricing" and "registered and ghosted" deserve different next steps. ### Without FlowRunner **Registration is a batch job**: Leads from forms and campaigns get uploaded to the webinar list whenever someone runs the import **Attendance data goes stale in the platform**: Who actually showed up lives in Livestorm while follow-up happens somewhere else, days later **Every webinar is manual setup**: Events, sessions, and registration pages get assembled by hand for each campaign ### With FlowRunner **Leads land registered in minutes**: A form submission becomes a session registration with the join link sent while interest is warm **Follow-up starts when the session ends**: Registrants and attendees flow into the CRM the same hour, split by attendance **Events spawn from campaigns**: A launch or campaign record creates its Livestorm event programmatically, sessions added on schedule ## Use Case Scenarios ### The lead who registers themselves A demo-curious visitor submits the webinar form. The agent calls List Sessions on the monthly product webinar, selects the next upcoming occurrence, and calls Register Person with their email, name, and company. The confirmation with the join link sends through [SendGrid](https://flowrunner.ai/integrations/sendgrid), and the registration writes to the lead's record in [HubSpot](https://flowrunner.ai/integrations/hubspot). Total elapsed time is under a minute, which matters, because webinar registration rates decay with every hour between interest and invitation. ### Follow-up that knows who showed up The session ends. The agent calls List People and splits the list on attendance status: attendees sync to the CRM flagged for sales outreach with their registration answers attached, and no-shows enter a replay nurture sequence. The full export also lands in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for the attendance report. The sales team starts Tuesday morning with a warm list from Monday's webinar instead of receiving a CSV on Friday. ### The campaign that ships with its own webinar A product launch kicks off in the project tracker. The agent calls Create Event with the launch title, tags, and registration page language, and the generated registration link flows back into the campaign assets. Sessions get scheduled in the workspace, and every subsequent form submission from the campaign routes through the Scenario 1 flow. The webinar exists because the campaign exists, not because someone remembered to set it up. ## Human-in-Loop Highlight Register Person does not just add a row; it sets Livestorm's machinery in motion toward a real inbox: confirmation email, calendar entry, reminder sequence, all addressed to the person the agent enrolled. For a lead who just asked, that is exactly right. For a thousand-row imported list, it is a spam run wearing your brand, and the recipients who never asked to attend will mark it as such, which is a cost your sender reputation pays for months. So FlowRunner draws the line at intent: registrations that trace to an individual's own action flow through instantly, while any bulk registration, list import, or re-registration campaign stops for the marketing owner to review the source, the count, and the session before the agent proceeds. One approval covers the batch. What it prevents is unrecallable, because you cannot unsend a reminder sequence to nine hundred people who never wanted it. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 7 actions ### Events 3 - **List Events** Lists the workspace's events with filtering by title, scheduling status, tag, and creation date range. Each result carries the event's title, slug, published status, and registration link. Paginated. - **Get Event** Retrieves a single event by ID with full attributes and relationships, including its sessions. The lookup behind enrichment and routing steps. - **Create Event** Creates an event with a title, optional registration page language, slug, and tags. Returns the created resource with its generated ID and registration link. Sessions are added afterward. ### Sessions 2 - **List Sessions** Lists all sessions belonging to an event, each with status, estimated start time, timezone, and room and registration links. The step that finds the next upcoming occurrence. - **Get Session** Retrieves a single session by ID, including actual start and end times, attendee counts, and room and replay links. The read behind attendance reporting. ### People 2 - **List People** Lists a session's registrants and attendees with email, name, registration date, attendance status, and registration field answers. The export that powers post-webinar follow-up. Paginated. - **Register Person** Registers a person for a session by email, with optional name and additional registration field answers. Returns the registrant with their join link; registering the same email again returns the existing registrant. The action this page's human gate applies to in bulk. ## Frequently Asked Questions ### What can FlowRunner do with Livestorm? FlowRunner agents can run List Events, Get Event, and Create Event in Livestorm, plus 4 more actions. ### Does connecting Livestorm to FlowRunner require OAuth? No. Livestorm connects to FlowRunner with an API key, no OAuth flow required. ### Can Livestorm trigger a FlowRunner workflow automatically? Livestorm doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Livestorm?** This integration exposes Livestorm to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/livestorm. Site index: https://flowrunner.ai/llms.txt