Repository navigation
Releases
Releases · WireCatLabs/hubspot-cli
0.4.0
Changed — may break callers
deals.write,people.writeandorganizations.writeare gone. They stopped only theapipath, so
deals.write: denystill letdeals updatethrough. Anapiwrite on deals, contacts or companies now checks the
key of the command that does the same (deals.update,people.create), as amoCRM and b24 do, and a merge
checks<group>.update. So a raw deal, contact or company write goes ahead as its command does, and deletes still
ask. Watch for: a setting that names one of the three old keys no longer matches anything: set
deals.update,deals.createor the group keydealsinstead.
Fixed
- A read denied on a CRM command is denied through
apitoo.config set permissions.people denystopped
people listbut notapi contacts-list, which read the same contacts. Each raw read now checks the key of the
command that reads the same records:people,organizations,deals,leads,activities,users,pipelines,
stagesandfields. See permissions.
0.3.2
0.3.1
Fixed
- Notes, meetings and tasks read as clean text. HTML codes such as
’and—become the characters
they stand for, and style blocks are left out, so search finds the words. Before, only six codes were decoded. - HubSpot's daily limit says "do not retry" on every path. The CRM commands called it retryable while
apidid
not, so an agent could retry for hours. session start --helpno longer says hubspot changes nothing. Writes shipped in 0.2.0.
0.3.0
Changed — may break callers
- The MCP Registry entry asks which profiles to serve. It started
mcp serve --profiles all, so a client that
installed the server from the registry reached every account on the computer without the owner choosing. Now
--profilesis a required argument with the examplepersonal: the client asks for one profile, a
comma-separated list orall. Why: a CLI never picks an account for the owner
(WC-MCP-9). Watch for: a client set up from the old entry keeps--profiles alluntil it is set up again; a
server added by hand or withmcp configdoes not change.
Fixed
mcp servestarts on a computer with no profile yet. It lists its tools, and each call answers with the command
that sets up a profile. Before, the server stopped at start, so a directory that checks servers could not list
them. From cli-core 0.699.0.
0.2.0
Added
deals create,update,move,closeanddeletechange deals in HubSpot, and the copy takes each answer.
closemoves a deal to its pipeline's closed won or lost stage and keeps--reasonas HubSpot's closed reason.
deletearchives the deal and asks first. See usage.people create|updateandorganizations create|updatechange contacts and companies. A contact keeps one
e-mail and two numbers, a company one number and no e-mail; a longer list is refused before anything is sent.apioffers HubSpot's writes and deletes too: 66 writes and 33 deletes of the CRM API, version 2026-03. Each
write checksapi.<command>and its group's<group>.write, each delete its<group>.delete, and both ask by
default. A write that does what a command does checks that command's key too (deals.update), a body that sets a
deal's stage checksdeals.moveanddeals.close, and one that sets an owner checkscrm.assign-others,denyby
default.api contacts-gdpr-deletealso checkspeople.erase, to deny erasing alone.--dry-runnames every key.
See settings.- Write scopes are optional. The setup and installation list
crm.objects.{deals,contacts,companies}.write; without them the key only reads.
Fixed
apisends the key with every operation. HubSpot's object specs mark 115 operations as needing no sign-in, so
in 0.1.0api deals-get,api contacts-listand the other record operations went out without the key and HubSpot
answered 401. The pipelines, properties, owners and account operations were not affected.
0.1.0
Added
- Started from
@wirecat/cli-template0.25.0. session startsigns a profile in with a HubSpot service key or a private app token. The key is read hidden or
from stdin, never as an argument, checked against the account, and kept in the keyring with the account's id. A
second profile on the same account is refused.WCHUBSPOT_TOKENworks in CI besideWCHUBSPOT_ACCOUNT, the
account's id. See installation.synccopies the account's CRM into WireCat's shared store. Deals, contacts, companies, leads (Sales Hub
Professional or Enterprise), owners, pipelines and properties, and the notes, calls, e-mails, meetings and tasks
once the activities setting is on.deals list,pipelines,changes listandsearch allthen answer offline. A
key names no user, so every profile reads the whole copy: filter byowner:<owner id>, notowner:me.people,organizationsandusersread contacts, companies and owners live from the account.apioffers every read operation of HubSpot's CRM API, version 2026-03, from its 15 specs. One command per
operation, each with its own permission key. This release only reads: the API's writes are not offered, and
api showon one says so.- A spent daily allowance ends the request at once and says when it comes back. HubSpot shares one daily
allowance among every app on the account.hubspotreportshubspot.daily-limitwith the wait to the account's
midnight, and stops every process on the account from asking again before then. The ten-second limit is waited
out. WCHUBSPOT_ACCOUNTis checked againstWCHUBSPOT_TOKENbefore anything is written. Asyncwith an id of
another account stops withaccount.mismatch, naming both ids, so one account's CRM is never filed under another's.
session status --checkwith the token alone prints the id to set. See
troubleshooting.