If your calls from Orum are not appearing in HubSpot, the most common causes are permissions, an outdated connection, or calling a prospect that Orum could not match back to the HubSpot source you were dialing from.
Which calls typically write back to HubSpot and which may not
How to check HubSpot permissions
How to reconnect or reauthorize the integration
Where to find logged calls in HubSpot
Make sure you are checking the contact record in HubSpot
Give HubSpot a moment to process the activity, then refresh the page
If possible, note whether the call was made from a HubSpot list, a HubSpot call task, or a manual dial
In general, Orum needs a clear way to match the call back to the HubSpot prospect it was dialing.
Calls are most likely to write back when:
The prospect was already loaded into Orum from HubSpot
The call was made from a HubSpot list or segment that Orum was actively using
The call was made from a HubSpot call task assigned to the rep
If you are unsure whether a specific call should have logged, run a quick test using a contact that is already present in the HubSpot list or call task you are dialing from.
Missing HubSpot permissions can prevent Orum from working correctly.
Ask your HubSpot admin to review the required permissions in our guide:
Key checks include:
App Marketplace Access is enabled by a HubSpot Super Admin
The affected users have the required HubSpot CRM permissions
If your team dials sequence-based call tasks, the required Sales Hub and Sequence permissions are enabled
If permissions look correct but calls still are not logging, refresh the connection.
Try the following:
In Orum, switch to the HubSpot-connected workflow or dialer view
Sign in to HubSpot again if you are prompted
Approve any reauthorization or reconnect prompts that appear
Place a new test call to a contact that is already in the HubSpot source you are using
If your team recently changed HubSpot users, changed the connected HubSpot instance, or you do not see a way to reconnect, contact Orum Support for help resetting the connection.
When a call logs successfully, it should appear on the contact record in HubSpot.
Look in either of these places:
The Activity timeline on the contact
The Calls tab on the contact, if your HubSpot view includes it
For reporting, use HubSpot’s native reporting filters such as:
Activity Type = Call
Activities Assigned To = the rep who placed the call
Activity Date = your chosen date range
For general setup guidance, see:
If the issue is intermittent, test with one contact that should clearly be eligible to log.
A good test case is a contact that:
Already exists in HubSpot
Is already present in the list, segment, or call task you are dialing from
Has the phone number in place before the call starts
If that test logs successfully but other calls do not, the difference is often the source of the prospect or task rather than a system-wide HubSpot outage.
This usually happens when some calls were made from prospects that Orum could clearly match back to HubSpot, while others were made from prospects outside the HubSpot source Orum was using.
Start with the contact’s Activity timeline. If your HubSpot layout shows a Calls tab, you can check there as well.
In known cases, calls did not retroactively write back after the contact or number was added later. If you need confirmation for your specific setup, contact Orum Support.
