# Livestorm integrations: sessions and people

> Start a Tray.ai workflow when Livestorm sends “Event created”. Connect Livestorm to the rest of your marketing stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/livestorm-integrations/
**Categories:** Marketing
**Connects through:** HTTP Connector

## Overview

Livestorm is a browser-based platform for hosting webinars, virtual events and online meetings, with registration pages, attendee tracking and session recordings. Tray.ai connects to Livestorm through the HTTP Connector, so your workflows can call the Livestorm API alongside the rest of your stack.

## Use cases

### Events

Read, create, update, and delete events in Livestorm from any Tray.ai workflow. The Livestorm API covers calls such as list events and create an event.

- List events
- Create an event
- Update an event

### Sessions

Read and delete sessions in Livestorm from any Tray.ai workflow. The Livestorm API covers calls such as list sessions and get a session.

- List sessions
- Get a session
- Register someone for a session

### People

Read people in Livestorm from any Tray.ai workflow. The Livestorm API covers calls such as list people and get a person.

- List people
- Get a person

### Users

Read, create, and delete users in Livestorm from any Tray.ai workflow. The Livestorm API covers calls such as create a user and list team members.

- Create a user
- List team members
- Delete a user

### Webhooks

Read, create, and delete webhooks in Livestorm from any Tray.ai workflow. The Livestorm API covers calls such as create a webhook and list webhooks.

- Create a webhook
- List webhooks
- Delete a webhook

### Livestorm events

Start a Tray.ai workflow the moment something happens in Livestorm. Livestorm sends events such as event created and event published to a Tray.ai webhook trigger.

- Event created
- Event published
- Session created

## Challenges Tray.ai solves

### Keeping Livestorm credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Livestorm credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Livestorm API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Livestorm API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Livestorm?

Yes. Tray.ai connects to Livestorm through the HTTP Connector, which calls the Livestorm API directly. Any call the Livestorm API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Livestorm?

The Livestorm API uses an API key in a request header and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Livestorm connector?

Livestorm runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Livestorm connector from the Livestorm API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/