How Breakout Works with HubSpot and Salesforce

A lot of B2B teams run HubSpot for marketing and Salesforce for sales. HubSpot holds the forms, scoring, and nurture. Salesforce holds the leads, contacts, accounts, campaigns, and the reps who work them. The two are usually already synced, with marketing ops having set the rules for how records move between them.

Breakout works with that setup as-is. It captures what happens on your site — in chat, in forms, in meetings — and sends each piece of data to the system that uses it: lead and form data go into HubSpot as a standard form submission, while conversation context and rep follow-ups go onto the Salesforce record.

What goes where

Since HubSpot is already set up to capture inbound leads and sync them to Salesforce, it's the right destination for pushing leads — Breakout's preferred path is through form submission, with direct-to-contact sync as a fallback. Everything else a rep needs, like a chat summary, goes to Salesforce directly or via HubSpot.

HubSpot and Salesforce already sync with each other, which is why Breakout never writes to both. Breakout writes lead data to HubSpot once, the existing HubSpot-to-Salesforce sync moves it across, and Breakout writes only sales context directly to Salesforce.

How Breakout works with HubSpot

Breakout sends lead data to HubSpot by submitting your HubSpot form through the Marketing Forms API — the preferred method, falling back to creating contacts directly through the CRM API only when that's not possible.

This matters because HubSpot treats a form submission as a marketing event: it runs the form's own logic, respects lifecycle and property-update rules, keeps page and campaign attribution attached, and shows up in form reporting. Creating a contact through the CRM API skips all of that and can overwrite properties marketing didn't intend to change.

Setup has three parts. You import the forms you already have — fields auto-map on import (email to email, firstname to first name, jobtitle to role, HubSpot selects to Breakout picklists), and you can review the mapping, drop optional fields, or mark one required before finalizing; fields HubSpot requires stay locked so the form can't break. All standard field types are supported. Forms with CAPTCHA enabled can't be imported, since CAPTCHA can't run inside a chat — you turn it off on the form, or duplicate the form and turn it off on the copy.

Submissions carry page and campaign context: the page URL, IP address, and the HubSpot tracking cookie (hutk), which HubSpot uses to link the submission to the visitor's browsing history. Breakout also spots UTM and Google, Facebook, Microsoft, and LinkedIn ad parameters on the form and offers to map them automatically, plus supports static values like a Salesforce campaign ID or any custom mapping you need.

Imported forms stay in sync: an imported form is a point-in-time copy, so you can check a linked form against its HubSpot source and pull in changes, previewed as a diff of fields added, removed, or changed. Export mappings update to match, and a form dashboard shows every form — native or HubSpot-linked — with its sync status; a linked form can also be unlinked into a standalone Breakout form while keeping its fields and export setup.

How Breakout works with Salesforce

Breakout both reads from and writes to Salesforce.

Reads are real time. When a visitor arrives, reverse-IP tells Breakout which company is on the site, and it reads that account's Salesforce attributes (accounts are matched on domain) — reps get alerted when one of their accounts is on-site, and Tier 1 accounts get priority for live chat. Once an email is known, Breakout checks Salesforce for an existing Lead or Contact and pulls the owner, so a returning visitor can be offered a chat with their account manager. This works the same way regardless of which marketing automation platform you use — routing and personalization run off Salesforce data even though lead data flows through HubSpot.

Writes add conversation context only. Breakout doesn't create Leads in Salesforce when you're running HubSpot — leads reach Salesforce through your existing HubSpot sync. What Breakout writes directly: an Activity on the Lead or Contact with the chat summary and transcript link for every meaningful conversation; a Task only when the conversation needs a follow-up; and for a booked meeting, an Activity recording the assigned rep plus a Task if there's prep needed before the call. Because the Lead or Contact needs to already exist in Salesforce for these writes to land, Breakout writes them with a short delay to give the HubSpot sync time to create the record first.

Large data — full chat transcripts, account-level visitor data — syncs in scheduled batches; high-intent signals sync immediately so routing and alerts aren't delayed.

Identifying the visitor

Breakout checks three signals in order to match a visitor to a contact: its own cached mapping from a prior match, an email the visitor typed in, or — for an anonymous returning visitor — the HubSpot cookie (hubspotutk). Each match is cached for later visits, and cookie matching only needs your website domain, set once when you import your first form.

On the Salesforce side, the same email is used to find the Lead or Contact and its owner — so a visitor can be matched to a HubSpot contact for form and meeting purposes, and to a Salesforce record for routing, in the same session. If someone chats without identifying themselves, Breakout stores the session and writes nothing to either system; once they give an email, their earlier activity is written too, so scoring and the rep's view include the full visit.

Meetings booked through Breakout

Visitors can book a meeting directly in the conversation using Breakout's calendar. Breakout resolves the contact first, by email or cookie, then creates the meeting in HubSpot, attaches it to that contact, and sets the meeting owner to whoever's calendar got booked. If it can't identify the contact, it doesn't create the meeting — so HubSpot doesn't end up with meeting records with no contact attached; the visitor can still submit the form, and the meeting is created once they're identified.

At the same time, Breakout writes an Activity on the Salesforce Lead or Contact recording the meeting and the assigned rep, plus a Task if there's prep needed — so the meeting lands on both systems with the same owner. If HubSpot is already handling meeting creation for you, Breakout skips this step.

Three lead-engagement scenarios

Explicit hand raise: the visitor asks for a demo, asks to talk to sales, or books a meeting. Breakout submits the HubSpot form with everything it collected plus page and cookie context; HubSpot runs its normal logic — updating lifecycle stage and score, or enrolling the lead in a fast-track workflow — and the sync moves the lead to Salesforce. Breakout also writes a Salesforce Activity with the conversation summary and transcript link, and for a booked meeting, records the rep and creates a Task. The rep sees the conversation and the next step right on the Lead record.

Email captured, lower intent: the visitor gives an email during a chat or content download. Breakout submits the form so HubSpot can add the behavior to scoring or enroll them in nurture, and writes a Salesforce Activity with the summary and transcript link — no Task unless the conversation needs a follow-up.

Conversation with no email: if the HubSpot cookie already ties them to a known contact, Breakout stores this context locally rather than writing it to HubSpot by default. If the visitor is anonymous, Breakout stores the session and writes it, with full history, once they identify themselves.

Setup

The HubSpot integration and form mapping are set up inside Breakout: connect HubSpot, import the forms you want Breakout to use, review the field mapping, confirm the attribution mappings Breakout suggests, and set your website domain so cookie matching works. The Salesforce integration is set up by Breakout together with your RevOps team, connecting through a dedicated Integration User authorized over OAuth.

HubSpot remains the system of record for leads and marketing, and Salesforce remains where reps work — Breakout sends data to both without requiring changes to how either is set up today. Lead data enters HubSpot as a form submission with full page, cookie, and campaign context, so attribution, scoring, and workflows work as intended, and your existing sync moves the lead to Salesforce. Breakout reads Salesforce in real time to route visitors to the right rep, and writes conversation summaries, transcript links, and follow-up Tasks onto the Lead or Contact record reps actually work from.