HubSpot integration via Apideck's CRM unified API — same methods work across every connector in CRM, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in HubSpot. Routes through Apideck with serviceId "hubspot".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Access HubSpot through Apideck's CRM unified API — one of 21 CRM connectors that share the same method surface. Code you write here ports to Odoo, Salesforce, Pipedrive and 17 other CRM connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant HubSpot plumbing.
hubspotActivate this skill when the user explicitly wants to work with HubSpot — for example, "pull contacts in HubSpot" or "sync leads in HubSpot". This skill teaches the agent:
serviceId to pass on every call (hubspot)For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-restFor the raw OpenAPI spec:
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List contacts in HubSpot
const { data } = await apideck.crm.contacts.list({
serviceId: "hubspot",
});The Apideck CRM unified API exposes the same methods for every connector in its catalog. Switching from HubSpot to another CRM connector is a one-string change — no rewrite, no new SDK.
// Today — HubSpot
await apideck.crm.contacts.list({ serviceId: "hubspot" });
// Tomorrow — same code, different connector
await apideck.crm.contacts.list({ serviceId: "odoo" });
await apideck.crm.contacts.list({ serviceId: "salesforce" });This is the compounding advantage of using Apideck over integrating HubSpot directly: code against the unified CRM API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
HubSpot is Apideck's most-installed SMB CRM connector. Strong coverage for contacts, companies, deals (opportunities), and activities.
| HubSpot entity | Apideck CRM resource |
|---|---|
| Contact | contacts |
| Company | companies |
| Deal | opportunities |
| Engagement (email, call, meeting, note, task) | activities / notes |
| Pipeline / Deal Stage | pipelines |
| Owner | users |
| Custom properties | custom_fields[] |
| Lists (static/dynamic) | not in unified API — use Proxy |
custom_fields[]/crm/v3/listshubId). Multi-portal = multi-connection.const { data } = await apideck.crm.opportunities.list({
serviceId: "hubspot",
filter: { status: "open" },
fields: "id,name,amount,close_date,pipeline,owner_id,company_id",
});const { data } = await apideck.crm.contacts.create({
serviceId: "hubspot",
contact: {
first_name: "Alex",
last_name: "Rivera",
emails: [{ email: "alex@example.com", type: "primary" }],
company_id: "hs_company_123",
},
});When an endpoint isn't covered by the CRM unified API, use Apideck's Proxy to call HubSpot directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on HubSpot's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: hubspot" \
-H "x-apideck-downstream-url: <target endpoint on HubSpot>" \
-H "x-apideck-downstream-method: GET"See HubSpot's API docs for available endpoints.
Other CRM connectors that share this unified API surface (same method signatures, just change serviceId):
odoo (beta), salesforce, pipedrive, zoho-crm, activecampaign, close, microsoft-dynamics, teamleader, and 12 more.
apideck-connector-coverage — programmatic coverage checksapideck-best-practices — architecture, Vault, pagination, error handlingapideck-node — TypeScript / Node SDK patterns9e04d86
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.