What is HubSpot?
HubSpot is a crm & sales tool. With OSP.net, your AI agent connects to it directly so it can act on your behalf instead of just answering questions about it.
What your OSP agent can do with HubSpot
- Search and read contacts, companies and deals
- Create and update records, notes and tasks
- Summarize pipelines and recent activity
How to connect HubSpot
- In HubSpot, go to Settings → Integrations → Private Apps and click Create a private app. app.hubspot.com → Settings → Private Apps
- On the Scopes tab, grant the CRM scopes you want the agent to use — read scopes are plenty for questions; add write scopes only if it should create/update records:
- Create the app, then copy the Access token (pat-…), paste it here and Connect. Your agent talks to HubSpot's official MCP server with it. HubSpot Docs: MCP server
Security: A private-app token is scoped to exactly the permissions you grant — keep it read-only for a question-answering agent. Rotate or delete it any time from the same Private Apps page. (Prefer one-click? HubSpot is also reachable via the OAuth connect card above.)
Who uses HubSpot with OSP
These roles commonly connect HubSpot to their OSP agent:
Related crm & sales integrations
Frequently asked questions
- Can OSP.net connect to HubSpot?
- Yes. HubSpot is a native OSP.net integration — you bring your own HubSpot key or token, paste it in your dashboard, and your agent restarts live.
- What can my OSP agent do with HubSpot?
- Your agent works your HubSpot CRM — contacts, companies, deals, tickets — via HubSpot's official MCP server. Specifically: Search and read contacts, companies and deals; Create and update records, notes and tasks; Summarize pipelines and recent activity.
- Is HubSpot a native integration or via the gateway?
- HubSpot is a native, baked-in integration. You connect it with your own credentials, which are stored in an encrypted vault and injected only at runtime.
- Is my HubSpot data secure with OSP.net?
- Yes. Your HubSpot credentials live in an encrypted secrets vault, are injected only at container runtime, and are never written to disk in plaintext or used to train any model. Each customer runs in a fully isolated instance.