Set up live sync with HubSpot

HubSpot live sync replaces the manual CSV-export step with a continuous background pull from your HubSpot account, so closed-lost deals show up in Thawly automatically and stay current as your team edits them.

What live sync does#

• Thawly watches your HubSpot account for new and updated closed-lost deals across every pipeline you give it access to.
• Lost deals you mark in HubSpot appear in Thawly automatically — no re-export, no re-upload.
• Re-engagement signals fire when one of your monitored companies' UK public-data triggers (a leadership change, a new contract win, a statutory filing, a job advert pattern shift) lines up with a closed-lost deal in your HubSpot.

What data Thawly reads#

Read-only access by default. The HubSpot OAuth consent screen will show the following scopes:

• oauth — HubSpot-required scope that issues the refresh token Thawly uses to keep the connection alive without re-prompting you. It does not grant any additional data access on its own; the read scopes below define what Thawly can actually see.
• crm.objects.deals.read — pull deals + stages + amount + close date + lost-reason field.
• crm.objects.contacts.read — pull the job title of the most-recent contact on each deal so the AI knows whether it's writing to a CFO, a Head of IT, or a Procurement Lead.
• crm.objects.companies.read — pull the associated company name and website so Thawly can match it to Companies House.

Thawly never sees contact-level personal data — no email addresses, no phone numbers, no contact names. Only job title and company-level deal context.

What Thawly never does#

• Never writes back to HubSpot. HubSpot's Developer Projects platform doesn't currently expose a granular notes-write scope that Thawly can request without also being able to mutate your deals (stages, amounts, owners). We refuse to take that broader scope, so HubSpot connections are read-only end-to-end — no "Re-engagement attempt" notes land on the source deal. For CRMs in your stack that do support write-back (Salesforce, Zoho, Capsule, Close, Copper, Dynamics, Pipedrive) the note lands automatically when a rep clicks Copy on a digest.
• Never deletes records.
• Never reads internal notes, files, or private contact data beyond the scopes listed above.
• Never modifies deal stages, owners, amounts, or close dates.

Set up#

Click below to connect. Thawly first shows a quick setup step where you choose your sync cadence (one-time import or ongoing sync), then redirects you to HubSpot's sign-in page to grant the read-only permissions listed above. After approval, you're back in Thawly with sync active.

Heads-up: HubSpot will show an "unverified app" warning, then a second screen asking you to type I accept the risk to continue. This is HubSpot's standard prompt for any app installed outside their public App Marketplace — it is not a security issue with Thawly. We're applying for Marketplace verification, which will remove the warning. Type the phrase exactly, click Connect — you'll only see this once per HubSpot account.

Connect HubSpot →

You'll be asked to sign in to the HubSpot account that owns your sales pipelines (admin seat recommended for the first connection — once connected, the link survives admin handoff), then to Grant access on the permissions screen. The first sync runs immediately and typically takes 1–3 minutes for under a thousand deals.

If you'd rather skip OAuth and do a one-off CSV export instead, the manual route still works: Migrate from HubSpot.

After setup#

• Sync runs every 15 minutes in the background.
• See sync status, last-sync time, and total deals imported on the integrations page.
• Disconnect any time from Settings → Integrations — revokes the OAuth token and stops all future syncs. Already-imported deals stay in Thawly.
• If the connection breaks (e.g. token revoked from HubSpot's side), the card flips to a red "Reconnect" state and you'll get an in-app banner. Sync resumes the moment you reconnect.