Ready for Unlimited Possibilities?
Let's get the conversation started.
| HubSpot Object | RezMagic Object | Direction |
|---|---|---|
| Contacts | Guest / Passenger | External → HubSpot |
| Bookings (custom object or deals) | Reservation | External → HubSpot |
| Booking status | Reservation status | External → HubSpot |
| Event properties | Event / Sailing | External → HubSpot |
Each RezMagic booking appears in HubSpot on the guest's record with the related event and status, so the team has full context in one place.
RezMagic Booking → HubSpot ContactMarketing builds lists by event, booking status or travel history to promote upcoming events and re-engage past guests.
RezMagic Bookings → HubSpot Lists → CampaignsNew bookings and status changes trigger HubSpot workflows for confirmations, reminders and service follow-up.
RezMagic Status → HubSpot WorkflowsRezMagic is a reservation and booking platform for group travel, tours and events. We build a custom integration on Karana, our integration platform, that brings guests, bookings and event details from RezMagic into HubSpot. Reservations continue to be made and managed in RezMagic, while HubSpot gives sales, marketing and service teams a complete view of each traveler.
A typical setup creates or updates a HubSpot contact for each guest, records each booking with its status and the related event, and keeps that information current as bookings change. The exact objects and fields, including whether bookings are stored as deals or as a custom object, are confirmed in a field mapping document before the build starts.
Yes. Once bookings are in HubSpot, marketing can build lists by event, booking status or travel history, promote upcoming events to past guests, and exclude travelers who have already booked from promotional campaigns. Workflows can also send confirmations and reminders based on booking changes.
RezMagic stays the system of record for reservations, inventory and payments, and HubSpot is the system of record for relationships, marketing and service. Each field has a defined owner in the mapping document, so the two systems never overwrite each other and the team always knows where a change should be made.
Yes. Which events and booking types sync, how often updates run, how guests are matched to existing contacts, and how bookings are modeled in HubSpot are all scoped to your process. We document the design, test it before go-live, and maintain the integration on Karana after launch.