Integrations

Fits the stack
you already run.

An honest look at how SeatView connects with event platforms today, and where we're headed. We don't show logos for integrations that don't exist yet.

Cvent

Exploring
How it would work

Attendee join links embedded in the event app or agenda; registration data via Cvent's API.

Expected effort

Medium — requires Cvent developer access and an event-scoped mapping.

Eventbrite

Exploring
How it would work

Join link in confirmation emails and the event page; attendee counts via the Eventbrite API.

Expected effort

Low to medium — public API, straightforward OAuth.

Whova

Exploring
How it would work

Deep links from the Whova agenda into a SeatView session; no native embedding today.

Expected effort

Low — link-based only unless Whova opens an embedding API.

Zoom

Planned
How it would work

SeatView runs alongside Zoom as the second screen; a Zoom app for in-meeting join is on the roadmap.

Expected effort

Medium — Zoom Marketplace app review required.

Microsoft Teams

Planned
How it would work

Join link in meeting chat today; a Teams tab app for in-meeting participation is planned.

Expected effort

Medium — Microsoft app manifest and tenant approval.

Slack

Planned
How it would work

Post session recaps and engagement summaries to a channel after the event.

Expected effort

Low — incoming webhooks or a small Slack app.

Your existing decks

Works today
How it would work

PowerPoint, Keynote, Canva, and Google Slides all export to PDF — upload the PDF and present.

Expected effort

None — this is how SeatView works today.

Need a specific integration for your event?

Tell us which platform your event runs on. It directly shapes what we build next.