HubSpot integration for Ruby AI

The Ruby AI HubSpot integration is a two-way CRM connection: Ruby reads the deals each rep owns along with the history behind them, and writes deal intelligence back onto the HubSpot record. An admin connects it once and every rep in the Ruby org inherits it.

At a glance

Why connect HubSpot to Ruby AI?

• Reps stop retyping deal data into two systems. Import takes one click per deal.

• Managers reviewing pipeline in HubSpot see Ruby's analysis on the record, not in another tool.

• Each rep sees only the companies and deals they own in HubSpot. Owner scoping is enforced on every read.

• Ruby's own notes are excluded from import, so analysis never gets fed back into itself.

How does Ruby AI use HubSpot?

Ruby reads companies, deals, contacts, owners, pipelines and property schemas, plus the five activity types associated with a deal. Everything is scoped to the connecting rep's HubSpot owner ID. Ruby members are matched to HubSpot owners by email address, and a rep with no matching HubSpot user is told so explicitly rather than shown an empty list.

Deal stages map to Ruby's stages by position in your pipeline, so custom pipelines work without configuration. Rich-text note and email bodies convert to markdown before the agents read them.

Ruby never reads records outside the connecting rep's ownership, and never runs an unfiltered fetch of the portal. The scopes Ruby requests are documented in HubSpot's OAuth scope reference.

What does Ruby AI put into HubSpot?

Four deal properties, created automatically at connect inside a property group called Ruby Insights: Pain / Impact, Compelling Event, Risks, Recommended Actions. Ruby fills them from the meeting analysis, deal health and sales strategy agents.

A meeting analysis note per meeting, formatted as a HubSpot timeline note with headings and bullets. Because HubSpot does not render tables in the timeline, Ruby converts them into readable blocks. Notes cap at 65,536 characters.

A pre-meeting brief note per calendar event, so the prep sits on the record before the call.

Stakeholder contacts with buying roles. Ruby matches by contact ID, then email, then LinkedIn URL, updates name, title, email, phone and LinkedIn, and associates the contact to the deal with a labeled association: Champion, Economic Buyer, Technical Validator, User, Procurement, Compliance, Blocker or Approver.

Standard field updates. Change amount, close date or stage in Ruby and Ruby patches the HubSpot deal to match.

Every write is content-hashed. Nothing unchanged is rewritten. Ruby never sets the deal owner, so a Ruby sync cannot reassign a rep's deal.

How do I connect HubSpot to Ruby AI?

1. Sign in to Ruby AI as an organization admin and go to Settings → Integrations → HubSpot.

2. Approve the scopes on HubSpot's own authorization screen.

3. Ruby provisions the four Ruby Insights properties immediately and builds the owner identity map. Import your first deal from the HubSpot browser inside Ruby.

No HubSpot admin work is required first. Setup takes about two minutes.

What can Ruby AI do with HubSpot?

Build accounts and deals from HubSpot instead of typing them. Browse your portal from inside Ruby, filter by industry, deal stage, open deals or any custom company property, and create the matching Ruby account and deal in one step. Company name, domain, industry, headcount, deal name, amount, close date and pipeline stage all come across.

Import the history, not just the record. Ruby pulls notes, logged calls with recordings and transcriptions, emails, meetings, and WhatsApp, SMS and LinkedIn messages logged as HubSpot communications. That history becomes context the analysis agents read, so the first meeting Ruby analyzes is not the first thing Ruby knows about the deal.

Stakeholders arrive already mapped. Contacts associated with the deal become Ruby stakeholders, seeded with name, title, email and phone. New accounts pull the 10 most recently updated contacts on the company.

Ruby stays current without polling. When a deal changes in HubSpot, Ruby marks it as having updates pending within seconds. Ruby also blocks its own edits to amount, close date and stage on that deal until you import, so a Ruby update can never overwrite something a rep just changed in HubSpot.

Analysis reruns when the deal actually moves. Ruby scores each imported change instead of rerunning on every edit. A 25% amount drop or a close date that slipped 30 days is enough on its own. A stage change counts too, and clears the bar by itself once the deal is past hypothesis. Three substantial new conversations logged on the deal, or seven activities of any kind, trigger a refresh. Renaming a deal counts for nothing.

Frequently asked questions

What permissions does Ruby AI need in HubSpot?

Read access to companies, deals, contacts and owners, write access to companies, deals and contacts, read and write on deal schemas, and read on call transcripts. Ruby does not request access to your marketing tools, your email inbox, your forms or your workflows.

Who can connect HubSpot, an admin or every rep?

An organization admin connects it once and every member of the Ruby org inherits the connection. Non-admins are blocked at the authorization step. Each rep still sees only the records they own in HubSpot.

Can Ruby AI see deals I do not own?

No. Every read is filtered by your HubSpot owner ID. Companies are widened slightly, so a company you do not own is visible if it carries at least one deal you do own, which handles portals that leave companies unassigned.

Will Ruby AI overwrite what my reps put in HubSpot?

No. Ruby writes to four custom properties it creates itself, to notes it authored, and to amount, close date and stage only when a rep changes those fields inside Ruby. When HubSpot has un-imported changes, Ruby blocks its own edits to those three fields until you import.

Does Ruby AI re-import its own notes?

No. Ruby tracks every note it created and excludes them from import, so an analysis note cannot be read back in as customer context.

Need help connecting HubSpot?

Open Learn Hub in the Ruby AI app for a step-by-step walkthrough, or use the support widget in the bottom-right corner of the app. You can also email the team at support@heyruby.io.

Related integrations

• Salesforce if your team runs on Salesforce instead

• Google Calendar, which triggers the pre-meeting brief notes Ruby writes to HubSpot

• Gong, the highest-fidelity source for the calls behind those deals