Integrations › Strapi
Integration ·
Automation & API

Your event content, managed in Strapi

Speakers, agenda, sessions and sponsors live in Strapi, where your content team works. Over Streavent's Open API that content syncs into your event website, so what editors publish in the CMS shows on the event page. One source of content, no copy and paste.

Book a demo
Create event for free
Streavent
Streavent
Strapi
Veranstalter, die mit Streavent arbeiten
SPD-Bundestagsfraktion DWA DVGW Bundesinstitut für Berufsbildung Universität Ulm Europlanet Society DVR Luminus Laserschutz Smart Village Deutsche Telekom Kertos FTAPI Kreiskliniken Reutlingen

The problem

Your event content lives in two places, and they drift apart

The agenda changes, a speaker drops out, a new sponsor signs: your content team updates the CMS, and then someone re-enters all of it in the event tool by hand. Two systems, the same content, always slightly out of sync.

Data flow

How your data moves

The most common flows, each as a live sync.

arrow_forward From Strapi into your event website

Strapi
Speakers
Streavent
Streavent

Speaker profiles from your CMS

Editors maintain speaker names, bios and photos as Strapi entries. Over the Open API those profiles populate the speaker section of your Streavent event website, updated whenever.

Strapi
Agenda
Streavent
Streavent

Agenda and sessions stay in sync

Sessions, times, rooms and tracks live in Strapi as structured content. The Open API pushes them into the Streavent agenda, so a last-minute reschedule in the CMS reaches the.

Strapi
Sponsors
Streavent
Streavent

Sponsor logos and tiers

Sponsor names, logos, tiers and links are managed in Strapi. Over the API they render in your event website's sponsor area, in the order and grouping your content team defines.

arrow_back

Streavent
Streavent
Strapi

Streavent
Streavent
Strapi

Streavent
Streavent
Strapi

These are the most common flows, not all of them. Speakers, sponsors, agenda and more sync too, and you can create a whole event straight from your tool.

How it works

How Streavent connects to Strapi

code

Over the Open API

Streavent's REST API (from the Growth plan) accepts your event content. A developer maps Strapi content types, speakers, sessions, sponsors, to the matching.

sync

Content stays where editors work

Your team keeps writing in Strapi, the tool they know. A scheduled sync or a Strapi webhook pushes each change to Streavent, so the event website always shows.

edit_note

Structured content, mapped once

Set the field mapping up one time: Strapi title to session name, relation to speaker, media to logo.

For your team

One event signal for your whole team

edit

Content team: one place to publish

Speakers, agenda and sponsors are written and approved in Strapi, with your editorial workflow intact. No second entry in the event tool, no copy that goes stale.

web

Web team: one content model, many outputs

The same Strapi content that feeds your main website also feeds the Streavent event page. One model, reused, instead of a separate CMS for every event.

event_available

Event team: an agenda that is never out of.

When the schedule shifts, the change is made once in Strapi and flows to the event website over the API. Attendees always see the current agenda, not last week's PDF.

Availability

Set up during onboarding, data protection as standard

We set up the integration together during onboarding, tailored to your systems.

  • GDPR-compliant with a data processing agreement
  • Hosting in Germany, ISO 27001 (in certification)
  • Accessible registration flows (EAA-compliant)

Customer Stories

Loved by event teams across industries

Meet the people behind the events: real teams who plan, run, and scale their events with Streavent.

“We ran the entire event in one system and went live in under a week.”

Christoph Newiger, Co-Founder Research Inititative Ostheopathy

“Our event app basically builds itself, with content syncing automatically from our CRM.”

Stefan Sutor, CEO Medien Bayern GmbH

“We deliver our AI webinars as professional livestreams in top quality, all from one platform.”

Franziska Weindauer, CEO, TÜV AI Lab

“We build event landing pages without an agency, and it shows a clear ROI.”

Christina Armbruster, Marketing Manager, Optigrün international AG

“Check-in was effortless, even volunteers were ready in minutes.”

Ludwig Rabe, Co-Founder Blütezeit Collective & APOGEO Festival

“Digital, hybrid, in-person: the platform gives us full flexibility, with a truly professional look.”

Alexandra Straka, Event Manager, German Road Safety Council

“We ran check-in entirely through the platform, and the analytics help us improve every event.”

Lars Eggers, CEO Seses Drinks & Host AGM Congress

“Our CRM connects directly via API, so we build complete events in just a few clicks.”

Christiane Schäfer, Event Manager, DWA BW

“The all-in-one solution we scale up or down for every event, seamlessly integrated with our CRM.”

Dr. Ricarda Engelmeier, CEO Münchner Management Kolloquium

Ready to run event content from Strapi?

Show us your Strapi content model and your next event, and we will map the sync with you: speakers, agenda and sponsors from the CMS onto your Streavent event website, over the Open API.

Book a demo

FAQ

Frequently asked questions

Over Streavent's Open API, and for content, not attendees. Strapi is your headless CMS: your team manages speakers, agenda, sessions and sponsors there. A developer maps those content types to the matching fields in Streavent, and a scheduled sync or a Strapi webhook keeps the event website current. Registrations and attendee data are not part of this flow, that stays inside Streavent.

Editorial event content: speaker profiles with bio and photo, the agenda with sessions, times, rooms and tracks, and sponsors with logos, tiers and links. You define the Strapi content types and map them to the speaker, session and sponsor fields on your Streavent event website. Whenever an editor publishes a change in Strapi, the sync carries it to the event page.

No, and we keep that honest. This integration is about content, not attendees. Registrations, check-in status and leads live in Streavent and are not written to Strapi. Strapi holds the editorial content, speakers, agenda, sponsors, and the Open API pushes that content onto the event website. For attendee data flowing out to a CRM, you would use the CRM integrations or the Open API directly.

For the initial mapping, yes. Streavent's Open API is available from the Growth plan, and a developer connects your Strapi content types to the matching Streavent fields and sets up the sync or webhook. After that one-time setup, your content team works entirely in Strapi: they publish, and the event website updates on its own, with no further developer involvement.