HubSpot through Squiid

What HubSpot is

HubSpot is a CRM and marketing platform with a full API over its objects: contacts, companies, deals, tickets, line items and custom objects, along with forms, email activity, workflows and lists. Associations link records together, and webhooks report changes so an application can react when a deal stage moves or a contact is created. The batch endpoints matter in practice, because updating ten thousand contacts one request at a time will hit rate limits immediately.

For AI-coded products the CRM is where customer context lives. An assistant that drafts a follow-up needs the deal history, a support tool needs the ticket trail, an enrichment job writes firmographic data back onto company records, and a product that sells to businesses often needs to create a contact the moment someone signs up. Doing that with a private app token copied into an environment file is the usual approach and the usual mistake. Property definitions are also customisable per portal, so generated code should read the schema rather than assume field names.

Why connect it through Squiid

HubSpot is on the Squiid roadmap as a connect service. When it lands, you will link the portal you already have through OAuth with the scopes you approve, and Squiid will hold the tokens and issue scoped access through https://api.squiid.io/v1/hubspot/... with Authorization: Bearer $SQUIID_API_KEY, with the official clients working by base URL swap (gateway convention). Your HubSpot subscription stays billed by HubSpot at the provider's listed price, and the connection is revocable in one click. Private app tokens do not expire, which is convenient and is exactly why they end up outliving the person who created them.

• One account, one key, one bill, one dashboard. HubSpot sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the HubSpot credentials. Your code carries SQUIID_API_KEY, so HUBSPOT_ACCESS_TOKEN, HUBSPOT_CLIENT_SECRET, HUBSPOT_PORTAL_ID never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what HubSpot costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Your existing HubSpot portal connected, not replaced
• Contacts, companies, deals and tickets through the API
• Custom objects, associations and webhooks
• Scoped, revocable access for agents
• HubSpot seats stay billed by HubSpot

How to connect HubSpot

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces HUBSPOT_ACCESS_TOKEN, HUBSPOT_CLIENT_SECRET, HUBSPOT_PORTAL_ID
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/hubspot/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

HubSpot bills your subscription directly at the provider's listed price, with no Squiid margin. Squiid passes that through at par: one dollar of prepaid credit is one dollar of HubSpot usage, with no markup and no per-request margin.

HubSpot has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so HubSpot usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Your own account: the HubSpot account was always yours and Squiid only holds an authorised connection, so revoking it leaves nothing behind. Squiid never owns your code, your schema or your domain, and the gateway speaks HubSpot's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

HubSpot through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on HubSpot usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.