HubSpot MCP integration for AI agents.
Connect AI agents to HubSpot contacts, companies, deals, tickets, CRM search, and record updates through machine-readable actions.
- ACTION CONTRACTS
- 26
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the HubSpot integration exposes
The HubSpot Agent App makes CRM identity explicit. An agent can search for a contact, company, or deal, retrieve the current record, and then create or update a record through an authorized connection. Search-before-write is essential because email addresses, company domains, and names are not always unique.
CRM actions affect shared operational data. Agents should preserve source attribution, avoid overwriting fields they did not retrieve, and keep marketing consent, lifecycle stage, ownership, and financial fields behind stricter policy or human approval.
VERIFIED ACTION SAMPLE
Real HubSpot capabilities.
Showing 12 of 26 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_campaign_analyticsREADGet HubSpot campaign analytics for one or more campaigns.
INPUTS: campaignIds / metricType / startDate / endDate
create_companyWRITECreate a HubSpot company with the provided properties and optional associations.
INPUTS: properties / associations
manage_crm_objectsREVIEWCreate or update HubSpot CRM records or activities through the MCP server.
create_contactWRITECreate a HubSpot contact with the provided properties and optional associations.
INPUTS: properties / associations
create_dealWRITECreate a HubSpot deal with the provided properties and optional associations.
INPUTS: properties / associations
get_campaign_asset_metricsREADGet metrics and properties for CRM objects associated with a HubSpot campaign.
INPUTS: campaignId / assetType / objectIds
get_campaign_asset_typesREADList HubSpot asset type names available as campaign assets.
get_campaign_contacts_by_typeREADFetch paginated HubSpot contact IDs for a campaign filtered by attribution type.
INPUTS: campaignId / attributionType / limit / after
get_companyREADGet a HubSpot company by record ID or by a custom idProperty value.
INPUTS: recordId / idProperty / properties / propertiesWithHistory / associations
get_contactREADGet a HubSpot contact by record ID or by a custom idProperty value.
INPUTS: recordId / idProperty / properties / propertiesWithHistory / associations
get_crm_objectsREADFetch one or more HubSpot CRM objects by ID through the MCP server.
INPUTS: objectType / objectIds / idProperty / properties / propertiesWithHistory
get_dealREADGet a HubSpot deal by record ID or by a custom idProperty value.
INPUTS: recordId / idProperty / properties / propertiesWithHistory / associations
INPUT CONTRACTS
Know what the action needs before it runs.
get_campaign_analytics
campaignIdsREQUIRED- HubSpot campaign IDs.
metricTypeOPTIONAL- Campaign analytics metric type.
startDateOPTIONAL- Inclusive analytics start date.
endDateOPTIONAL- Inclusive analytics end date.
create_company
propertiesREQUIRED- HubSpot properties keyed by property name.
associationsOPTIONAL- Association definitions to create alongside the record.
create_contact
propertiesREQUIRED- HubSpot properties keyed by property name.
associationsOPTIONAL- Association definitions to create alongside the record.
create_deal
propertiesREQUIRED- HubSpot properties keyed by property name.
associationsOPTIONAL- Association definitions to create alongside the record.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Account follow-up
Find open opportunities without a recent contact, retrieve owner context, and prepare outreach drafts.
Support context
Resolve a customer identity and retrieve only the CRM fields needed to understand an active conversation.
Pipeline hygiene
Identify records missing required fields and produce a reviewable change set before updating them.
SAFETY BOUNDARY
Operate HubSpot with explicit limits
- Resolve the record by stable ID before writing.
- Do not infer marketing consent or lawful basis.
- Confirm pipeline stage, owner, amount, and close-date changes.
- Report every changed property in the execution result.
CONNECTION MODEL
OAuth 2.0
HubSpot uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 18
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by HubSpot.