Integrations

Keep the ticketing you already have.

ewent is an overlay, not a replacement. It reads the registrations you already collect and adds the layer that happens afterwards — checklists, cadence, the live nudge. Nothing about your ticketing changes.

PlatformStatusHow it connectsNotes
Eventbrite Import CSV / attendee export Bring the registration export; ewent creates the event and attendees from it. Direct sync is next.
Luma Import CSV / attendee export Same path as Eventbrite. Luma’s own reminders and ewent’s cadence coexist without duplicating receipts.
Cvent Planned — Enterprise registration. On the list because it is where the largest no-show budgets sit.
Meetup Planned — Recurring community events — the strongest fit for the series model.
Zoom Planned — Join links and attendance signal for the live nudge.
Google Sheets Live CSV upload The universal fallback. Any platform that can export a list can feed ewent today.
Your platform Live REST API Three calls. See the quickstart.
We mark these honestly. “Planned” means exactly that — not a quiet beta. If a connector you need is on the Planned row, tell us; demand decides the order. Meanwhile the CSV path and the API both work today and carry real events.

The overlay model

What stays yours.

◧

Ticketing & payment

Untouched. ewent never handles money and never re-issues a ticket.

◨

The attendee relationship

Messages go out in the organizer’s name. ewent is deliberately invisible.

◩

Your attendee data

We receive what we need to run a cadence and nothing else. See the DPA.

◪

Your exit

Turn ewent off and the event still runs. There is no lock-in because there was never a migration.

Integration questions

Won’t attendees get duplicate emails?

The cadence is built to carry what your ticketing platform doesn’t — logistics, prep, and the live nudge — rather than repeat the receipt. If you also run your own broadcast list, you control the overlap.

How often does the data sync?

On the CSV path, whenever you upload. On the API path, whenever you call it — most partners call once per registration, in the same request that creates it.

What if an attendee cancels on the ticketing side?

Push the cancellation through the API or re-upload, and the pending cadence for that attendee stops.

Can I run ewent on only some of my events?

Yes. It is per-event, not per-account. Most organizers start with one recurring series.

Stop losing the people who already said yes.

Connect the registrations you already collect. We handle the rest — per-attendee checklists, timezone-local reminders, and a live nudge when the room opens.