Which deals have not moved in three weeks, and whose are they?
Open deals filtered on when they last changed, with the stage each is sitting in and the owner it belongs to.
-
search_deals -
retrieve_owners
Setup guide
How to connect HubSpot to Claude
Put HubSpot behind Claude and it works in the real pipeline, with your portal's own properties and stages rather than a guess at them.
245 Tools available
100 Read only
145 Can change data
~5 min Setup time
Before you start
Claude already has a HubSpot connector
HubSpot's own connector is in the directory, verified, and it brings CRM context into an answer. This page's route is a different shape: the whole HubSpot tool list behind one endpoint, with you choosing which of it Claude can touch.
HubSpot Verified
Versus
Connect FloConnector in five minutes
Connecting FloConnector connects HubSpot, and HubSpot is one of 60 connectors the same endpoint can carry. You do this setup once, not once per app.
- HubSpot tools, not one workflow The listing above does the job its vendor shipped it to do. A profile reaches all of them, and you switch on the handful you actually use.
- One endpoint, not one app HubSpot is one of 60 connectors a single profile can carry, so Claude answers across your stack rather than one app at a time.
- You decide what it can change Reading and writing are separate switches. Leave the writes off and the connection cannot alter a record, however the question is put to it.
Step one
Connect HubSpot
- Sign in to FloConnector and open Connectors, then choose HubSpot.
- Choose Connect. HubSpot's own page opens and asks which account to connect and which permissions to grant, then returns you to the dashboard.
- Open a profile, or create one, and switch on the HubSpot tools you want available. Keep the search tools on alongside anything that creates records, because that pairing is what stops duplicates.
- Copy the profile's endpoint URL. That is the only thing you paste into Claude, and it is per profile, so sales and support can have different ones.
Step two
Add the endpoint in Claude
- In Claude, open Settings, then Connectors.
- Choose Add custom connector.
- Give it a name you will recognise, such as your workspace name, and paste your profile endpoint as the URL.
- Save, then choose Connect. Claude opens the FloConnector sign-in page.
- Sign in with the email on your FloConnector account and approve access. Claude loads the profile's tools.
Control
Build the profile, then hand over the URL
A profile carries only the tools you switch on, and the endpoint exposes only that profile. That is the whole permission model, and it is set before anyone connects.
HubSpot Connected 13/245 8 read 5 write
Tick a row to include it, or flip Read only to lock every write off at once.
FloConnector holds the HubSpot credential, encrypted before it is stored, and calls HubSpot on the model's behalf. Claude sees the tools and their results, never the credential behind them.
Once it is connected
What to ask Claude
Each of these runs real HubSpot tools, named underneath so you can see what Claude is actually calling. 13 of the 245 tools are covered here.
Write up the call I just had with Priya at Meridian and set a follow-up for Friday.
A note on that contact's timeline and a task dated Friday against the same record, both landing on the existing contact rather than a new one.
-
search_contacts_by_criteria -
create_note -
create_task
Add the demo signups as contacts and link each one to their company.
Contacts written against your portal's actual property names, then associated with the matching company record instead of left floating on their own.
-
list_contact_properties -
create_contacts -
search_companies -
create_association
What is in the pipeline for this quarter, by stage and by owner?
Deal value totalled by stage and by owner, against the stage names your pipeline actually uses rather than the ones HubSpot ships with.
-
search_deals -
get_pipeline_by_id -
retrieve_owners
Which support tickets have been open longest, and what did the customer last say?
Open tickets sorted by age, with the contact on each and the most recent note from their record.
-
search_tickets -
list_contact_notes
Move the Meridian deal to contract sent and push the close date out a fortnight.
That one deal found and changed, with the new stage and date read back. Nothing else in the pipeline moves with it.
-
search_deals -
update_deal
Troubleshooting
When Claude does not behave
-
Claude Desktop sits on Connect after you signed in
The sign-in has usually succeeded. Check the profile in your dashboard: if the grant is there the connection is live, and restarting the desktop app clears the stale button. It is a client-side issue, not something the server can fix.
-
The connector saves but no tools appear
Disconnect and reconnect it once. If it is still empty, check in the dashboard that the connection behind the profile is still connected and that you are an assigned member of that profile.
-
The first load is slow on a very large profile
A profile exposing hundreds of tools takes longer to load, and a model given too many tools chooses worse. Split the work across two profiles rather than exposing everything at once. This is the failure mode most MCP write-ups name and never solve.
Questions, answered
Does Claude see my HubSpot login?
No. You sign in on HubSpot's own page and choose the permissions there. The token that comes back is encrypted before FloConnector stores it, and Claude only ever sees the tools and what they return.
Will it create duplicate contacts?
Not if the search tools are on the profile beside the create tools. Claude looks for the record first and updates it when it finds one; a profile that can create but cannot search is the one that makes duplicates, so switch them on as a pair.
Does it use our custom properties or HubSpot's defaults?
Yours, provided the property list is on the profile. That is its own read tool, and with it available Claude writes to the fields your portal really has. Without it, expect to be asked for field names every time.
Can Claude send marketing emails from our account?
The marketing email tools are separate switches from the CRM ones, and publishing is separate again from drafting. Leave publishing off and Claude can build an email for somebody to look at, but cannot put it in front of a list.
Can a rep get their own access without seeing everything?
Yes. People are assigned to profiles one at a time, so a rep can have an endpoint carrying deal search and note writing, while reporting and anything destructive lives on a profile they are not on.
Does the same setup cover ChatGPT?
Yes, and it is the same URL. A profile endpoint is a standard hosted MCP server, so adding it in another client is a paste rather than a second connection.
One HubSpot account per connection
A connection authorises one portal, and a workspace holds one connection. An agency running HubSpot for several clients needs a workspace each, which is also how you keep one client's pipeline from ever appearing in another's endpoint.
Records are joined by associations, not by a field
A contact, a company, a deal and a ticket are separate objects wired together by association records. Creating a contact does not put it on a company; that is a second call. Ask for the link explicitly, or you end up with tidy records that know nothing about each other.
There is a delete that does not come back
HubSpot's GDPR delete removes a contact permanently and blocks the address from ever being added again. Those tools are flagged in the picker, and they should stay off on every profile except one somebody built on purpose for exactly that job.
Your turn
Put HubSpot in front of Claude.
One connection, one endpoint, and 245 HubSpot tools your AI can actually run. Start free with 1,000 tool calls and see what your own first week looks like.
