Integration Products | Campaign Creators

Toast HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 17, 2026, 3:40:23 PM
Integration Assessment
Integration Assessment · Hospitality

Toast × HubSpot

How a restaurant brand on Toast can turn orders, locations and menus into guest records, visit and spend profiles, and catering leads HubSpot can segment, automate and report on, and which Toast API access tier each part needs.

Toast REST APIsStandard API accessCustom integration accessOrders and menus webhooksMulti-location brandsRead-only by default
Platform ownerToast, Inc.
Integration typeCustom build on Toast APIs
Primary directionToast → HubSpot
FeasibilityBuildable, tier-dependent
API accessOpen with conditions
01 — Summary

Does Toast integrate with HubSpot?

Toast is a restaurant point-of-sale and operations platform. Every order, check, menu and location lives in Toast, and multi-location brands manage them as one restaurant group.

API access
Open APIOpen with conditionsGated API

Public documentation, but production access needs vendor approval, certification, a paid license or a specific plan.

Open with conditions. Standard API access is read-only and needs the right Toast subscription at each location. Anything that writes to Toast needs a custom integration approved through Toast.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

Toast can feed HubSpot reliable order, spend and location data, with guest identity strongest on takeout and delivery orders.

Campaign Creators assessment

Toast publishes REST APIs for orders, menus, restaurants, configuration, labor and stock, authenticated with client credentials. A restaurant brand can buy Standard API access and create its own read-only credentials, including webhooks for orders and menus. That is enough for a HubSpot integration that reads data. Writing to Toast needs a custom integration arranged through the brand's Toast account representative. The main limit is identity: Toast documents that standard API access returns guest details only for takeout and delivery orders, so dine-in spend is reported by location unless the guest is otherwise identified.

Scorecard
Order dataHigh
Real-time eventsWebhooks
Guest identityTakeout & delivery
Build complexityModerate

Scores are CC judgments from Toast's public developer documentation. The brand's access tier, scopes and Toast subscription are confirmed per location in discovery.

Strength

Push-based orders, self-serve credentials

With Standard API access, the brand creates read-only credentials in Toast Web and subscribes a CC-hosted URL to the orders webhook, which fires on every new or updated order.

Plan for

Anonymous dine-in checks

Guest name, email and phone come back only for takeout and delivery orders. Dine-in spend without a guest attached is reported at the location level, not on a contact.

Gate

Access tier sets what is possible

Standard API access is read-only and needs the right Toast subscription at each location. Anything that writes to Toast needs a custom integration approved through Toast.

02 — API modules

Which Toast APIs does the integration use?

Seven building blocks shape the integration. Three carry it, two enrich it, one sits outside the published read APIs, and one is a scope decision.

Core

Orders API

orders:read · GET /orders/v2/ordersBulk

Orders, checks, selections and payments for each location, searchable by business date for backfill.

  • Dining option, revenue center, source and guest count
  • Check totals and menu item selections
  • guest.pi:read adds the guest on takeout and delivery
Core

Orders webhook

Event type order_updated

Pushes the full order to a CC-hosted URL whenever an order is created or updated.

  • Guest details omitted from the push; fetched by order GUID
  • Payloads can exceed 600 KB
  • Subscribed in Toast Web under API access
Core

Restaurants & configuration

restaurants:read · config:read

Location name, address and hours, plus the dining options and revenue centers that give each order its meaning.

  • One HubSpot Location record per Toast restaurant
  • Dining option behavior: dine-in, takeout, delivery
  • Low change rate; synced daily
Enrichment

Menus API

menus:read · Menus v2

Fully resolved menus per location, used to group order selections into categories for item affinities.

  • Menu groups become affinity options
  • Menus webhook for changes
  • One request per second per location
Low CRM value

Labor, stock & cash

labor:read · stock:read · cashmgmt:read

Employees, shifts, inventory and cash drawer events. Useful for operations, rarely for guest marketing.

  • Server name on a check, if wanted
  • Out-of-stock items to pause promotions
  • Usually left out of scope
Confirm with Toast

Toast loyalty and gift cards

Not in the published read APIs

Toast's loyalty and gift card APIs are built for outside providers to plug into Toast. Reading the brand's own Toast loyalty members and gift card balances is not part of standard API access.

  • Loyalty info on a check appears when a loyalty service is attached
  • Confirm any other access with the Toast account representative
  • Gift card sales may appear as order items; confirm in discovery
Scope decision

Guest messaging in HubSpot

Email · SMS · offers

HubSpot becomes the one place guest marketing runs from. If guest messages go out from Toast today, the plan assigns each message type to one sender.

  • List which guest messages run today, and from where
  • Move each one to HubSpot or leave it in Toast, never both
  • Bring existing opt-outs into HubSpot first
03 — Framework

How does the Toast HubSpot integration work?

Toast pushes order events to a CC-hosted endpoint. The integration layer fetches guest details by order GUID, resolves identity, rolls up visits and spend, and writes to HubSpot in batches. Locations and menus sync daily.

Toast APIs
Orders webhookorder_updated events
Orders APIorder detail, ordersBulk backfill
Restaurants & configlocations, dining options
Menus APImenu groups and items
CC integration layer
Webhook receiververifies source, queues events
Order enricherfetch guest by order GUID
Identity resolveremail → phone → name + location
Aggregatorvisits, spend, RFM, affinities
HubSpot writerbatch upserts, error replay
HubSpot
Contactsguest profile and rollups
Ordersidentified takeout and delivery orders
Locations (custom object)one record per Toast restaurant
Dealscatering and group-event orders
Lists & workflowswin-back, first visit, catering
Toast → HubSpot (primary flow)HubSpot → Toast (only with custom integration access)
Principle

Aggregate, don't mirror

A busy location closes thousands of checks a week. HubSpot stores identified orders and rollups; line-level detail stays in Toast and its reporting.

Principle

Location is always known

Every order carries its restaurant GUID, so spend is reported by location even when the guest is anonymous.

Principle

Read first, write by exception

The default build reads from Toast. Any write to Toast is a named item in the SOW with its own Toast approval.

04 — Process

What does Toast HubSpot integration setup involve?

Each phase ends on a gate the brand signs off before the next begins, so the fixed scope holds even if Toast access or data differs from what was expected.

1

Discovery & access

Confirm the brand has Standard API access and the Toast subscription each location needs for webhooks. Create read-only credentials in Toast Web with the agreed scopes, and decide whether any write needs a custom integration request.

Gate to next phaseCredentials return orders and restaurants for a pilot location
2

Data audit & identity rules

Pull 30 days of orders. Measure the share of orders with a guest, how dining options and revenue centers are set up, and how catering orders are marked.

Gate to next phaseSigned match rules and a measured identified-spend rate
3

Messaging ownership

List guest messages sent today, by Toast or anyone else, and assign each one to a single sender. Map opt-outs to HubSpot subscription types.

Gate to next phaseSigned sender-of-record matrix
4

HubSpot data model

Create the Location object, guest rollup properties, the order pipeline, the catering deal pipeline and affinity options in a HubSpot sandbox.

Gate to next phaseSchema approved and created
5

Integration build

Build the webhook receiver, order enricher, identity resolver, aggregator and batch writer, paced to Toast's per-location limits.

Gate to next phaseOne pilot location syncing end to end
6

Backfill

Load 12 months of orders through ordersBulk in windows of one month or less, then compute rollups once.

Gate to next phaseRollups reconcile to Toast reports within an agreed tolerance
7

Workflows, parallel run & rollout

Build win-back, first-visit and catering workflows with sends paused, run two weeks in parallel, then add remaining locations in waves.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Toast HubSpot integration sync?

Toast field names follow the Orders, Restaurants and Menus APIs as Toast documents them. Exact paths and catering markers are confirmed against the brand's locations during discovery.

Toast fieldHubSpot propertyObjectDirectionNotes
Guest identity · check customer (guest.pi:read)
checks[].customer.emailemailContactToast → HSMatch key #1. Takeout and delivery orders.
checks[].customer.phonephoneContactToast → HSMatch key #2. Normalize to E.164.
checks[].customer.firstName / lastNamefirstname, lastnameContactToast → HSFill blanks only.
checks[].customer.guidtoast_guest_idContactToast → HSStored for matching later orders.
first order businessDatetoast_first_order_dateContactToast → HS
deliveryInfo.city / zipCodecity, zipContactToast → HSNeeds delivery address scope; off by default.
Visits & spend · Orders API
max(order.businessDate)toast_last_order_dateContactToast → HSIdentified orders only.
count(orders) 90 days / 12 monthstoast_orders_90d, toast_orders_12mContactToast → HSComputed in the integration layer.
sum(checks[].amount)toast_lifetime_spendContactToast → HSBefore tax and tip; rule agreed in discovery.
avg(checks[].amount)toast_avg_checkContactToast → HS
recency, frequency, spendtoast_rfm_segmentContactToast → HSSegment labels agreed with marketing.
restaurant GUID (mode)toast_favorite_locationContactToast → HSMost-ordered location in 12 months.
diningOption behaviortoast_preferred_channelContactToast → HSTakeout, delivery or dine-in.
order.sourcetoast_order_sourceOrderToast → HSOnline ordering, in store and other channels.
selections[] by menu grouptoast_item_affinitiesContactToast → HSTop menu groups, not every item.
Orders, catering & groups
order.guidhs_external_order_idOrderToast → HSIdentified orders only.
order.businessDate / closedDatehs_createdate, toast_business_dateOrderToast → HS
checks[].totalAmounths_total_priceOrderToast → HS
order.numberOfGueststoast_guest_countOrderToast → HS
catering dining option or total over thresholdDeal in Catering pipelineDealToast → HSMarker and threshold agreed with the brand.
checks[].appliedLoyaltyInfotoast_loyalty_identifierContactToast → HSPresent when a loyalty service is attached.
Locations & menus · Restaurants, Config, Menus
restaurant GUIDtoast_restaurant_guidLocation (custom)Toast → HSPrimary key.
restaurant name / location addressname, address fieldsLocation (custom)Toast → HS
restaurant group GUIDtoast_group_guidLocation (custom)Toast → HSGroups locations for multi-brand reporting.
dining optionstoast_dining_optionsLocation (custom)Toast → HSReference for channel mapping.
menu groupsaffinity optionsContactToast → HSDaily; one call per second per location.
06 — Auth & API

How are authentication and API limits handled?

Toast uses client credentials and a per-request location header; HubSpot uses one app token. Values Toast does not publish are marked for confirmation.

TopicToastHubSpot
AuthenticationPOST /authentication/v1/authentication/login with clientId, clientSecret and userAccessType TOAST_MACHINE_CLIENT. Returns a Bearer JWT with an expiry in seconds.Private app access token or OAuth 2.0 public app.
Location targetingEvery location-specific call carries the Toast-Restaurant-External-ID header with the restaurant GUID.One portal for all locations; Location records separate them.
Access tiersStandard API access: read-only GET, credentials created by the brand in Toast Web. Custom integration: read and write, arranged through the Toast account representative. Partner integration: issued by the Toast integrations team.Self-serve in the portal; custom objects need an Enterprise hub.
Real-timeWebhooks for orders, menus, stock, restaurant availability, online ordering schedule and packaging. Standard API access needs the Manage Integrations permission and the required Toast subscription at each location.Webhooks or workflows for HubSpot-side changes, such as unsubscribes.
Rate limits20 requests per second and 10,000 per 15 minutes. GET /menus: 1 per second per location. ordersBulk: 5 per second per location, windows of one month or less. 429 with Retry-After.Per-10-second burst and daily limits by subscription tier.
Guest dataguest.pi:read returns the check customer on takeout and delivery orders only. The orders webhook omits guest details.Contacts hold only what the brand approves; no card data.
Sensitive dataPayments carry card references. CC never syncs card numbers, only tender type and amount.No payment card data stored in the CRM.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Dine-in guests are mostly anonymousHigh

Spend without a guest cannot reach a contact. Measure the identified share in the data audit and set reporting expectations before promising guest-level automation.

Access tier decides the scopeHigh

Standard API access is read-only. Writing guests, orders or menus to Toast needs a custom integration approved through Toast. Make the tier a client-owned dependency in the SOW.

Loyalty and gift card dataMedium

Toast's own loyalty members and gift card balances are not in the published read APIs. Confirm with the Toast account representative before scoping them.

Two senders for one guestMedium

If Toast already sends guest marketing, agree which system sends each message type, so guests hear from the brand once.

Volume and per-location limitsMedium

Writing every check to HubSpot would exhaust limits and clutter the CRM. Aggregate in the integration layer and pace backfills to Toast's per-location limits.

Mixed subscriptions across locationsLow

Webhooks need the right Toast subscription at each location. A location without it is covered by a scheduled ordersBulk pull until it is upgraded.

Opportunities in HubSpot

Guest value profile on every identified contactHigh value

Last order, frequency, lifetime spend, average check, favorite location and channel become filters for every list and workflow.

RFM segments that update themselvesHigh value

Recency, frequency and spend segments recalculate after each order, so win-back and VIP journeys always target the right guests.

Catering and group-event pipelineHigh value

Catering and large-party orders create deals for the catering or events team, with follow-up tasks and repeat-order nurture.

Menu-item affinitiesMedium value

Guests who order from a menu group get launches and offers for that group, by location.

Location reporting in one placeMedium value

Location records tie guests, orders and campaigns together, so marketing can report campaign-driven orders by site and by brand.

First-order welcome by channelNice to have

A guest's first online or delivery order starts a welcome journey tailored to how they ordered.

Rollout order

Start with what Toast already gives you.

The integration grows with the brand's Toast access. Read-only access delivers most of the marketing value; write access is added only when a use case needs it.

  1. Locations first: one HubSpot Location record per Toast restaurant, grouped by brand.
  2. Orders next: identified takeout and delivery orders with visit and spend rollups and RFM segments.
  3. Catering and groups: large and catering orders become deals in their own pipeline.
  4. Extend by exception: write-back, loyalty or gift card data once Toast confirms the access.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the toast_ prefix in a Toast property group. Rollups are calculated in the integration layer so they are consistent across reports.

Internal nameLabelObjectTypeSource / logic
toast_guest_idToast Guest IDContactSingle-line textchecks[].customer.guid
toast_first_order_dateFirst OrderContactDateEarliest identified order
toast_last_order_dateLast OrderContactDateLatest identified order
toast_orders_90dOrders (90 days)ContactNumberCount of identified orders
toast_orders_12mOrders (12 months)ContactNumberCount of identified orders
toast_lifetime_spendLifetime SpendContactNumber (currency)Sum of check amounts
toast_avg_checkAverage CheckContactNumber (currency)Lifetime spend ÷ orders
toast_rfm_segmentRFM SegmentContactDropdownRecency, frequency and spend bands
toast_favorite_locationFavorite LocationContactDropdown (location list)Most-ordered location, 12 months
toast_preferred_channelPreferred ChannelContactDropdownDining option behavior
toast_item_affinitiesItem AffinitiesContactMultiple checkboxesTop menu groups
toast_restaurant_guidToast Restaurant GUIDLocationSingle-line textUnique key
09 — Scope builder

Interactive scope builder

Choose the APIs 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.

Scope summary

0Fields
0Inbound
0Write-back
Toast × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Toast HubSpot integration FAQ

Does Toast integrate with HubSpot?

Yes, through a custom build on Toast's REST APIs. Standard API access gives the brand read-only credentials, including orders and menus webhooks, which is enough for an integration that reads Toast data. Writing to Toast needs a custom integration approved through Toast.

What data syncs between Toast and HubSpot?

Guests on takeout and delivery orders become HubSpot contacts with visit, spend, favorite location and item affinity rollups. Identified orders sync to HubSpot orders, each Toast restaurant becomes a Location record, and catering orders become deals. Dine-in spend without a guest attached is reported by location.

Which system owns which data?

Toast owns orders, checks, menus and locations, and HubSpot stores identified orders and rollups rather than every line item. HubSpot owns guest marketing, with each guest message type assigned to one sender. The default build only reads from Toast.

What does setting up the Toast HubSpot integration involve?

Seven phases, each closed by a brand sign-off: discovery and access, a data audit with identity rules, messaging ownership, the HubSpot data model, the integration build on a pilot location, a 12-month order backfill, and a two-week parallel run before workflows go live and remaining locations are added in waves.

How long does the integration take and what does it cost?

Timeline and cost depend on the number of locations, the Toast access tier, the order history in scope and whether any write to Toast is needed. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.