DataMCPComing soon

HubSpot

CRM, marketing, sales, and service in one platform.

CRM, marketing, sales, and service in one platform. This integration is on the roadmap — UI may appear as Coming Soon until your tenant is enabled. Use this guide to understand capabilities, setup, and how HubSpot fits into AKOBOT MCP workflows.

In this article

What this integration does in AKOBOT
Key capabilities and supported workflows
Setup and configuration steps
Operational notes and related links

Audience — Operators, developers, and team leads connecting HubSpot to AKOBOT agents and automations.

Overview

HubSpot is a MCP integration in the Data category. It extends AKOBOT agents with real-world actions while keeping access scoped to your organization.

Quick access

Configure this integration from the Tool-Kit dashboard or share this page with teammates who need setup guidance.

Capabilities

Run approved queries against connected data sources.
Return tabular summaries suitable for dashboards and chat.
Enforce read/write scopes per connector configuration.
Expose MCP-compatible resources to approved agents.
Govern schema changes through your internal change-control process.

Common use cases

Automate repetitive data tasks with HubSpot.
Combine with AKOBOT agents for natural-language control.
Audit usage and access from the Tool-Kit dashboard.

Setup

1Open the Tool-Kit and locate HubSpot.
2Review availability — this integration may be marked Coming Soon in your tenant.
3Follow the in-product prompts to authorize or configure the connector.
4Validate the integration from an agent or automation test run.
5Assign the tool to agents that should invoke it during conversations.

Coming soon

This connector may appear as Coming Soon in the Tool-Kit until your workspace is provisioned. You can still review this documentation to plan rollout.

Configuration reference

Field	Value
Integration type	MCP
Category	Data
Authentication	Varies by deployment
Availability	Coming soon
Dashboard path	/dashboard/tool-usecase

Operational notes

MCP connectors should be versioned internally. Document owners, secrets rotation, and escalation paths outside of this product guide.