Skip to main content
Integrations · HubSpot
A Guild agent reads, creates, updates, and deletes HubSpot CRM records on your team’s behalf. Guild stores the HubSpot private app token server-side and injects it into every request, so agent code never sees the credential. Credential policies let you restrict which operations each agent can call, and every request passes through Guild’s credential proxy before it reaches HubSpot.

Book a demo

See how teams govern agents that use HubSpot.

Talk to sales

Get access to Guild, then connect HubSpot to your first agent.

What the HubSpot integration exposes

The tools cover contacts, companies, deals, tickets, leads, products, quotes, calls, emails, meetings, notes, and tasks. Agents can also manage pipelines and their stages, read pipeline and stage audit logs, work with lists and list folders, and read or write properties, property groups, owners, and associations between objects. Tools are prefixed with hubspot_openapi_ and can be narrowed with pick() as described in the SDK tools docs.

How it works

1

Create a HubSpot private app token

In HubSpot, create a private app and copy its access token. The integration authenticates with this token sent as a bearer token in the Authorization header.
2

Connect the credential in Guild

Go to Access and setup > Credentials, click Connect, select hubspot-openapi, and paste the token into the API Key field. See Credentials for workspace, member, and agent-scoped options.
3

Import tools into your agent

Import HubspotOpenapiTools from the integration package and spread it into your agent’s tools object. Use pick() to include only the tools your agent needs.

Why HubSpot access needs governing

HubSpot CRM holds contact records, deal values, pipeline structures, and product data that many teams depend on. A single agent with unrestricted access can delete contacts, move deals through stages, or drop entire lists. Guild’s credential policies let you write ALLOW and DENY rules that the credential proxy enforces before any request leaves Guild. You can limit an agent to read-only GET operations, restrict it to specific object types, or block destructive operations by pattern while allowing everything else. Guild stores the private app token server-side and injects it into requests after the policy check passes. Agent code never receives the token. You can scope a credential to one workspace, one member, or one agent using the Credentials page, so a shared HubSpot connection does not give every agent the same reach. The tools also expose pipeline and stage audit logs, which agents can retrieve to surface a change history without leaving Guild.

About the HubSpot integration

Agents can read, create, update, and delete CRM records such as contacts, companies, deals, tickets, leads, products, and quotes. They can manage pipelines and their stages, organize lists and folders, and work with properties, owners, and associations between objects. Authentication uses a HubSpot private app token. The integration is guildai~hubspot-openapi.

Authentication

  • Type: API key
  • Header: Guild sends the key as a bearer token in the Authorization header

Setup

1

Connect HubSpot

In Guild, go to Access & setup > Credentials, click Connect, select hubspot-openapi, and paste the key into API Key.
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Selecting specific tools

Tools are named with the hubspot_openapi_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~hubspot-openapi:

Frequently asked questions

Yes. Write a DENY rule matching delete operations such as hubspot_openapi_delete_* and an ALLOW rule for the operations you want. Guild’s credential proxy enforces the policy before any request reaches HubSpot. See Credential policies for rule syntax.
No. The catalog entry for guildai~hubspot-openapi lists no webhook events, so the integration does not receive inbound events from HubSpot.
Yes. Connect a dedicated credential on each agent’s detail page, or scope separate credentials to individual agents. Guild picks the most specific credential in scope when an agent calls a tool, as described in Credentials.
Use the pick() helper from the Guild Agent SDK to select tools by name from HubspotOpenapiTools before spreading them into your agent. The SDK tools page shows the syntax.

Put a governed agent on HubSpot this week

Book a demo

See how teams govern agents that use HubSpot.

Talk to sales

Get access to Guild, then connect HubSpot to your first agent.
Also runs on Guild: Affinity · Attio · Brex · Gong Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 20, 2026