How SevenRooms guest profiles, visits, spend, reservations and private event inquiries can reach HubSpot, so a restaurant or hotel group runs brand, events and B2B marketing and group-wide reporting in HubSpot while SevenRooms keeps running service and venue marketing.
SevenRooms runs reservations, seating, guest profiles and marketing for restaurants, hotels and hospitality groups. Its guest profile holds visits, spend, tags and preferences, with one view of the guest across every venue in a group.
Documentation and credentials come only through the vendor, under a license, partner agreement or customer login.
Gated API. Access is requested through SevenRooms' partnership form and reviewed by its team. Credentials and the API reference come with approval.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
SevenRooms keeps the guest relationship at the venue; HubSpot adds the brand, events and B2B layer above it, with reporting across the group.
Campaign Creators assessment
SevenRooms offers a REST API for reservations, guest profiles, venues and feedback. SevenRooms grants access to approved venue operators and integration partners, with credentials issued for the client's venue group, so a direct SevenRooms-to-HubSpot integration can be built. SevenRooms has its own email marketing and automated emails, and those keep running for the venues. HubSpot takes the work that spans the group: brand campaigns, private events and corporate dining sales, partnerships, and reporting across venues. The first decision in the project is which messages each system sends.
Ratings are CC judgments from SevenRooms' public product pages. The API reference is shared with approved accounts, so endpoints, field names, event delivery and limits are confirmed with SevenRooms during discovery.
SevenRooms describes over 100 data points per guest, including visits, lifetime and itemized spend, tags, auto-tags, preferences and special occasions, unified across locations.
SevenRooms sends venue campaigns and automated emails. Each message type gets one sender, and a guest's venue-level marketing choices are respected in HubSpot.
API access is requested through SevenRooms' partnership form and reviewed by its team. Credentials and the API reference come with approval.
Seven parts of SevenRooms matter to HubSpot. Four carry the integration, two enrich it, and one is a scope decision the client makes before the build.
Contact details, tags and auto-tags, dining preferences and special occasions, held once for the whole venue group.
Reservations with venue, date and time, party size, booking channel, status and tags.
When a venue's point of sale is linked to SevenRooms, checks attach to guest profiles, giving visit counts and spend per guest.
When a requested date, party size or location isn't available, guests can submit an event inquiry with their contact details.
The venues in the client's group, used to label every reservation, visit and inquiry.
Post-visit feedback scores that SevenRooms collects for each venue.
SevenRooms' own email marketing and automated emails keep running for the venues. The client decides which programs HubSpot runs.
A CC-built integration layer reads SevenRooms changes, matches each guest to a HubSpot contact, maps marketing choices to HubSpot subscription types, computes visit and spend rollups, and writes in batches. HubSpot sends opt-outs back so both systems agree.
Reservations, seating, notes and allergies are managed in SevenRooms. HubSpot stores the results it needs and never edits a reservation.
Brand marketing, events and B2B sales, and reporting across venues happen in HubSpot, with the SevenRooms guest ID on every contact.
Each message type has one owner, recorded in the SOW, so guests never get two versions of the same email.
Each phase ends on a gate the client signs off before the next begins, so the fixed scope holds even if SevenRooms' API differs from what the public materials describe.
Submit SevenRooms' partnership request as a customer integrating a third-party system, list the venues in scope, and confirm which SevenRooms products the group uses (marketing, Event Management, POS links).
Pull sample guests, reservations, visits and inquiries. Document each field, confirm whether event delivery is available, and measure how many guests carry an email address.
Decide, per program, whether SevenRooms or HubSpot sends it, and map venue-level and group-level marketing choices to HubSpot subscription types.
Create the Visit and Venue custom objects, guest rollup properties, the events pipeline and the SevenRooms property group in a HubSpot sandbox.
Build the change reader, identity resolver, consent mapper, rollup engine, HubSpot writer and error replay. Connect one venue end to end.
Load current guests and an agreed window of past reservations, then compute rollups once.
Build brand, events and B2B workflows with sends paused, run two weeks in parallel, then switch on and add the remaining venues.
SevenRooms shares its API reference with approved accounts, so source fields below are described plainly. Exact field names and paths are confirmed in the API audit.
| SevenRooms field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Guest profile | ||||
| guest (client) ID | sr_guest_id | Contact | 7R → HS | Primary key. Stored as text. |
| Contact | ↔ Both | Match key #2. | ||
| phone | mobilephone | Contact | ↔ Both | Normalize to E.164. |
| first and last name | firstname, lastname | Contact | ↔ Both | Fill blanks only. |
| tags and auto-tags | sr_tags | Contact | 7R → HS | Multi-select of agreed tags only. |
| special occasions | sr_birth_month, sr_anniversary_month | Contact | 7R → HS | Month only. |
| dining preferences | sr_preferences | Contact | 7R → HS | Agreed preference tags; allergies and notes stay in SevenRooms. |
| venue-level marketing choice | Subscription type per brand or venue | Contact | ↔ Both | Opt-out on either side suppresses both. Confirm field in discovery. |
| group-level marketing choice | Subscription type: Group marketing | Contact | ↔ Both | Confirm field in discovery. |
| Reservations and visits | ||||
| reservation ID | sr_reservation_id | Visit | 7R → HS | Unique key on the Visit record. |
| venue | Venue association | Visit | 7R → HS | |
| reservation date and time | sr_visit_date | Visit | 7R → HS | |
| party size | sr_party_size | Visit | 7R → HS | |
| reservation status | sr_reservation_status | Visit | 7R → HS | Booked, completed, cancelled, no-show. Confirm values. |
| booking channel | sr_booking_channel | Visit | 7R → HS | Direct, partner channels, phone. |
| check total (from POS link) | sr_check_total | Visit | 7R → HS | Present when the venue's POS is linked. |
| Guest rollups · computed in the integration layer | ||||
| count of completed visits | sr_total_visits | Contact | 7R → HS | Across all venues in scope. |
| sum of check totals | sr_lifetime_spend | Contact | 7R → HS | |
| latest completed visit | sr_last_visit_date | Contact | 7R → HS | Drives win-back timing. |
| venue of latest visit | sr_last_venue | Contact | 7R → HS | |
| next upcoming reservation | sr_next_reservation | Contact | 7R → HS | Suppresses win-back while a booking is open. |
| Private events and feedback | ||||
| event inquiry contact details | Contact + Deal | Deal | 7R → HS | Inquiry becomes a deal in the events pipeline. |
| inquiry date, guest count, venue | sr_event_date, sr_event_guests | Deal | 7R → HS | |
| event status | dealstage | Deal | 7R → HS | Custom statuses mapped to stages. |
| event revenue | amount | Deal | 7R → HS | Confirm availability in the API. |
| feedback score | sr_last_feedback_score | Contact | 7R → HS | Low scores can open a ticket. |
SevenRooms grants API access per approved partner. Values SevenRooms does not publish are marked for confirmation.
| Topic | SevenRooms | HubSpot |
|---|---|---|
| Access model | Requested through SevenRooms' partnership form and reviewed by its team. Credentials are issued for the client's venue group. | Self-serve in the client portal. Custom objects need an Enterprise hub. |
| Interfaces | REST API for reservations, guest profiles, venues and feedback. The API reference is shared with approved accounts. | REST APIs: CRM objects, custom objects, associations, imports. |
| Authentication | Client credentials issued by SevenRooms and exchanged for a bearer token. Confirm the token flow in discovery. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Event delivery | Not described in public materials. Confirm whether webhooks are available; otherwise the build reads changes on a schedule. | HubSpot webhooks with a v3 signature for opt-outs. |
| Pagination & backfill | Not published. Confirm export or paged list options with SevenRooms. | Paged search and list APIs; CRM imports for large loads. |
| Rate limits | Not published. Confirm with SevenRooms. | Per-10-second burst and daily limits by subscription tier. |
| Sensitive data | Allergies, free-text notes and payment details stay in SevenRooms. HubSpot receives contact details, rollups and agreed tags. | Sensitive data properties on Enterprise; field-level permissions by team. |
Severity reflects impact on the SOW, not technical difficulty alone.
SevenRooms sends venue campaigns and automated emails. Without a sender-of-record decision, guests get duplicates. The SOW lists each program and its owner.
Credentials and the API reference come after SevenRooms approves the request. Make access a client-owned dependency with a date in the SOW.
Public materials do not describe webhooks. If none are available, the build reads changes on a schedule, and HubSpot updates within an agreed interval instead of instantly.
Phone-only bookings cannot receive HubSpot email. They are matched on phone and counted in venue reports, and reservation flows can ask for email.
Free-text notes and allergy details stay in SevenRooms. Only agreed tags and preferences reach HubSpot.
Venues create many tags. An agreed short list maps to HubSpot, and the list is reviewed each quarter.
Event inquiries become HubSpot deals with follow-up tasks and sequences, so no large-party lead goes cold.
Guests who book for their company roll up to HubSpot companies, giving sales a list of corporate accounts to grow.
Visits, spend, events and feedback by venue and brand in one HubSpot dashboard.
Hotel groups combine dining visits with stay data in HubSpot, so a guest's restaurant visits inform stay offers and the reverse.
Guests who stop visiting one brand receive offers from another brand in the group, within their marketing choices.
Low feedback scores open HubSpot tickets for the venue manager, with the visit attached.
Both systems keep doing what they do best. The integration gives HubSpot the guest data it needs, and the sender matrix keeps every guest on one message per moment.
All custom properties use the sr_ prefix in a SevenRooms property group. Rollups are calculated in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| sr_guest_id | SevenRooms Guest ID | Contact | Single-line text | Guest profile ID; unique |
| sr_tags | SevenRooms Tags | Contact | Multiple checkboxes | Agreed tags and auto-tags |
| sr_preferences | Dining Preferences | Contact | Multiple checkboxes | Agreed preference tags |
| sr_total_visits | Total Visits | Contact | Number | Count of completed visits |
| sr_lifetime_spend | Lifetime Spend | Contact | Number (currency) | Sum of check totals |
| sr_last_visit_date | Last Visit | Contact | Date | Latest completed visit |
| sr_last_venue | Last Venue | Contact | Dropdown (venue list) | Venue of latest visit |
| sr_next_reservation | Next Reservation | Contact | Date | Earliest upcoming booking |
| sr_last_feedback_score | Last Feedback Score | Contact | Number | Latest feedback |
| sr_reservation_id | Reservation ID | Visit | Single-line text | Reservation ID; unique |
| sr_party_size | Party Size | Visit | Number | Reservation party size |
| sr_booking_channel | Booking Channel | Visit | Dropdown | Reservation channel |
Choose the modules and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation. SevenRooms shares its API reference with approved accounts; endpoints, event delivery and limits are confirmed with SevenRooms during discovery.
Yes, through a custom build on the SevenRooms REST API, which covers reservations, guest profiles, venues and feedback. Access is requested through SevenRooms' partnership form and reviewed by its team, and credentials and the API reference come with approval.
Each SevenRooms guest becomes a HubSpot contact with agreed tags, visit and spend rollups and consent choices. Completed reservations become Visit records, each venue becomes a Venue record, and private event inquiries become deals in an events pipeline. HubSpot sends opt-outs back so both systems agree.
SevenRooms owns service: reservations, seating, notes and allergies, and HubSpot never edits a reservation. HubSpot owns the group view, with brand marketing, events, B2B sales and reporting across venues. Each message type has one sender, recorded in the SOW.
Seven phases, each closed by a client sign-off: discovery and the SevenRooms access request, an API audit, the sender-of-record and consent mapping, the HubSpot data model, a build that connects one venue end to end, a backfill, and a two-week parallel run before the remaining venues are added.
Timeline and cost depend on the number of venues, the SevenRooms products in use (marketing, Event Management, POS links), the history in scope and what SevenRooms' API returns once access is approved. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.