What does this sync actually do?

It pulls your HubSpot contacts and deals into GTM Brigade on a recurring schedule and matches them to LinkedIn profiles using HubSpot's standard linkedin_url and hs_linkedinid fields. Every comment, reaction, or DM your reps make against a watchlist profile is logged in your GTM Brigade tenant with the matched HubSpot contact and deal context attached. The integration is read-from-HubSpot — it does not push custom properties back to HubSpot. RevOps exports the attribution data to HubSpot reports on their own cadence.

Who is this designed for?

B2B sales teams of 4–25 reps already running HubSpot as their CRM, with a defined ICP and an active LinkedIn motion. Most common fit is RevOps-led organizations that need pipeline attribution. It also fits sales-led orgs where the VP Sales is trying to prove LinkedIn ROI to a CFO. It doesn't fit teams without a CRM or teams where HubSpot contains fewer than 200 contacts.

How long does deployment take?

Sync is live on day 1 (HubSpot OAuth + initial contact pull take about 90 minutes). Watchlist build and voice model deployment take the rest of the 14-day window. By day 7 the first LinkedIn engagements are logged against matched HubSpot contacts in your tenant. By day 14 the in-tenant LinkedIn-sourced attribution lane is populated. RevOps typically builds the first export-to-HubSpot report by day 30.

What does this replace?

It replaces the Zapier or Make chains your RevOps team has been maintaining (typically 4–6 zaps, breaking weekly) plus any one-off scripts logging LinkedIn data manually. Most teams also retire their lead-routing tool's LinkedIn handoff workflow. Engineer hours saved usually pay for the seat cost in the first quarter. The sync handles HubSpot OAuth, rate-limit backoff, and retry logic natively.

How is this different from running a Zapier integration between Sales Nav and HubSpot?

Zapier-based integrations can move connection acceptances and a few InMail events. They cannot capture comments, reactions, post views, or watchlist context — that data is not exposed by LinkedIn's public API. GTM Brigade runs against the engagement surfaces directly and logs structured events with the matched HubSpot contact attached in the engagement view. Zapier is good glue for stable APIs. LinkedIn engagement data requires a purpose-built pipeline.

LinkedIn to HubSpot sync that keeps your watchlist anchored to real pipeline

The problem you're trying to solve

Your HubSpot has zero data on what's actually happening on LinkedIn. Reps are commenting on buyer posts, DMing prospects, and reacting to thought leadership — but none of it ever reaches the CRM. The contact record shows the cold-email sequence from 9 months ago, an old form fill, and nothing else. When an SDR asks "have we touched this person before?", the honest answer is "I think someone might have liked their post in March".

The RevOps team tried to fix it with Zapier. There are 4 zaps running: one for connection acceptances, one for InMail responses, one for form fills from LinkedIn ads, one for Sales Nav saved-lead alerts. They break weekly. The data they capture is shallow — timestamps and names, no context. When a deal closes, attribution shows "Direct" because LinkedIn engagement never made it into the same view as the deal.

Meanwhile your CFO wants LinkedIn ROI numbers. You don't have them because the data isn't anywhere reportable — it lives in 8 reps' heads and a few screenshots. This is the exact gap the RevOps workflow is built to close from the attribution side.

What GTM Brigade configures on day one

On day one we connect HubSpot via OAuth, pull your contacts and deals into your GTM Brigade tenant, and match them to LinkedIn profiles using HubSpot's standard linkedin_url and hs_linkedinid fields. This is the integration spec, not a marketing pitch.

What we read from HubSpot

GTM Brigade calls HubSpot's standard contact and deal endpoints (crm.contacts.basicApi.getPage and crm.deals.basicApi.getPage) and pulls the properties RevOps already maintains:

firstname, lastname, email — for contact identity
linkedin_url and hs_linkedinid — for LinkedIn profile matching (these are HubSpot's standard LinkedIn fields)
Deal dealstage, dealname, amount, closedate, hubspot_owner_id — so the rep's draft shows up with deal context attached

The sync runs on a recurring schedule (configurable, default hourly) so new contacts and deal-stage changes flow into your watchlist context without manual refresh.

What lives in your tenant

Every watchlist engagement — comments your reps leave, comments received on your reps' posts, reactions, DMs sent and received — is logged in your GTM Brigade tenant with the matched HubSpot contact attached. When a contact's HubSpot deal stage changes (e.g. moves from qualifiedtobuy to presentationscheduled), the watchlist re-prioritizes that profile automatically so reps know to engage warmer — exactly the deal-stage routing the AE workflow depends on.

The LinkedIn-sourced attribution lane is a report in your GTM Brigade tenant — it lists every contact-engagement-deal correlation so RevOps can build the HubSpot-side report on top of it.

What does NOT sync

We do NOT push custom properties back into HubSpot. Your HubSpot schema stays exactly as RevOps maintains it.
We do NOT write timeline events to HubSpot. Engagement data lives in your GTM Brigade tenant.
We do NOT modify deal records, lifecycle stages, or workflows.

The integration is deliberately read-direction. Most teams want their CRM schema left alone — we respect that.

What the first 90 days look like

By day 7 contact matching is live, by day 30 RevOps is exporting the first LinkedIn attribution reports, and by day 90 LinkedIn-sourced pipeline is a board-deck line item.

Days 1–14: HubSpot OAuth + initial contact pull (90 min). Watchlist build, voice models. First matched engagements log in your tenant by day 7.
Days 15–45: RevOps builds the first reports inside HubSpot using the exported attribution data. LinkedIn-sourced contacts segment cleanly. AEs see LinkedIn touch history when they pull up a contact in your tenant.
Days 45–90: Attribution becomes trustworthy. CFO gets the number. The Zapier zaps get retired.

What this is not a fit for

Skip this if you're not on HubSpot, your HubSpot has fewer than 200 contacts, or you don't have RevOps capacity to export and shape reports. Honest disqualifiers:

Not on HubSpot. This integration is HubSpot-first. Salesforce sync is also live but uses a different schema. If you're on Pipedrive, Close, or a custom CRM, this isn't the right fit yet.
HubSpot contains fewer than 200 contacts. The matching layer needs enough data to be useful. Teams running HubSpot as a 50-contact contact book don't benefit.
No RevOps capacity. The attribution data lands cleanly in your tenant, but somebody on your team needs to export it and shape the HubSpot-side report — the sales-manager workflow describes how front-line managers consume that data even without dedicated RevOps. We can recommend a template; we don't run RevOps for you.

How to know if this is the right play for you

A 30-minute walkthrough with one of our strategists is the fastest qualification path. We'll look at your current HubSpot setup, show exactly which contacts and deal properties we'd read on day one, and tell you in the meeting whether this materially improves your LinkedIn attribution — or whether you should fix something upstream in HubSpot first.