C
Cody
OpenClaw Integrations

How to Connect HubSpot to OpenClaw: Setup, Models, and Workflow Guide

·5 min read

If you're searching for "how to connect HubSpot to OpenClaw", the real question is usually not just whether the connection is possible. It's how to make HubSpot usable inside an OpenClaw workflow with the right model, the right context, and the right level of control.

That's the practical framing.

OpenClaw gives you the orchestration layer: connectors, skills, tools, prompts, approvals, and the ability to run workflows where your team already works. HubSpot provides the domain context. The integration becomes valuable when those two pieces are connected cleanly.

What “Connect HubSpot to OpenClaw” Actually Means

In practice, connecting HubSpot to OpenClaw usually involves four layers:

  • Authentication so OpenClaw can securely access HubSpot
  • Tooling or proxy endpoints that expose the right HubSpot actions and data
  • Skills/instructions that tell OpenClaw how to reason over HubSpot context
  • Model selection so the assistant uses the right LLM for the job

That last piece matters more than most people expect.

Which Models Can You Use?

OpenClaw is model-flexible, so a HubSpot integration does not need to be tied to a single provider. Depending on your setup, teams commonly want to use:

  • OpenAI models like GPT-4o, GPT-4.1, and o3 for broad reasoning and tool use
  • Anthropic models like Claude 3.5 Sonnet, Claude Sonnet 4/4.5, and Claude Opus for strong writing, analysis, and long-context work
  • Google models like Gemini 1.5 Pro or newer Gemini models for multimodal and large-context workflows
  • Other model backends if your OpenClaw environment exposes them

The practical point: you can connect HubSpot to OpenClaw once, then run different workflows with different models depending on the job.

For example:

  • Use Claude for nuanced summarisation or drafting
  • Use OpenAI for structured extraction, tool-heavy workflows, or general-purpose copiloting
  • Use Gemini when multimodal or very large context windows matter

A Good Integration Pattern for HubSpot

A strong HubSpot + OpenClaw setup usually looks like this:

  1. OpenClaw receives a request in chat or from an automation
  2. It calls the right HubSpot endpoint or proxy
  3. The selected model reasons over the returned context
  4. OpenClaw returns an answer, draft, classification, or action
  5. High-risk actions stay behind approvals or structured guardrails

That is what makes the setup operational rather than just experimental.

Step-by-Step: Connect HubSpot to OpenClaw

Step 1: Create a HubSpot Private App

Go to HubSpot → Settings → Integrations → Private Apps and create a new app. Select the scopes you need — crm.objects.contacts.read, crm.objects.deals.read, crm.schemas.contacts.read for basic CRM data. You'll get a Private App token (similar to an API key) to use in your proxy.

Step 2: Explore the CRM API

HubSpot's v3 CRM API has consistent endpoints for objects: /crm/v3/objects/{objectType} for contacts, deals, companies, etc. Use the search endpoint (/crm/v3/objects/{objectType}/search) with filters to find records by email, name, or other properties. The API explorer in HubSpot's developer docs is useful for prototyping queries.

Step 3: Build the Proxy and Skill File

Build your proxy around the search and retrieve endpoints for the objects your team cares about. Write ~/.openclaw/skills/hubspot.md with your pipeline stage names and common query patterns (e.g., how a rep would ask about a deal's status).

Model-Specific Workflow Ideas

HubSpot + OpenAI

Use this when you want a strong general-purpose setup for extraction, classification, action planning, and tool-driven workflows around HubSpot.

HubSpot + Claude

Use this when you want better writing quality, clearer summaries, stronger nuance, and reliable long-context reasoning over HubSpot data.

HubSpot + Gemini

Use this when the workflow benefits from large context windows, multimodal inputs, or Google-native ecosystem alignment.

Common Mistakes

Most teams do not fail because the model is bad. They fail because:

  • the HubSpot connection is too thin
  • the model lacks the right live context
  • prompts are vague
  • no structured outputs are enforced
  • permissions and approvals are skipped
  • one model is forced to do every job, even when another would be a better fit

The best setup is usually one integration layer, multiple model options, and clear guardrails.

Challenges and Caveats

Associations Between Objects Are Separate Calls

To get a deal's associated contacts, or a contact's associated company, you need additional API calls to the associations endpoints. A single 'tell me about this deal' query might require 3–4 API calls. Build your proxy to handle these efficiently.

Rate Limits Vary by Plan

HubSpot's API rate limits depend on your subscription. Free/Starter plans get 100 API calls per 10 seconds. Professional and Enterprise get more. If your team is using OpenClaw heavily, you may need to cache responses to avoid hitting limits.

Custom Properties Need Explicit Handling

If your team has created custom properties on CRM objects, they won't appear in default API responses. You need to specify them in your requests. Document your most important custom properties in the skill file.

Want HubSpot Connected to OpenClaw Without Building the Whole Stack Yourself?

Cody has HubSpot integration built in. Query deals, contacts, and pipeline health from Slack without any API configuration.

Get started with Cody →

Related OpenClaw Guides

Looking for a more workflow-first angle? See: HubSpot AI Automation and HubSpot AI Assistant.

← Back to all guides