Integrations · intermediate · for gtm-engineer

Tipoff connects to HubSpot with your own private-app token, so your data stays in your portal under your control. Once connected, Tipoff mirrors qualified accounts and their buying committee into HubSpot, writes tier and ICP data into its own namespaced properties, and keeps them fresh — without ever touching the fields your team owns. This guide walks a GTM engineer through the token, scopes, and what actually gets written.

Create the private app in HubSpot

1. In HubSpot, go to Settings → Integrations → Private Apps and create a new app (name it something like "Tipoff sync").
2. On the Scopes tab, grant:
   • crm.objects.companies.read and crm.objects.companies.write
   • crm.objects.contacts.read and crm.objects.contacts.write
   • crm.schemas.companies.write — lets Tipoff auto-create its radar_* properties
   • crm.lists.read — so tier-based dynamic lists resolve
3. Create the app and copy the access token.

Connect the token in Tipoff

1. Open Integrations in Tipoff (workspace admins only).
2. Paste the token into the HubSpot field and save. Tipoff runs a live check against your account and confirms the portal ID.
3. The secret is stored encrypted and never echoed back — reads only return the last four characters.

What Tipoff writes (and never touches)

Tipoff follows strict CRM rules:

• Never deletes. A downgrade flips radar_tier/radar_status; records are never removed.
• Never overwrites your fields. On an existing company it writes only its own radar_* properties (radar_tier, radar_icp_score, radar_status, radar_source) and fills genuinely blank fields.
• Dedup-safe. Companies match by domain, contacts by email, so no duplicates.
• Every touched record is stamped radar_source so you can trace and filter what came from Tipoff.

Pushing tiers

Accounts enter HubSpot when you qualify them — with their buying committee attached and associated to the company. Tier lives on the radar_tier company property, which drives self-maintaining dynamic lists. Pushing tiers is confirm-gated (you explicitly opt in per push), and the daily job only refreshes accounts already qualified — it won't bulk-dump your whole target list. Like other Tipoff capabilities, CRM writes are metered in Tipoff credits.

Related: see connecting Pipedrive (same never-delete, never-overwrite rules) and account tiering vs. your ICP corpus.