LiveStorm

How to integrate LiveStorm with Webflow

Webinar registration pages built in Webflow need to connect with LiveStorm for attendee management, confirmation emails, and calendar invites. LiveStorm handles registration workflows automatically while Webflow manages the front-end design and content presentation. This integration enables teams to capture registrations through custom-designed landing pages while maintaining centralized attendee data in LiveStorm.

LiveStorm doesn't have a Webflow marketplace app, so integration requires embed widgets, automation platforms like Zapier or Make, or custom API development. Embed widgets deploy registration forms quickly. Automation platforms connect Webflow forms to LiveStorm without custom code. API integration supports bidirectional data flow and custom attendance tracking in Webflow CMS.

Embed registration widgets and company pages

LiveStorm provides embed codes that you paste into Webflow's custom Code Embed elements. Registration data flows directly to LiveStorm while visitors stay on your Webflow site. According to LiveStorm's landing page guide, access the embed code from the "Share event" modal in your LiveStorm dashboard, then paste it into a Webflow HTML Embed element. This embed method makes registration data available immediately in your LiveStorm dashboard while maintaining the visitor experience on your Webflow site.

What you can embed:

• Event registration forms with adjustable width for different layouts using the embed code from your event's share modal
• Company page widgets displaying upcoming and past events with language localization options and event filtering capabilities
• On-demand video players configured through recording and replay settings with access controls for viewer permissions

LiveStorm's embedded registration widgets collect confirmation emails and reminder sequences automatically through LiveStorm's native workflows, not through Webflow. Your Webflow site maintains its design while LiveStorm manages the registration infrastructure. Style the surrounding container in Webflow, but the widget itself follows LiveStorm's configuration options and design parameters. Custom styling of the widget requires LiveStorm Pro, Business, or Enterprise plans (LiveStorm custom code documentation).

Embedding requires copying code from LiveStorm and pasting into Webflow's custom Code Embed elements. Using this method, registrations are captured directly by LiveStorm with no additional infrastructure needed. However, if you want to synchronize registration data into Webflow CMS for further automation or analysis, you'll need to implement middleware such as Zapier or Make, or develop a custom API integration. For registration capture alone, the embed method provides immediate functionality without building sync infrastructure.

Connect through automation platforms

Zapier, Make, and viaSocket provide automated workflows connecting Webflow forms to LiveStorm registration endpoints through custom configuration, rather than providing native pre-built integrations. You can configure form submissions in Webflow to automatically create registrants in LiveStorm events through these middleware platforms. Conversely, you can sync LiveStorm registration data to create or update CMS items in Webflow collections, though this requires setting up API connections and data field mapping within your chosen automation platform.

Zapier's LiveStorm-Webflow integration provides pre-built workflow templates where Webflow form submissions automatically trigger LiveStorm event registrations, supporting real-time attendee synchronization. Make's integration provides visual scenario builders with conditional logic and multi-step workflows, allowing teams to build complex automation sequences connecting Webflow forms to LiveStorm registration endpoints. viaSocket offers similar workflow automation capabilities with configurable field mapping between Webflow and LiveStorm, though with fewer pre-built templates than Zapier.

Connect both platforms by providing API credentials to the automation tool, then map form fields to LiveStorm registration data. When someone submits a Webflow form, the automation platform calls LiveStorm's API to create the registration. For real-time synchronization, use webhook-based integration where LiveStorm webhooks trigger instant updates to Webflow. For polling-based sync, timing depends on your automation platform's plan tier. Zapier free tier checks every 15 minutes, while paid Zapier plans offer 1-5 minute intervals, and Make provides configurable timing closer to real-time.

This method works when you want to use custom-designed Webflow forms combined with LiveStorm's registration capabilities through middleware platforms like Zapier or Make, or when you need to implement webhook-based synchronization to sync attendee data back to Webflow CMS for personalized content display. Note that there is no native LiveStorm-Webflow integration, so these implementations require third-party automation platforms or custom API development.

Build with Webflow and LiveStorm APIs

LiveStorm's REST API provides custom integrations for teams needing full control over data synchronization. You can build workflows that create Webflow CMS items from LiveStorm registration events, register contacts to webinars from Webflow forms, or update CMS collections based on attendance data.

Authentication uses LiveStorm's API tokens and Webflow's OAuth 2.0 flow. Generate LiveStorm tokens from Account Settings → Integrations → Public API (requires workspace admin access). Webflow authentication requires appropriate scopes including sites:read, sites:write, cms:read, cms:write, and depending on use case, additional scopes like forms:read and forms:write.

Use webhooks instead of polling to optimize API usage and maintain efficient data synchronization.

Sync event data to Webflow CMS

LiveStorm's Events API retrieves event details in JSON:API format with attributes including titles, descriptions, registration links, and session schedules stored in the attributes object. Webflow's CMS API uses standard REST JSON for POST requests to create collection items with custom fields, requiring specific field types (Plain Text, Rich Text, Email, Date, etc.) mapped to your collection schema.

Fetch events from GET /v1/events, extract relevant fields like title and description, then POST to Webflow's /v2/collections/{collection_id}/items endpoint to create CMS entries. Store LiveStorm event IDs in Webflow custom fields to maintain bidirectional references between platforms. Session data comes from GET /v1/events/{id}/sessions (as documented in the LiveStorm Session reference) with scheduled start times and attendance counts.

Configure LiveStorm webhooks for real-time updates when events publish or sessions start. Webhook events like event.published and session.created POST JSON to your server, which then updates Webflow CMS via PATCH requests to /v2/collections/{collection_id}/items/{item_id}.

Date fields require format conversion. LiveStorm returns ISO 8601 dates like 2025-12-03T10:00:00Z, but Webflow needs milliseconds like 2025-12-03T10:00:00.000Z. This conversion is critical for proper date field handling in Webflow CMS collections and API requests.

Register contacts from Webflow forms

Webflow form submissions trigger form_submission webhooks that POST submission data to your endpoint. Extract email, name, and custom fields, then call LiveStorm's registration endpoint using POST /v1/sessions/{session_id}/people.

For bulk operations, LiveStorm's bulk registration endpoint (POST /v1/sessions/{id}/people/bulk) accepts up to 100 registrants per request. Query Webflow CMS collections using GET /v2/collections/{collection_id}/items, batch contacts into groups of 100, then POST to LiveStorm's bulk endpoint.

Store registration confirmation data in Webflow CMS by updating the contact's collection item with attendance status and LiveStorm person IDs. This supports conditional content display based on registration state.

Track attendance and engagement

LiveStorm attendance webhooks fire events including people.attended, people.not_attended, and people.watched_replay with attendance duration and engagement metrics. Configure webhooks to POST to your server via HTTPS, then update corresponding Webflow CMS items with the received attendance data.

Use Webflow CMS to store and segment attendee data by retrieving event registrants via GET /events/{id}/people or registering users via POST /sessions/{id}/people. Through Webflow's CMS API, create or update collection items with attendance data by mapping LiveStorm registrant information to custom fields. This supports content personalization based on attendance status, attendance duration, or engagement metrics captured from LiveStorm webhooks like people.attended and people.not_attended. Display different resources to attendees versus no-shows, or use engagement data to determine which content gets surfaced to specific user segments.

Webhooks require HTTPS endpoints and automatically retry failed deliveries up to 5 times. After 5 consecutive failures, LiveStorm disables the webhook subscription and emails the account owner. Note that webhooks operate as workspace-wide subscriptions, so event filtering must be implemented client-side. Implement proper error handling and monitor webhook health to prevent disablement.

What you can build

Integrating LiveStorm with Webflow creates webinar registration capabilities directly on Webflow sites, with options for bidirectional data synchronization through APIs or automation platforms. Teams can embed registration widgets, sync attendee data to Webflow CMS collections, and build automated workflows connecting webinar events to site content. While there is no native integration, these implementation methods support registration capture, attendee tracking, and content personalization without requiring manual data entry.

• Webinar registration landing pages: Design custom landing pages in Webflow using standard HTML Embed elements for LiveStorm registration widgets. According to LiveStorm's landing page documentation, these embedded registration widgets capture attendee information while LiveStorm handles confirmation emails, calendar invites, and attendee management. Teams use this pattern for feature announcements, product demos, and lead generation webinars.
• Automated event calendars: Pull LiveStorm session data into Webflow CMS collections that power dynamic event calendars showing real-time seat availability, upcoming schedules, and registration status.
• On-demand content archives: Create on-demand webinar replays that you can embed in Webflow through video hosting platforms like YouTube or Vimeo, supporting product training libraries and customer education hubs.
• Attendance-based content personalization: Use LiveStorm attendance webhooks to update Webflow CMS collection items with engagement data, then display personalized resources based on attendance status.