HubSpot integration

Your HubSpot pipeline, next to the marketing that fed it.

Connect a HubSpot account and Supercurve reads your deals, companies and contacts, read-only, to show which marketing turns into revenue. This guide covers setup, permissions, the data it keeps, and how to disconnect.

What it does

Revenue, in the same place as the marketing.

HubSpot data shows up in three places in Supercurve. None of them write back to HubSpot.

The pipeline page

Deals by pipeline and stage, win rate, won value and the deals that are moving, next to the marketing that fed them. Open a deal to see its stage history, its original source and the contacts on it.

Curve's answers

Ask Curve how the pipeline is doing and it answers from stage totals, win rates and new companies and contacts, then ties them back to your campaigns and content.

Lookalike audience export

A CSV of the contacts on companies that won a deal, which you can download and upload to an ad platform yourself. Supercurve never sends it anywhere. Details below.

Setup

Four steps, no keys.

One person with access to the HubSpot account connects it once. Everyone on the team sees the result.

  1. 01

    Open Integrations

    In Supercurve, go to Integrations and pick the website the pipeline belongs to. HubSpot is on the Growth and Custom plans.

  2. 02

    Click Connect on HubSpot

    HubSpot opens and asks which account to connect. Review the read-only permissions listed below and approve.

  3. 03

    Let the first sync run

    Syncing starts right away. Deals arrive first; companies, contacts and deal history fill in over the next few syncs.

  4. 04

    Open the pipeline

    Analytics, CRM, HubSpot shows the pipeline. From then on Supercurve re-reads the account on a schedule, so it stays current.

Required permissions

Five read scopes, each for one job.

This is the full list HubSpot shows on the approval screen. Supercurve asks for nothing that can change your account.

crm.objects.deals.readRead deals, their pipelines and stages (to tell open, won and lost apart), and a deal's stage history.
crm.objects.companies.readRead the companies deals belong to: name, domain, industry, size, country and lifecycle stage.
crm.objects.contacts.readRead the contacts on those companies and deals: name, primary email, job title and lifecycle stage.
crm.objects.owners.readRead owner names, so each deal, company and contact shows who owns it.
oauthThe basic connection scope HubSpot requires of every app: the account's id and domain, and the email of the person who connected it.

Supercurve asks for no write scopes, and nothing for tickets, quotes, products, marketing emails, forms, workflows, files, calls, meetings, notes, conversations or webhooks. It does not read email bodies, call recordings or transcripts.

Data we read and store

What syncs, and what never does.

Supercurve keeps a copy of these fields so pages load fast and history survives. Anything not listed here is not stored.

DealsName, pipeline, stage and when it entered it, amount and currency, close date, probability, deal type, original source, owner name, the linked company and contacts, and every past stage with its date.
CompaniesName, domain, website, industry, employee count, annual revenue, country, city, lifecycle stage and owner.
ContactsFirst and last name, primary email address, job title, lifecycle stage, lead status, original source, company and owner. Phone numbers are never stored.
Pipelines and stagesEach pipeline's name and order, and each stage's name, order, whether it is a closed stage and its win probability.
AccountThe account's id and domain, the email of the person who connected it, and the owner names used for deal, company and contact owners.

The data is used for one thing: showing your team its own pipeline and recommendations in Supercurve. It is stored encrypted, visible only to your workspace, never sold, never used for advertising by Supercurve, and never used to train AI models. The full terms are in our privacy policy.

Lookalike audience export

A file for you, not a feed to ad platforms.

The pipeline page can export your won customers as a customer-list CSV, the kind Meta and LinkedIn accept for a lookalike audience. Here is exactly how it works.

Only when you ask

The file is built when a signed-in member of your team clicks Download on the pipeline page, and goes straight to their browser. Supercurve does not keep the file.

Never sent to an ad platform

Supercurve does not upload it to Meta, LinkedIn or anyone else, does not use it to advertise Supercurve or anyone else, and does not sell or share it. You decide whether it goes anywhere.

Small and chosen

Contacts with an email on companies that won a deal, nothing else. Email is always in; first name, last name, country, company, job title and won value are columns you tick.

Your call, your consent

Upload it only where you have the right to use those contacts for advertising, under your own privacy notice, the law that applies to you and the ad platform's customer-list terms.

Disconnecting

Two ways out, and the data goes on request.

Either one stops syncing at once.

From Supercurve

Integrations, HubSpot, Disconnect. Syncing stops and the access and refresh tokens are deleted from our servers straight away.

From HubSpot

Uninstall Supercurve under Settings, Integrations, Connected apps in HubSpot. The tokens stop working, and Supercurve shows the connection as needing a reconnect.

Deleting synced data

Data already synced stays so your history remains readable. Email privacy@supercurve.ai to delete it and we do so within 30 days. Deleting the website or your Supercurve account deletes it too.

FAQ

Questions, answered.

  • No. Every permission is read-only. Supercurve never creates, edits or deletes deals, companies, contacts or anything else in HubSpot.

  • No. The app does not ask for engagement permissions, so none of those are read. The pipeline comes from deals, their pipelines and stages, and the companies and contacts linked to them.

  • Members of your Supercurve workspace who have access to the website the connection belongs to. Access tokens stay on our servers, encrypted, and are never sent to the browser.

  • No. Curve reads your data to answer you and to write your recommendations. It is never used to train models, and it is never sold.

  • The data from the previous account is deleted before the new one syncs. One website holds one HubSpot account at a time.

  • HubSpot shows that notice for every app that is not yet listed on its marketplace. The permissions on the screen are the whole list, and this page describes exactly what each one is for.