HubSpot

HubSpot

This connector works with one HubSpot account through the CRM API (https://api.hubapi.com, date-versioned API 2026-09): search, read, create and update contacts, companies, deals, tickets and other CRM objects, list and create associations, read owners, pipelines and properties, and add notes and tasks. It authenticates with a service key (or a legacy private app token) that you create in your own account.

Setup (super admin or a user with Developer tools access, about 5 minutes)

1. In HubSpot open Development in the left sidebar, then Keys → Service keys, and click Create service key.
2. Name it (for example "AnythingMCP"), click Add new scope and tick the scopes below, then Update and Create.
3. Open the key, click Show, then Copy, and paste it into HUBSPOT_ACCESS_TOKEN. Keys start with pat- (for example pat-eu1-...).
4. Older accounts may still use a legacy private app (Development → Legacy apps, previously Settings → Integrations → Private Apps): its access token works the same way.

Scopes

• Read: crm.objects.contacts.read (also covers notes and tasks), crm.objects.companies.read, crm.objects.deals.read, crm.objects.tickets.read, crm.objects.owners.read.
• Write: crm.objects.contacts.write (also needed for notes and tasks), crm.objects.companies.write, crm.objects.deals.write, crm.objects.tickets.write.
• Read-only setup: give the key only the read scopes and switch off hubspot_create_object, hubspot_update_object, hubspot_associate_records, hubspot_create_note and hubspot_create_task. hubspot_archive_object is installed switched off.

Ids and properties: every record has a numeric id (hs_object_id), passed as a string. Object types are plural: contacts, companies, deals, tickets, notes, tasks; custom objects use their id such as 2-1234567. Property values are strings keyed by internal name (firstname, dealstage, hubspot_owner_id); hubspot_list_properties gives names, types and dropdown options. Dates are YYYY-MM-DD or Unix milliseconds, timestamps ISO 8601. Deal stages and ticket statuses are stage ids from hubspot_list_pipelines, not labels. Owners come from hubspot_list_owners.

Search: hubspot_search_objects takes free text, filter groups (AND inside a group, OR between groups, at most 5 groups and 18 filters) and one sort. To find records linked to another, filter on associations.contact (or .company, .deal, .ticket) with EQ and the id. New or changed records can take a few seconds to show up.

Associations: hubspot_get_object with associations=deals returns linked ids; hubspot_get_associations lists them with labels. hubspot_associate_records links two records with the default type. On create, associations needs a type id: note to contact 202, company 190, deal 214, ticket 228; task to contact 204, company 192, deal 216, ticket 230; contact to company 1; deal to contact 3, deal to company 5; ticket to contact 16, ticket to company 26.

Pagination: lists and searches return paging.next.after; pass it as after with the same other arguments until it is missing. Lists allow 100 per page, search 200 per page and 10,000 results per query.

Rate limits: 100 requests per 10 seconds per key on Free and Starter (higher on Professional and Enterprise), 250,000 a day per account, and 5 search requests per second. Over a limit HubSpot answers 429; wait a few seconds.

Errors: 401 means the key is wrong, expired or was rotated: copy it again. 403 names the missing scope: add it to the key under Edit. 404 is a wrong id or object type. 400 VALIDATION_ERROR names the property or filter that is wrong, for example an unknown property name or a dropdown value that is not an option. "The following required properties were missing" lists properties the account made mandatory: accounts with data privacy (GDPR) settings on require hs_legal_basis on every new contact.

Out of scope here: marketing emails, forms, lists, workflows, files, quotes and line item pricing, merges and batch writes.