---
title: "HubSpot"
description: "Let a playbook read and change HubSpot contacts, companies, deals, tickets, activities and campaigns, and read invoices, owners and conversations, as you."
url: "https://on.auto/integrations/hubspot"
last_updated: "2026-11-10T08:17:42Z"
---

# HubSpot

Read and change contacts, companies, deals, tickets, activities and campaigns, and read invoices, owners and conversations.

A HubSpot connection gives a playbook's functions HubSpot's MCP server. You sign in to HubSpot, choose an account and allow access, and the connection acts as you, with the HubSpot permissions you hold in that account. HubSpot grants the tools you allow at sign-in rather than named scopes, so its consent screen is the list of what the connection may do.

Available on Auto Cloud and on self-hosted runtimes.

* * *

## What a playbook can do with HubSpot

*   Read and change contacts, companies, deals, tickets, line items and products.
*   Read and change activities, campaigns, segments and landing pages.
*   Read invoices, owners and conversations.

HubSpot's server gives Auto no blog or website tools, which HubSpot offers to a few AI clients alone. A function cannot publish a page or a post through this connection.

HubSpot's MCP server lists its own tools when a function runs, and once you connect, your agent lists them with `list_connection_tools`.

* * *

## An example workflow

Qualifying inbound leads the way your team does. A schedule trigger runs the workflow every hour. A lookup function lists the contacts created since the last run with the server's contact tools, with their company. A reasoning function scores each one against the criteria in its prompt, the segments you sell to, the signals that matter, the ones that rule a lead out, and writes a one-line reason. A computation function keeps the leads above the threshold. An interaction function updates each kept contact's lifecycle stage and owner through the server's tools, and creates a follow-up activity for the owner. A lead the reasoning function could not place is left for a person: the workflow asks the sales lead through a Slack connection and waits for the answer. Every score and its reason are in the run's history in Studio, so the team can see why a lead was routed as it was and tighten the criteria.

* * *

## How to connect HubSpot

*   **Sign in to HubSpot, choose an account and allow access.** HubSpot shows on its consent screen what the connection may do.

Then:

1.  Ask your agent to connect HubSpot to Auto, or open **Settings**, **Agents**, **Connections** in [Auto Studio](https://studio.on.auto/) and choose HubSpot.
2.  On the Studio page, check the service and its access, choose which playbooks may use the connection, and approve it.
3.  Have your agent check one small read through the connection before a function depends on it.

* * *

## What it needs

*   A HubSpot user in the account, whose permissions the connection has. What you cannot do in HubSpot, the playbook cannot do either.
*   Your agent connected to Auto and signed in as you, with permission to change your organization, if your agent adds the connection.
*   On a self-hosted runtime, an MCP connector you make in HubSpot and register as the runtime's client, as [Let people add connections](https://on.auto/docs/self-host/connections) sets out; HubSpot's server takes no other kind of client.

### Permissions Auto asks for

No scopes are named: HubSpot grants what you allow on its consent screen.

* * *

## Good to know

A tool that changes a record is marked as one that acts, so a lookup function cannot call it, and a reasoning function calls it only where its definition names the tool. What a function reads, a contact's properties or a conversation, is kept in the run's history, where people with access to the playbook can read it.

* * *

[All integrations](https://on.auto/integrations/) · [Stripe](https://on.auto/integrations/stripe) · [LinkedIn](https://on.auto/integrations/linkedin) · [Slack](https://on.auto/integrations/slack) · [Bring in business data](https://on.auto/docs/cloud/connections) · [Give a function tools](https://on.auto/docs/guides/tools) · [Pricing](https://on.auto/pricing) · [HubSpot documentation](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server)

## Sitemap

See the [full documentation and product sitemap](https://on.auto/sitemap.md) for related pages.