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.
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.