HubSpot
Org-level connection
HubSpot is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
How to connect
Click "Connect with OAuth" below to authorize On Belay to access your HubSpot account. You'll be redirected to HubSpot to approve the connection — no credentials to copy or paste.
Ready to connect?
Go directly to the integrations page in your dashboard.
Permissions (scopes)
These are the data scopes On Belay can be granted for HubSpot. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
crm.objects.contacts.read | Read contacts | Read only |
crm.objects.contacts.write | Write contacts | Read / Write |
crm.objects.companies.read | Read companies | Read only |
crm.objects.companies.write | Write companies | Read / Write |
crm.objects.deals.read | Read deals | Read only |
crm.objects.deals.write | Write deals | Read / Write |
tickets | Tickets | Read / Write |
content | CMS content | Read / Write |
cms.knowledge_base.articles.read | Read knowledge base | Read only |
cms.knowledge_base.articles.write | Write knowledge base | Read / Write |
cms.knowledge_base.articles.publish | Publish knowledge base | Read / Write |
forms | Forms | Read only |
sales-email-read | Read CRM email content | Read only |
marketing-email | Marketing email | Read only |
automation | Automation | Read / Write |
oauth | OAuth (required) | Read only |
Troubleshooting
"redirect_uri_mismatch" error during OAuth
Your OAuth app's authorized redirect URIs don't include the On Belay callback URL. Add https://app.onbelay.ai/api/oauth-callback/hubspot to the allowed redirect URIs in your OAuth app settings.
"invalid_scope" error
The API or scope isn't enabled in your cloud project. For Google integrations, make sure the relevant API (e.g., Google Ads API, Search Console API) is enabled in Google Cloud Console for your project.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
Still stuck? We're happy to help.
Contact support →