HubSpot is a CRM platform, and Vobiz connects to it as a calling widget: agents dial from a contact record, talk in the browser, and HubSpot writes the call onto the contact itself. Because HubSpot creates that record from the agent's own session, the integration asks for no CRM permissions at all.
SIP endpoint per agent, so calls reach the right desk
Before you start
Two things shape this one. It installs as a private app rather than from the HubSpot Marketplace, and it runs against a small backend you host, which holds the Vobiz credentials and answers the call webhooks. Each agent registers with their own SIP endpoint, so an inbound call rings the person it is meant for rather than whoever's browser reaches it first.
Why this pairing
Why run HubSpot calling on Vobiz
Call logging is the part of CRM hygiene that never survives contact with a busy week. A rep dials from a mobile, means to log it, and logs some of them — so the deal record that a forecast depends on is missing its most recent conversation. Any calling integration fixes that by starting the dial inside the CRM.
What is less usual here is what it costs you in access. HubSpot builds the call record itself, from the agent's own session, which means the app requests no CRM permissions and nothing of yours writes to HubSpot. Vobiz supplies the numbers and carries the calls, and your CRM data stays untouched by a third party.
HubSpot owns
Contacts, deals and the record the call lands on
Creating the call engagement itself
Agent accounts, sessions and permissions
Reporting and forecasting on call activity
The workspace the widget sits inside
Vobiz owns
Phone numbers and instant provisioning
Placing and receiving the call itself
The agent's browser audio over WebRTC
Call recording and its signed, expiring delivery
Call detail records and quality telemetry
Local regulatory compliance, including India KYC
What you get
What Vobiz adds to HubSpot
A softphone on the contact record, with no access to anything on it.
01
Zero CRM permissions
Most calling integrations ask to write to your CRM, and a HubSpot admin has to weigh that against the benefit. This one does not: HubSpot creates the call record from the widget's own messages, using the agent's session, so the app requests no scopes and the backend never writes to HubSpot. There is nothing to review because there is nothing being granted.
02
The call logs itself against the contact
Dial from a contact record and HubSpot attaches the call to it when the call ends. Nobody remembers to log anything, and the deal history reflects what actually happened.
03
Inbound raises a screen pop
A call to your attached number raises an overlay over HubSpot with answer and decline, driven from the keyboard, so an inbound call reaches the person rather than a voicemail box.
04
Recordings behind links that expire and carry nothing
Completed calls are listed in the widget with an inline player. Playback runs on signed links with a short expiry that carry no credentials of any kind, which is a deliberate design decision rather than a default.
05
Numbers in 130+ countries, in your own account
Local, mobile and toll-free inventory across 130+ countries, including regulated formats where a market demands them — India's 140-series and 1600-series among them. Pick any number on the account as the caller ID.
06
Provision the whole setup from the widget
Rather than wiring the application by hand, the widget can create a dedicated Vobiz application and SIP endpoint for HubSpot and attach a number to it, with the webhook URLs already filled in.
How it works
How to connect HubSpot to Vobiz
A developer sets this up once. The agent signs in and dials.
01
Prove the Vobiz account first
Place a call from the Vobiz browser demo before touching anything else. If that does not work, nothing downstream will, and you will spend a day debugging the wrong layer.
02
Create a SIP endpoint
Create an endpoint for the agent. Use a separate one per integration: an endpoint binds to exactly one application at a time, so sharing it between HubSpot and another CRM quietly breaks whichever was set up first.
03
Run the backend on a public HTTPS address
The backend holds the credentials, serves the widget and answers the call webhooks. Vobiz has to reach it, so it needs a stable public hostname. Check the answer URL responds correctly before opening any interface.
04
Point Vobiz at the backend
One call creates the application, binds the endpoint and attaches your number to it.
05
Sign in and call
Open the widget in HubSpot, sign in with your Vobiz API credentials — the Auth Token rather than your console password — pick a caller ID, and dial. Clicking a phone number anywhere in HubSpot dials it too.
The full setup, the backend routes, the call XML and a troubleshooting table covering every symptom are in the Vobiz docs.
No — it requests no CRM permissions at all. HubSpot creates the call record itself from the widget's messages, using the signed-in agent's own session, so nothing of ours ever writes to your CRM. For an admin weighing up third-party access, this is the unusual part: there is no scope to approve.
Yes. Dial from a contact record and HubSpot attaches the call to that contact when it ends, including inbound calls answered in the widget. No manual logging and no sync job.
Yes. Each agent gets their own SIP endpoint, so they register separately and an inbound call reaches the right person rather than whichever browser answers first. One installation serves the team.
Yes, a small one. It holds the Vobiz credentials, serves the widget and answers the call webhooks, and it needs a stable public HTTPS address because Vobiz calls into it during every call. The complete application and backend are in the repository.
Not currently. It installs as a private app on your own HubSpot account, which also means there is no review queue between setting it up and using it.
You can provision numbers in 130+ countries — local, mobile and toll-free, including regulated formats where a market requires them, such as India's 140-series and 1600-series. The numbers stay in your own Vobiz account rather than inside the CRM.
HubSpot is a customer platform covering CRM, marketing, sales and service. Learn more at hubspot.com. Vobiz is not affiliated with HubSpot; this integration is a private app built on HubSpot's public calling extensions framework. Platform behaviour and screens reflect HubSpot as of 21 October 2026.
We use cookies to run this site and, with your permission, to understand how it's used. Read our Cookie Policy.