Event integrations
Start from the files you already have.
TripPass does not ask you to rebuild your event somewhere else. It reads your exhibitor list, your floor plan and your schedule, and sends leads and activity back out to wherever you work.
Spreadsheet import
LiveCSV or Excel exhibitor lists with a saved column mapping you reuse each year.
Registration exports
LiveExhibitor and session exports from the registration system you already run.
Floor plan and booths
PilotFloor plan images and booth locations are supported; interactive booth mapping remains in pilot.
Lead capture and export
LiveConsented leads are visible to the correct exhibitor and available for export.
Lead delivery by email
In developmentNot labeled Live until authenticated sending, bounce handling, webhooks and demo isolation pass production testing.
CRM webhooks
PilotSigned delivery paths exist and remain subject to production connector validation.
REST API
LivePush exhibitors, sessions and updates programmatically with your own key.
Transportation · RideOS ecosystem
Livery and passenger connectors.
These connectors belong to the transportation side, where TripPass passenger technology runs inside RideOS. FlightAware is an existing integration for supported connected airport workflows, not a planned feature.
LimoExpress
LiveReservations, drivers, vehicles, and status webhooks on connected workflows.
FlightAware
LiveFlight status and terminal awareness on supported connected airport workflows.
Limo Anywhere
PlannedOn the roadmap. Same normalized status model.
GroundWidgets
PlannedAffiliate and farm-in job ingestion.
Ridebits
PlannedCloud dispatch with real-time GPS sync.
TripMaster
PlannedParatransit and NEMT booking import.
Fleetio
PlannedVehicle maintenance and inspection records.
Salesforce
PlannedAccount and opportunity-driven reservations.
HubSpot
PlannedCRM-triggered passenger workflows.
Mock connector
LiveTest the full passenger workflow before live credentials.
TripPass maps every provider's status vocabulary into a single normalized set (pending, confirmed, driver assigned, en route, arrived, onboard, completed, cancelled, no-show, attention required) so passenger updates stay consistent no matter which dispatch platform the operator uses.