HubSpot Integration

Overview

The HubSpot integration is a full bi-directional sync between Avina and your CRM. It ensures Companies and Contacts are enriched with Avina signals, while pulling in HubSpot context to power signals, account intelligence, and drafting.

Purpose

Create and update Companies and Contacts in HubSpot automatically
Write Avina signals as timeline activities on those records
Pull HubSpot CRM data (contacts, deals, emails, activities, tickets) into Avina to enrich signal generation and insights
Provide sellers with buying signal context directly in HubSpot while enhancing Avina’s scoring and drafting

How It Works

The connection has two halves. They are granted separately and do different jobs.

Write — puts Avina inside HubSpot:
- Companies and Contacts created for organizations and people your CRM doesn’t have yet
- Timeline Notes carrying each signal’s summary and tags, on the related Company and Contact (and Deal where applicable)
- Automation destinations you configure: sequence enrollment, list membership, ad-audience sync
Read — pulls HubSpot back into Avina:
- Companies, Contacts, Deals, Tickets, and Engagements
- Powers the signal types that depend on your existing relationships, CRM-state filters in automations, and CRM context for AI drafting

Access & permissions

Write is the half most workspaces need, and for many it’s the only one they turn on — it’s what puts signals on your HubSpot records. Read is not required for most signal detection. It earns its place for the signal types that depend on your existing relationships, and for filtering automations on live CRM state.

Which half does what

Capability	Needs write	Needs read
Signal notes on the Company, Contact, and Deal timelines	✅	—
Creating a Company or Contact for a company or person your CRM doesn’t have yet	✅	—
Automation destinations — enroll in a sequence, add to a list, sync to an ad audience	✅	—
Champion movement — recognizing that the person who changed jobs was one of your contacts	—	✅
Outbound & re-engagement signals — scored against the email and activity history already in your CRM	—	✅
CRM-state filters in automations — e.g. exclude closed-won customers, or accounts with an open deal	—	✅
Account ownership context — routing a signal to the rep who already owns the account	—	✅

Most signal types need neither half. Web visits come from the Avina Web SDK; new hires, job postings, and social activity from Avina’s own data sources; ad engagement from your ad-platform integrations. All of that reaches the Signals Inbox whether or not HubSpot is connected at all.

Common misconception: write access is not what powers signal detection, and Champion Movement does not depend on it. What Champion Movement needs is read — Avina has to know who your existing contacts are before it can tell you one of them moved. Write only decides whether the result is published back into HubSpot.

What each grant gets you

Write only — the common setup. Every signal Avina can produce on its own lands on the right HubSpot records, and your automations can create companies and contacts, enroll people in sequences, and populate lists. Adding read — unlocks the relationship-dependent signal types above, lets automations filter on live CRM state (suppress accounts with an open deal, exclude closed-won customers, target a lifecycle stage), and feeds deal history, email engagement, and meeting notes into Avina’s drafting so outreach reflects the relationship you already have.

What write access actually touches

When signals push to HubSpot, Avina writes to three object types:

Object	What Avina does	What Avina never does
Notes (Activity)	Creates one note per signal, associated with the related Company and — where applicable — Contact and Deal. Each note is the summary sentence plus the tag line.	Edit or delete notes it didn’t author; touch tasks, calls, meetings, or emails on the timeline.
Companies	Creates a company when a signal surfaces an organization you don’t have. Matched on domain first, so an existing record is reused rather than duplicated.	Delete companies, or merge records you already have.
Contacts	Creates a contact when a signal surfaces a person you don’t have, and associates them with the company. Matched on email; a person with no email address is skipped.	Delete contacts, or change lifecycle stage, owner, or lead status on a record it didn’t create.

Avina never creates, edits, or deletes a Deal or a Ticket, and never modifies your portal’s configuration — workflows, properties, and settings are untouched. The one addition is automations you build yourself: if you configure a destination that adds a contact to a HubSpot list, enrolls them in a sequence, or syncs them to an ad audience, that destination writes the corresponding membership. Those writes only happen for automations you’ve explicitly created. Records Avina creates are Avina’s to keep current. Whether Avina also enriches properties on records it didn’t create is a per-workspace setting — if you want Avina to stay strictly create-only against your existing records, tell us at connect time and we’ll configure it that way.

What you control

Control	Where	Effect
Which halves you grant	Avina → Settings ▸ Integrations	Write and read are independent. Start with write only and add read later — or the reverse — without re-connecting from scratch.
Scope of the grant	HubSpot consent screen	The exact scopes Avina requests are listed at connect time, and stay visible afterwards under HubSpot ▸ Settings ▸ Integrations ▸ Connected Apps.
Who installs the app	The connecting HubSpot user	The install is only as broad as the scopes that user is permitted to grant, so a purpose-built integration user keeps the grant tight and easy to audit.
Which signals push	Avina → signal & automation config	Push is configured per signal and per automation, so you can send only the signal types you want in your CRM.
Record creation	Avina → automation destinations	Creating Companies and Contacts is a destination you enable, not an unavoidable side effect of turning on write.
Auditability	HubSpot	Every Avina-written note is attributed to the connected app, and every note carries an `avina_*` tag — so you can list, report on, or bulk-remove them at any time.
Revocation	Either side	Disconnect in Avina, or uninstall the app in HubSpot. Writes stop immediately; notes already written stay on your records until you remove them.

Access FAQ

Question	Answer
Do I need write access for Champion Movement signals?	No — that one needs read, so Avina knows which contacts are yours. No signal type requires write; write only controls whether signals appear on your HubSpot records.
We only granted write. What are we missing?	Champion movement and outbound/re-engagement signals, CRM-state filters in automations (open deals, closed-won), and CRM context in AI drafting. Everything else works as normal.
Will Avina overwrite data my team entered?	No. Avina creates notes, and creates companies/contacts you don’t already have. It does not delete records, and does not overwrite fields your team owns.
Does Avina create duplicates?	No. Companies are matched on domain and contacts on email before anything is created; an existing match is always reused.
Can I see everything Avina has written?	Yes. Build a list or report filtered on Note body contains `avina_` to see every note Avina has created — see Push to HubSpot.
What happens to Avina’s notes if we disconnect?	They remain in HubSpot as ordinary notes. Nothing is removed on disconnect, and nothing new is written.
Which HubSpot user should authenticate the connection?	A user with access to the objects you want synced — typically an admin, or a dedicated integration user created for this purpose so the grant is easy to audit and revoke.

Setup

Navigate to Settings → Integrations in Avina.
Select HubSpot.
Authenticate with your HubSpot account.
Save and verify the sync.

For details on how signals land in HubSpot (notes, tag schema, dynamic lists), see Push to HubSpot.

Use Cases

Signal visibility in your CRM

Every Avina signal is written as a timeline Note on the related Company and Contact records so your team sees buying intent directly inside HubSpot without switching tools.

Dynamic lists off signal tags

Each note includes standardized tags (e.g., avina_new_hire_signal, avina_web_visit_signal) that you can use to build dynamic lists and workflows. See Push to HubSpot for the full tag reference.

Automated CRM updates

When Avina surfaces a new prospect via a signal, the corresponding Company and Contact are automatically created or updated in HubSpot. No manual data entry required.

Personalized drafting

HubSpot deal history, email engagement, and meeting notes feed into Avina’s AI drafting engine, producing more relevant email copy and outreach.

Supported Actions in Automations

When building automations, HubSpot supports the following destination types:

Add to sequence: enroll contacts in a HubSpot sequence
Create lead/contact: add new contacts discovered by signals
Create account/company: add new companies to HubSpot
Add signals to contacts/accounts: attach signal data to existing records
Add to list: include contacts in static or dynamic HubSpot lists
Add to ad audience: sync to LinkedIn, Meta, or Google ad audiences via HubSpot

Sync Behavior

Initial sync: Avina pulls historical CRM data (companies, contacts, deals, activities, engagements) when first connected.
Ongoing sync: new data syncs bi-directionally in near real-time.
De-duplication: Avina matches contacts by email and companies by domain to prevent duplicates.

AI Sequences

HubSpot’s Sequences API is read/enroll only, so using HubSpot as a sending platform for AI Sequences requires a one-time manual setup (creating the sequence shell and custom properties in HubSpot). See AI Sequences in HubSpot for the full step-by-step.

​Overview

​Purpose

​How It Works

​Access & permissions

​Which half does what

​What each grant gets you

​What write access actually touches

​What you control

​Access FAQ

​Setup

​Use Cases

​Signal visibility in your CRM

​Dynamic lists off signal tags

​Automated CRM updates

​Personalized drafting

​Supported Actions in Automations

​Sync Behavior

​AI Sequences

Overview

Purpose

How It Works

Access & permissions

Which half does what

What each grant gets you

What write access actually touches

What you control

Access FAQ

Setup

Use Cases

Signal visibility in your CRM

Dynamic lists off signal tags

Automated CRM updates

Personalized drafting

Supported Actions in Automations

Sync Behavior

AI Sequences