← Back to Skills Marketplace
6470
Downloads
5
Stars
0
Active Installs
18
Versions
Install in OpenClaw
/install hubspot-api
Description
HubSpot API integration with managed OAuth. The documented surface is CRM: contacts, companies, deals, associations, and properties. What is reachable is decided by the OAuth grant the user approved for this connection, which HubSpot enforces on every request: if that grant covers marketing, CMS, conversations or automation scopes, those APIs are reachable too. This skill uses the CRM endpoints and asks before touching any other. Use this skill when users want to create or update CRM records, search contacts, or sync data with HubSpot; anything outside CRM needs the user to ask for that endpoint by name. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a HubSpot connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a HubSpot action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with HubSpot examples; they add no HubSpot capability - HubSpot is itself an event source, so its own events are in `references/hubspot/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install only if you intend to let Maton access your HubSpot account. Use least-privilege OAuth scopes, confirm every write/delete/bulk operation, and be especially careful with triggers or destinations because they can forward future CRM events automatically until removed.
Capability Assessment
Credentials
Network access, OAuth, credential-store use, and HubSpot API calls are proportionate for an API integration. The artifact warns not to inspect credentials, not to persist API keys, and to send raw HTTP keys only to api.maton.ai.
Install Mechanism
Installation uses pinned Maton CLI/package versions via npm or Homebrew, with SDK packages also pinned. No bundled executable scripts or hidden install hooks were found.
Instruction Scope
The instructions repeatedly require read-first behavior and explicit user approval before connection creation, writes, deletes, hosted function deployment, trigger destinations, and local --exec handlers. The bundled HubSpot trigger reference includes ticket events, which is broader than the primary endpoint surface but is presented as event-source reference material requiring user request by name.
Persistence & Privilege
The skill can create long-lived OAuth connections, hosted functions, and persistent trigger destinations, but these are disclosed, user-approved, scoped, and include cleanup and destination-risk guidance.
Purpose & Capability
The stated purpose is HubSpot CRM access through Maton OAuth, and the documented capabilities fit that purpose: contacts, companies, deals, associations, properties, optional hosted functions, triggers, and raw HTTP only when the CLI is unavailable.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install hubspot-api - After installation, invoke the skill by name or use
/hubspot-api - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.9
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.8
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.7
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.6
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.4
Tell the connection-to-function-to-trigger story for this app: the Functions section opens with a function that performs one action for this app through the Maton SDK, the Triggers section opens with the trigger that runs it (this app's own event source where it has one, otherwise a time schedule), and the description says these are the constructs that turn the connection into automation and add no capability of their own. Framing is generated from a per-app record so the shared platform text stays identical to api-gateway.
v1.2.3
Explain the platform sections this skill shares with api-gateway: why hosted functions and triggers are documented here, whether this app is an event source, that the trigger reference files are the platform's event catalogues and add no capability for this app, and that destinations forward source payloads rather than this app's records. Adds this skill's own policy: destinations stay on api.maton.ai or *.maton.app unless the user names and approves a third-party host, and functions set up during a task here are deployed with DENY_ALL networking. Each trigger reference opens with the same framing.
v1.2.2
Bring the skill to the current api-gateway baseline: API reference, Functions and trigger references mirrored from api-gateway 1.2.17; CLI and SDK installs pinned to 0.3.1; absolute API URLs replaced with placeholders; multipart uploads use mktemp; the passthrough is described by its enforced boundary (host pinning and the connection's authorization) rather than as a documented list that is not a technical limit; the native-API-docs tip no longer reads as a menu of further endpoints. The description states that what is reachable is decided by the OAuth grant HubSpot enforces, and that this skill uses the CRM endpoints and asks before any other.
v1.2.1
Stop under-declaring the scope: the description, the access-scope statement and the API Command section now say that the maton api passthrough reaches every HubSpot API the connection is authorized for, not only the documented CRM endpoints, and that non-CRM APIs such as marketing email, CMS publishing and workflow automation have effects invisible in a CRM record
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.7
- Removed the file skill-card.md.
- No other changes to functionality or usage.
v1.0.6
- Added Maton CLI command examples throughout (for contacts, companies, deals, associations, and connection management).
- New installation instructions for Maton CLI via NPM and Homebrew.
- Expanded authentication section with CLI login flow.
- Each API resource section now includes a corresponding Maton CLI usage example.
- Clarified specifying connections via CLI and Python.
- No functional API changes; documentation improvements only.
v1.0.5
- Switched all API endpoint URLs from `gateway.maton.ai` and `ctrl.maton.ai` to `api.maton.ai` for consistency.
- Updated code examples and connection management instructions to use the new `api.maton.ai` URLs.
- Clarified usage of the `Maton-Connection` header: now required if you have multiple HubSpot connections.
- Added a security notice: all write operations (create, update, delete) require explicit user approval.
- Simplified and realigned documentation to match the latest Maton API proxy changes.
- Removed the LICENSE.txt file.
v1.0.4
- Added metadata field for Clawdbot integration, including required environment variable MATON_API_KEY.
- No other user-facing changes or functionality updates.
v1.0.3
No changes detected in this version.
- Version 1.0.3 includes no file changes or updates.
v1.0.2
- Added a reference to the api-gateway skill in the description for use with other third-party apps.
- Updated all shell (curl) code examples to Python equivalents using `urllib.request` for connection management and API usage.
- Improved documentation for setting and using the API key as an environment variable.
- No changes to the core functionality or API endpoints.
v1.0.1
- Updated the base URL section for clarity: now specifies `{native-api-path}` and clarifies proxying to HubSpot endpoints.
- Expanded "Get Connection" sample response with new fields (`creation_time`, `last_updated_time`, `metadata`).
- Clarified instructions for choosing between multiple HubSpot connections, including default selection behavior.
- Improved description of the API key acquisition process.
- Made minor improvements to headings and explanatory text for better usability and accuracy.
v1.0.0
Initial release with Maton-managed OAuth and HubSpot CRM integration
- Provide API access to HubSpot CRM via the Maton gateway using managed OAuth (no manual token setup).
- Support for managing contacts, companies, and deals with create, read, update, delete, and search operations.
- Association and batch operations supported through documented endpoints.
- Allows multiple HubSpot account connections; select via `Maton-Connection` header.
- Comprehensive setup instructions, including connection management through the Maton control panel.
- Includes detailed cURL request examples and API field/operator references.
Metadata
Frequently Asked Questions
What is HubSpot?
HubSpot API integration with managed OAuth. The documented surface is CRM: contacts, companies, deals, associations, and properties. What is reachable is decided by the OAuth grant the user approved for this connection, which HubSpot enforces on every request: if that grant covers marketing, CMS, conversations or automation scopes, those APIs are reachable too. This skill uses the CRM endpoints and asks before touching any other. Use this skill when users want to create or update CRM records, search contacts, or sync data with HubSpot; anything outside CRM needs the user to ask for that endpoint by name. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a HubSpot connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a HubSpot action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with HubSpot examples; they add no HubSpot capability - HubSpot is itself an event source, so its own events are in `references/hubspot/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 6470 downloads so far.
How do I install HubSpot?
Run "/install hubspot-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is HubSpot free?
Yes, HubSpot is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does HubSpot support?
HubSpot is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created HubSpot?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.9.
More Skills