HubSpot integration: companies and deals

Take Prairie Foods, the customer whose lanes anchor most of Roadmark's quoting examples. Its HubSpot company record links to its Roadmark customer, and the Mississauga → Joliet lane it ships sits under a deal a rep already has open. When Quoting prices a request on that lane, the draft can link to that deal instead of the two records drifting apart, one saying the deal's still open, the other showing it booked and paid. When the quote wins and becomes a load, Roadmark can close the deal and set its amount from the load, so the pipeline a sales manager reviews in HubSpot already reflects it.

What links, and which way it moves

Companies flow one way: Roadmark reads the company and uses it to match a customer, but it doesn't rewrite what a rep has entered about who they are or how to reach them. Deals are the two-way part. Roadmark reads what's open on a company so a linked quote points at the right deal, and when that quote is won or lost, it can write the outcome back, moving the deal's stage and amount rather than leaving a rep to update two systems by hand. Nothing about a customer's contract, rate or credit terms moves through HubSpot; those stay Roadmark's own record, the one billing and quoting price from.

Connecting it

Roadmark connects through a service key, HubSpot's account-level credential for system-to-system integrations. A super admin, or a user with developer tools access, creates one under Development → Keys → Service keys. Setting one up means choosing scopes rather than installing anything from a marketplace: the admin adds crm.objects.companies.read and .write and crm.objects.deals.read and .write, and HubSpot generates a key limited to exactly those objects. A key can only carry scopes the person creating it already has. Roadmark authenticates every request with that key; there's no broader OAuth install to approve, and nothing about contacts, tickets or marketing data is touched. Service keys take over from HubSpot's legacy private apps, which HubSpot stops letting accounts create during 2026; a private app that already exists keeps working. Once it's authorized, an admin matches each Roadmark customer to its company, which is the step that decides which quotes and loads show up where.

Running beside your CRM

Roadmark's own quoting works without HubSpot: prospects move through lanes-first stages, from a first conversation with expected volume attached through to a signed rate. Teams that already run their pipeline in HubSpot don't have to move it. The two stay in step through the linked company and deal instead, so a rep can work from either screen and see the same numbers.

Turning it off, and what's recorded

The connection works the same as any other integration on Security: every write it makes to a deal is recorded, who or what made it and when, and the connection itself can be turned off for a person, a team or the whole company at any time, from Roadmark rather than from HubSpot's service key settings. Nothing about the service key changes how sign-in works either; your team still signs in with the identity provider you already run.

See Quoting for how a price is built and Analytics for what a linked deal feeds into once the load closes, and Brokers for the inbox a request starts from.