HubSpot ↔ RingCentral integration

Calls and texts from RingCentral land on the right HubSpot contact, missed calls become tasks, and reps dial from the HubSpot record through their own RingCentral line

Sales talks to clients through RingCentral and keeps the pipeline in HubSpot. Between them — calls that nobody writes down, a missed call from yesterday's lead that nobody returns, and a manager who cannot say who actually talked to the client last week. The HubSpot ↔ RingCentral pair writes every call and text to the contact found by the phone number, turns missed calls into tasks for the contact owner, creates a contact for a first-time caller, and lets the rep dial straight from the HubSpot record through their own RingCentral line. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: HubSpot →System page: RingCentral →

What moves between the systems

RingCentral → HubSpotEvery finished RingCentral call is written to HubSpot as a call on the contact found by the phone number: direction, duration, the rep and a link to the recording if it exists.
RingCentral → HubSpotA missed inbound call from a known number becomes a HubSpot task for the contact owner with a due date, so it is called back rather than forgotten.
RingCentral → HubSpotA call from an unknown number creates a new HubSpot contact with the number, the time and the rep who answered, so a first-time caller is not lost.
RingCentral → HubSpotText messages sent and received through RingCentral are attached to the same contact, so the conversation is visible next to the calls and e-mails.
RingCentral → HubSpotA logged call can start a HubSpot workflow: for example, the first answered call moves a new contact to the next lifecycle stage, or a missed call from an open deal alerts the deal owner.
HubSpot → RingCentralThe rep starts a call from a contact, a list or the conversations inbox in HubSpot, and the call goes out through their own RingCentral line; it is logged back the moment it ends.
HubSpot → RingCentralNames, companies and open deals from HubSpot are used to recognise the caller, so the rep sees who is calling and which deal it is about before picking up.

What we connect

We agree on the rules: which record a call goes to when one number belongs to several contacts, who owns a contact created from an unknown number, and which calls are not logged (internal, shorter than a few seconds).
In HubSpot the administrator creates a private app for this account with access to contacts, calls, tasks and deals; that access can be revoked at any time.
In RingCentral the administrator adds the exchange as an application with rights to read call logs, recordings and messages and to place calls on behalf of the users who opted in.
We map RingCentral extensions to HubSpot users, so each call lands on the right rep and the manager's reports show who talked to whom.
We set the rhythm within RingCentral's per-minute request ceilings: the exchange signs in once and holds the session, reads call logs in batches every few minutes, and waits exactly as long as RingCentral asks when a ceiling is reached.
We test on a HubSpot test account with two reps and a day of real calls, check the logged calls and tasks with the sales lead, and only then connect the working account.

Automation scenarios

Calls that nobody writes down

Before a rep talks to a client for twenty minutes and forgets to log it, and the next colleague calls the same person with the same questions.

After the call is on the HubSpot contact with its duration and recording link as soon as it ends.

A missed call nobody returns

Before yesterday's lead calls back while the rep is busy, the missed call sits in the phone's history, and the lead buys elsewhere.

After the missed call is a task for the contact owner with a due date, visible in their HubSpot task list.

A first-time caller is lost

Before a new client calls from an advert, the rep promises to send details, and the number is never entered anywhere.

After the unknown number becomes a HubSpot contact with the call attached, and the agreed owner picks it up.

The manager cannot see who called whom

Before call statistics live in RingCentral and deals in HubSpot, and the weekly review is two screens and guesswork.

After every call sits on the contact and the deal with the rep's name, so HubSpot reports show calls per rep and per deal.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

HubSpot's CRM is built around objects — contacts, companies, deals, tickets and others — and every object type has its own numeric ID used in requests.
Source: developers.hubspot.com ↗ checked 2026-09-25
The built-in Workflows builder automates actions — sending an email, updating CRM data, launching another integration — based on an event, a schedule or a condition.
Source: knowledge.hubspot.com ↗ checked 2026-09-25
The built-in Calling tool works straight from a contact record, a contact list, or the conversations inbox, and can place a call through a HubSpot number, a registered outbound number, or a third-party provider.
Source: knowledge.hubspot.com ↗ checked 2026-09-25
Default ceilings per group, per user per minute: Light 50, Medium 40, Heavy 10, and Auth (signing in) just 5 — each with its own 60-second penalty window.
Source: developers.ringcentral.com ↗ checked 2026-09-25
Going over the ceiling returns a Too Many Requests error, and the exact number of seconds to wait before trying again is stated right in the response.
Source: developers.ringcentral.com ↗ checked 2026-09-25
The groups are counted independently of each other — running out of allowance on light requests doesn't touch the remaining allowance on medium ones.
Source: developers.ringcentral.com ↗ checked 2026-09-25

Limits

The limits come from both systems. RingCentral meters requests per user per minute by groups, and sign-in attempts are metered most strictly, so call logs are read in batches and a call appears in HubSpot within minutes, not at the same second. Calling from a HubSpot record needs a Sales Hub or Service Hub seat on a paid plan, and automatic call transcription in HubSpot is available only on Professional and Enterprise seats of those hubs. A call from a number stored in HubSpot in a different format is matched only after numbers are normalised, which we do at setup. Recordings stay in RingCentral; HubSpot receives a link, not the file.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Isn't there a ready-made RingCentral app for HubSpot?

HubSpot's own App Marketplace is the first place we check. If a ready app covers your rules, we set it up and stop there. We build only the parts it does not do for you: your own matching order, tasks from missed calls with your due dates, contacts from unknown numbers with your ownership rules, and workflows started by calls.

Can we log calls only for the sales team, not for support?

Yes. The exchange works per extension: only the extensions mapped to HubSpot users are read, other extensions of the company are not touched.

HubSpot has its own calling. Will calls be logged twice?

No. HubSpot's calling can go through a HubSpot number, a registered number of your own or an outside phone provider; for reps who work through RingCentral we agree which side logs the call, and each call is written to the contact once.