HubSpot is the default marketing automation platform for most B2B teams, and Breakout is built to fit into it rather than replace it. Forms live in one place, conversational signals flow back to HubSpot automatically, and the right contact gets the right meeting — without anyone managing two systems or writing code.
Unlike tools that only integrate deeply with Salesforce, Breakout is natively built for both HubSpot and Salesforce. The integration is owned by the marketing ops team: import your existing HubSpot forms, submissions flow back the moment they happen, visitors resolve to the correct contact, and meetings tie to that contact and its owner — all point-and-click, no API work.
The preferred method: push lead data through the Forms API
The core design decision is how lead data reaches HubSpot. Breakout pushes data through HubSpot's Marketing Forms API — submitting the form — rather than creating contacts directly through the CRM API.
That matters because a form submission is a first-class marketing event: it runs the form's own logic, respects lifecycle and property-update rules, keeps page and campaign attribution intact, and ties into form-based reporting. Writing contacts directly through the CRM API bypasses all of that, and can overwrite properties in ways marketing didn't intend.
Many signal-capture tools push contacts directly or pass a thin field set with no page, cookie, or campaign context — breaking attribution and creating cleanup work. Breakout avoids that entirely: it enters HubSpot the same way a native form submission does, so nothing downstream needs to be reworked.
Form import: bring your HubSpot forms into Breakout
Teams import existing HubSpot forms directly rather than rebuilding them. Field names and types auto-map on import — email to email, firstname to first name, jobtitle to role, HubSpot selects to Breakout picklists — and teams can review the mapping, exclude optional fields, or mark a field required before finalizing. Required HubSpot fields stay locked so the form can't break.
Breakout supports the full range of HubSpot field types: single- and multi-line text, number, checkbox, radio, multi-select, picklist, and hidden fields.
One guardrail: forms with CAPTCHA enabled can't be imported, since a bot-detection challenge can't run inside a conversational flow. Breakout flags this and asks the team to disable CAPTCHA before importing.
Export mapping: context and attribution travel with every submission
Every submission carries full context, not just field values: the page URL (pageUri), IP address, and the HubSpot tracking cookie (hutk) used for identity resolution. Breakout also detects UTM and Google, Facebook, Microsoft, and LinkedIn ad parameters on the form and offers to map them automatically, so paid and campaign attribution flows through unchanged. Teams can add static values — a Salesforce campaign ID, for example — and custom mappings as needed.
Form sync: keep imported forms current
An imported form is a point-in-time copy, so Breakout lets teams check a linked form against its HubSpot source and sync changes on demand, previewing exactly what will change first.
Sync detects added fields, removed fields, and configuration changes, and surfaces each as a reviewable diff. Export mappings update to match — new fields resembling known campaign parameters get suggested automatically, and mappings for deleted fields are removed. A form management dashboard shows every form, native or HubSpot-linked, its sync status, and lets a linked form unlink into a standalone Breakout form while keeping its fields and export config.
Identity resolution: matching visitors to HubSpot contacts
For meetings and personalization, Breakout resolves a visitor to the right HubSpot contact by checking the cheapest, most reliable signal first: its own cached mapping, then email if the visitor has provided one, then the HubSpot cookie (hutk) for anonymous visitors. Once resolved, the mapping is cached so future interactions match instantly.
Cookie-based resolution reads the hubspotutk cookie on the customer's domain, configured once at import time by specifying the website domain.
Meetings tied to the right contact and owner
When a visitor books a meeting, Breakout resolves the contact first — by email or cookie — then creates the meeting in HubSpot, associates it with that contact, and sets the meeting owner to whoever's calendar was booked. If no contact can be resolved, Breakout deliberately skips creating the meeting rather than leaving an orphan record. Anonymous visitors can still submit forms through the Forms API; meeting creation simply waits until they're identified.
The result: HubSpot stays the system of record, and marketing ops doesn't have to change how it runs the platform. Existing forms import and stay in sync, every submission carries full context, visitors resolve to the right contact through a cached lookup, and meetings land on the correct owner with no orphan records — all without adding manual work for the team that owns HubSpot.
