Connect HubSpot to Claude Code
Give Claude Code governed access to HubSpot’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add HubSpot to Claude Code in four steps
Admins approve the server once. Everyone in Claude Code then gets it through the same governed connection.
- 1
Approve HubSpot in Runlayer
Add HubSpot from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Claude Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, HubSpot’s 30 tools show up in Claude Code’s own tool list (supported Claude Code versions).
Claude Code setup guide - 3
Sign in to HubSpot
Sign in the way HubSpot requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use HubSpot from Claude Code
HubSpot’s approved tools appear in Claude Code. Every call is checked against policy and recorded.
Tools
30 HubSpot tools in Claude Code
Runlayer policy decides which of these Claude Code users can call. 16 read data only and 5 can change or delete data.
Discover HubSpot schema
Searches HubSpot schema to discover available data types or look up known types directly.
Get AEO metrics
Portal-level AEO analytics: brand visibility, mentions, citations, competitor share-of-voice, and per-assistant breakdowns for a date window.
Get campaign attribution reports
REQUIRED FIRST STEP: before your first call, invoke tool_guidance for "get_campaign_attribution_reports" and follow it.
Get content analytics report
Run a content analytics report across landing pages, website pages, and blog posts in the portal.
Get conversation channel metadata
List inboxes, channels, and channel instances in this portal.
Get CRM objects
Fetches multiple CRM objects of the same object type in a single request.
Get marketing email analytics
Provides analytics data for marketing emails based on sends in the given date range.
Get organization details
Get organization-wide teams, job titles (roles), seats, and account info (timezone, currency, account type, portal name).
Control
What Runlayer can see and stop in Claude Code
Some controls apply to every client at the gateway. Others depend on what Claude Code exposes to Runlayer.
Gateway policy (available)
Every HubSpot call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Code as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
OTLP telemetry (available)
Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.
Stop a call before it runs (available)
Runlayer can deny a tool call before Claude Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Claude Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.
In Claude Code
- When a tool fails, Runlayer records the error but cannot hide it.
Frequently asked questions
Connect more
