How to Integrate OpenClaw with HubSpot for CRM Automation

OpenClaw is an open-source AI agent framework that runs on your local hardware and connects to external services through skills and MCP servers. The HubSpot integration gives your agent direct access to CRM data: contacts, companies, deals, tickets, and custom objects. Your agent can read records, create new ones, update fields, and trigger actions across HubSpot's sales, marketing, and service hubs.

The integration matters because HubSpot's native AI features only work inside HubSpot itself. OpenClaw sits outside the platform and orchestrates across tools. Your agent can pull a contact from HubSpot, research the company using web search, draft a follow-up email, log the activity back to HubSpot, and store the output in a shared workspace. That cross-platform orchestration is what separates an agent framework from a built-in chatbot.

Two connection methods exist. The first uses Composio's managed MCP server, which handles OAuth tokens, scopes, and refresh cycles automatically. The second uses a HubSpot Private App token with granular permission scoping you control directly. Both support the same CRM operations. The choice comes down to whether you want managed authentication or full control over token lifecycle.

Composio provides a managed MCP server that brokers the connection between OpenClaw and HubSpot. This is the faster setup path because Composio handles OAuth, token refresh, and scope management on your behalf. You authenticate once through a browser-based flow, and Composio keeps the connection alive without you managing tokens manually.

Two setup paths are available. The dashboard method works entirely through Composio's web interface: you sign up, find the HubSpot toolkit, copy a setup prompt, and paste it into your OpenClaw chat. Composio walks you through the OAuth authorization in your browser, and your agent gets immediate access to HubSpot tools. No CLI interaction needed. The second path uses Composio's CLI plugin, which you install into OpenClaw and configure with your Composio account credentials. This gives you the same managed authentication but lets you automate the setup across multiple machines or team members.

Both paths register all available HubSpot tools in your OpenClaw environment automatically. Once connected, your agent calls CRM operations by name without separate search or execute steps. If the OAuth token expires, Composio handles the refresh cycle or prompts you to re-authenticate through the dashboard. Check Composio's OpenClaw integration page for current setup instructions, since the exact steps may change as both platforms evolve.

Give your CRM agent a workspace humans can actually use

Store pipeline reports, enrichment data, and meeting summaries where your team can search, review, and ask questions. generous storage, no credit card, MCP-ready endpoint for OpenClaw.

Start 14-Day Trial

If you want direct control over authentication without a third-party broker, create a HubSpot Private App and connect OpenClaw using the API token. This approach gives you explicit control over which HubSpot scopes your agent can access.

Create the Private App in HubSpot:

1. Go to Settings, then Integrations, then Private Apps in your HubSpot account
2. Name the app something clear like "OpenClaw Integration"
3. Enable these scopes based on what your agent needs:
   • crm.objects.contacts.read and crm.objects.contacts.write
   • crm.objects.companies.read
   • crm.objects.deals.read and crm.objects.deals.write
   • crm.objects.owners.read
4. Create the app and copy the access token

Store the token securely:

Keep the token in a .env file outside your workspace directory. Never embed tokens directly in skill files or commit them to version control.

HUBSPOT_ACCESS_TOKEN=pat-na1-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Configure OpenClaw to use the token:

Add the token to your OpenClaw environment so your agent can authenticate against HubSpot's API. The exact configuration depends on your OpenClaw setup, but the key requirement is that the token stays out of version control and skill files reference it as an environment variable rather than a hardcoded value. Include a rule in your agent's instructions requiring confirmation before any write operation. This prevents accidental bulk updates to your production CRM. Refer to the OpenClaw integrations guide for current configuration steps.

The Private App method works well for teams that need audit-friendly authentication. Every API call traces back to a specific Private App with documented scopes, which simplifies compliance reviews. Once your agent starts producing CRM output, you will want somewhere persistent to store it. A workspace like Fastio gives your agent a place to write reports that humans can review and search later.

Both connection methods expose the same core CRM operations. Here is what your OpenClaw agent can do once connected to HubSpot.

Read operations:

• Look up contacts by email, name, or custom properties
• Search companies by domain, industry, or revenue range
• Check deal pipeline status and stage history
• Pull owner assignments and team structures
• Query custom objects and their associations

Write operations:

• Create and update contacts, companies, and deals
• Log calls, meetings, and email activities
• Move deals between pipeline stages
• Create tasks and set follow-up reminders
• Update custom properties on any CRM object

Bulk and automation operations:

• Batch archive contacts, deals, quotes, and line items
• Merge duplicate CRM records
• Manage property schemas and custom object definitions
• Handle privacy requirements deletion requests programmatically
• Run pipeline health checks on a schedule

The Composio path exposes 200+ operations across these categories. The Private App path gives you the same underlying HubSpot API, but you write the specific operations into your skill file. Start with read-only operations in week one, add write capabilities in week two, and introduce scheduled automations in week three. This phased approach limits the blast radius of any misconfiguration.

Sales development reps spend roughly 28% of their work week on administrative tasks, primarily CRM data entry. That is over 11 hours per week not spent on actual selling. Here are four automation recipes that address the most common time drains.

Contact auto-enrichment: When a new contact enters HubSpot, your OpenClaw agent researches the company, locates the contact's LinkedIn profile, gathers recent company news, and appends firmographic details to the CRM record. This runs in the background without manual research.

Deal monitoring and alerts: Configure your agent to scan the pipeline daily. It flags deals that have been inactive for seven or more days, highlights high-value opportunities with no recent activity, and summarizes weekly pipeline movement. Route these alerts to Slack, Telegram, or email.

Meeting documentation: After a sales call, your agent processes the meeting transcript, summarizes key discussion points, updates the deal record in HubSpot, and generates follow-up tasks with suggested next actions. The rep reviews and approves rather than writing everything from scratch.

Lead scoring and routing: Your agent evaluates new contacts against your ideal customer profile, scores them based on firmographic and behavioral signals, and routes qualified leads to the appropriate sales rep with context about why the lead scored well.

Each of these workflows produces output your team needs to review: enrichment reports, pipeline summaries, meeting notes, and scoring rationale. Storing that output somewhere accessible matters, especially when agents run overnight or on weekends.

CRM automation generates artifacts: enrichment reports, pipeline summaries, call transcripts, lead scoring breakdowns. These files need to live somewhere your team can find them, not buried in chat logs or lost between agent sessions.

Local storage works if you are the only person reviewing output. But sales teams need shared access, and agents running on schedules need persistent storage that survives restarts. S3 or Google Drive can hold files, but they do not index content for search or let you ask questions about what your agent produced.

Fastio provides workspaces where agents write files and humans review them. Your OpenClaw agent stores CRM reports, enrichment data, and pipeline analyses in a shared workspace. The team opens the same workspace in a browser to review, comment, and approve. When Intelligence is enabled on the workspace, every file your agent uploads is automatically indexed for semantic search and RAG chat. You can ask "Which deals went stale last week?" and get an answer grounded in the actual reports your agent generated.

The Fastio MCP server gives your OpenClaw agent direct access to workspace operations: upload files, create folders, manage permissions, and trigger intelligence indexing. Ownership transfer lets the agent build out a workspace and then hand control to a human when the project is complete. The Business Trial includes 50 GB of storage, included credits, and five workspaces with no credit card required.

A practical setup: your OpenClaw agent writes a daily pipeline summary to a Fastio workspace folder called /hubspot-reports/daily/. The sales manager gets a automation hooks notification, opens the workspace, reads the summary, and asks Ripley AI follow-up questions about specific deals. The agent produced the data; the human makes the decisions.