Your data, where
it already lives.
Every registration, every verified check-in and every morning-after report flows into the tools your team already uses — natively, through Zapier, or through webhooks and CSV that ship with every plan.
CRM, payments, calendars, Slack and Sheets — configured in a couple of taps.
Signed JSON for every event and a morning-after export, on every plan.
Data moves only to the organiser who collected it, under RSVP consent.
EU events on EU-resident processing. Deletion propagates downstream.
- 12native connectors at launch
- 6webhook events, signed
- 7,000+apps reachable via Zapier
- 7:00 AMmorning-after report, local time
How it works
Three stages. The third one is where your stack plugs in.
Invitations go out by link — public in Discover or invite-only. RSVPs, registration answers, approvals and tickets are captured with explicit consent at the point of RSVP.
The door scans every ticket — online or from a local cache when the venue wifi fails. Scans reconcile server-side, by gate and tier, with a timestamp. This is the record.
The verified record flows out: to your CRM as attendance events, to Slack as alerts, to Sheets as live rows, to Stripe as settled payments — and as CSV and webhooks, always.
The catalogue
Native connectors are configured in the organiser's settings. Anything not listed is reachable through Zapier or a webhook.
- StripePayments · Ticket purchases · payouts · refunds
NativePaid ticket tiers settle to the organiser's own Stripe Connect account. EVNTS never holds funds; refunds and payouts follow your Stripe policy.
- Apple Wallet & CalendarAttendee · Passes · calendar events
NativeEvery ticket is an Apple Wallet pass with a rotating QR; every RSVP lands on the attendee's calendar with venue and start time.
- Google CalendarAttendee · Calendar events · updates
NativeOne itinerary for the week, mirrored to Google Calendar on Android and web. Time changes and venue updates propagate.
- HubSpotCRM · Contacts · attendance events · lists
NativeFor your own registrants, under the consent they gave at RSVP: verified attendance becomes a timeline event on the contact, registrations create or update contacts, no-shows are flagged for follow-up.
- SalesforceCRM · Leads · campaign members · attendance
NativeYour own registrants only: campaign members are created from registrations and marked Attended from verified check-ins — by gate and tier, with timestamps.
- SlackOps · Door alerts · daily report
NativeDoor alerts as they happen — VIP arrived, capacity at 90%, offline scans reconciled — and the morning-after report posted to a channel.
- ZapierAutomation · Triggers · actions
NativeEvery EVNTS event (RSVP, ticket, check-in, export) is a Zapier trigger scoped to your own events, so the data reaches any of 7,000+ apps without code.
- Google SheetsData · Live rows · exports
NativeA live sheet per event: registrations, approvals, tickets and check-ins, updated as scans happen. The morning-after export lands as a new tab.
- NotionOps · Pages · databases
Zapier / WebhookRun-of-show, host notes and the attendance summary into your event workspace.
- MailchimpMarketing · Audiences · tags
NativeAudiences of the guests who separately opted in to hear from you — re-invite the people who actually came, segment by tier. Guests who didn't opt in are never synced.
- AirtableData · Records · views
Zapier / WebhookGuest lists and operations bases kept in sync with registrations, approvals and check-ins.
- Google DriveData · CSV · PDF report
NativeThe morning-after report and the registration export delivered to a shared folder at 7:00 AM local time.
Privacy built into every layer
Attendees trust us with the fact that they were in a room. Integrations are built so that trust is never the price of convenience.
Registering never opts a guest into marketing or into being visible to other attendees. Each scope is asked separately at RSVP, and each is revocable.
Integrations move data only to the organiser who collected it. Nothing flows between events or between organisers.
Audience Verification reports are aggregate only — seniority, organisation mix, net-new reach. Never an individual's record.
An attendee's connections, messages and People-to-Meet activity never sync anywhere. They belong to the attendee.
Account deletion removes the individual's record from future exports and fires attendee.deleted so downstream systems can do the same.
EU events will be processed on EU-resident infrastructure from day one. Data is encrypted in transit and at rest.
See the Privacy Policy for the full picture.
Need a connector
we don't list?
Webhooks plus CSV will cover most stacks at launch. A public API follows — join the waitlist as an organiser and tell us what you run on.