Install
$ agentstack add skill-dipankar-hubspot-cli-hubspot-tickets ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
HubSpot Tickets (via hubspot CLI)
Tickets represent customer service cases. They live in a ticket pipeline and move through stages (New → Waiting on contact → Waiting on us → Closed).
Auth
Set HUBSPOT_ACCESS_TOKEN. Optional --profile .
Canonical commands
| Intent | Command | | --- | --- | | List open tickets | hubspot crm tickets list --limit 20 --properties subject,hs_pipeline_stage,hs_ticket_priority | | Get by ID | hubspot crm tickets get 12345 | | Create | hubspot crm tickets create --subject "Login broken" --content "User reports 500" --priority HIGH | | Create from JSON | hubspot crm tickets create --properties '{"subject":"Login broken","hs_pipeline":"0","hs_pipeline_stage":"1","hs_ticket_priority":"HIGH"}' | | Update stage | hubspot crm tickets update 12345 --properties '{"hs_pipeline_stage":"4"}' | | Close | hubspot crm tickets update 12345 --properties '{"hs_pipeline_stage":"4","hs_resolution":"RESOLVED"}' | | Delete | hubspot crm tickets delete 12345 --yes | | Search by priority | hubspot crm tickets search --filter-groups '[{"filters":[{"propertyName":"hs_ticket_priority","operator":"EQ","value":"HIGH"}]}]' | | Open tickets only | hubspot crm tickets search --filter-groups '[{"filters":[{"propertyName":"hs_pipeline_stage","operator":"NEQ","value":"4"}]}]' |
Pipelines and stages
hubspot crm pipelines list tickets
hubspot crm pipelines stages tickets
Ticket stage IDs are numeric strings ("1", "2", "3", "4"), unlike deal stages which are named.
Common properties
subject, content, hs_pipeline, hs_pipeline_stage, hs_ticket_priority (LOW|MEDIUM|HIGH), hs_ticket_category, hubspot_owner_id, source_type, createdate.
Associating tickets
hubspot crm associations create tickets 12345 contacts 67890
hubspot crm associations create tickets 12345 companies 54321
hubspot crm associations create tickets 12345 deals 11111
Scopes
- Read:
tickets - Write:
tickets
Tips
- If
hs_pipelineis omitted on create, HubSpot uses the default ticket pipeline — fine for most cases. hs_resolutionis free text; standardize on values the team already uses.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dipankar
- Source: dipankar/hubspot-cli
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.