Livestorm
Create and manage Livestorm events, sessions, registrants and webhooks.
About
Livestorm ships in the w6w first-party pack. It declares 40 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.livestorm- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Video & Streaming · Communication
Overview
Livestorm runs the webinar or virtual event itself — scheduling it, accepting registrations, running the live session, and recording who actually showed up — and this app brings that lifecycle into a workflow.
Create and manage events (the reusable webinar/meeting definition) and the sessions (individual live occurrences) under them, register or remove participants directly rather than routing them through a separate signup form, bulk-register a whole list at once via an async job, and read chat messages, Q&A questions and recordings back after a session runs. Webhooks let a workflow react to registration, attendance and session-lifecycle events instead of polling for them.
A common pattern is triggering a workflow off an external event — a course enrollment, a CRM stage change, a landing-page form — and registering the person for the right session directly with People Attributes carried over from that source, or reading attendance back afterward to decide who gets which follow-up.
This app covers the everyday event/session/people/job/webhook lifecycle over Livestorm’s private API token; it does not cover the OAuth2 app-install flow (a browser-based third-party-integration flow, not a headless server-to-server credential).
Build with Livestorm
Three routes to the same 40 actions. The Workflow tab is generated from Livestorm's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create Event
event-create Create a new event (webinar/meeting), optionally copying settings from another.
List Event People
event-people-list List the people (registrants and team members) attached to an event.
Replace Event (Full Update)
event-replace Fully update an event via PUT. The vendor does not document whether omitted fields reset to a default — prefer Update Event (PATCH) unless you need this endpoint specifically.
Create Event Session
event-session-create Create a new session under an event, optionally attaching people to it.
List Event Sessions
event-session-list List the sessions (individual occurrences) that belong to an event.
Assign Tag to Event
event-tag-assign Assign a tag to an event (creating the tag if it does not already exist).
Remove Tag from Event
event-tag-remove Unassign a tag from an event by title. Per the vendor's own docs this does NOT delete the tag itself from the workspace, only the assignment.
List Job Tasks
job-tasks-list List the per-item results of an async job (e.g. each bulk registration row).
Get Current User
me-get Get the identity behind the connected account. Note: Livestorm's own documented response schema for this endpoint is identical to GET /organization's — see README.md.
Get Current Organization
organization-get Get the workspace (organization) the connected account belongs to.
List People Attributes
people-attribute-list List the People Attribute slugs (built-in and custom) your workspace can use when registering or updating a session participant.
Bulk-Register People for Session
session-people-bulk-register Register multiple participants for a session in one call. Creates an async job — poll Get Job / List Job Tasks with the returned ID rather than assuming immediate success.
List Session People
session-people-list List the people (registrants and team members) attached to a session.
Register Person for Session
session-person-register Register a new participant for a session. Pass registration data as {id, value} People Attribute pairs in "Fields" (e.g. id "email", id "first_name") — see README.md.
Remove Session Person
session-person-remove Remove a participant from a session, identified by Person (People) ID.
Remove Session Person by Email
session-person-remove-by-email Remove a participant from a session, identified by email address.
Update Session Person
session-person-update Update a contact's People Attributes for a session. Attributes are sent as {id, value} pairs, not top-level keys — see this app's README.
List Session Recordings
session-recordings-list List a session's recordings, with signed playback/download URLs.
Replace Session (Full Update)
session-replace Fully update a session via PUT. Prefer Update Session (PATCH) unless you need this endpoint specifically — see README.md.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Livestorm's real ids.
{
"manifestVersion": "2",
"name": "livestorm-example",
"steps": [
{
"id": "event-get",
"uses": {
"app": "io.w6w.livestorm",
"action": "event-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Get Event
readevent-get -
Create Event
performevent-create -
List Events
searchevent-list -
List Event People
searchevent-people-list -
Get Event Person
readevent-person-get
+35 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Livestorm, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Livestorm. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "event-get",
payload: {
id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action event-get --payload '{"id":"<value>"}'Give an AI agent Livestorm — without giving it Livestorm's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.livestorm#event-get",
"input": {
"id": "<id>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Livestorm connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Livestorm's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Livestorm itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Livestorm declares its own checks, so its health is a property of the app rather than something the host guesses at.
Livestorm platform status
Atlassian Statuspage rollup for status.livestorm.co. Livestorm publishes one component for the whole product, so this check cannot isolate the API from the rest of the app. Unauthenticated and unsigned.
API rate-limit headroom
Requests remaining in the current monthly and 1-second-interval windows, read off RateLimit-Monthly-*/RateLimit-Interval-* response headers on a GET /ping call.