# Hubspot Tickets

> Use when the user wants to manage HubSpot CRM tickets (support cases, service desk issues, customer requests) via the `hubspot` command-line tool.

- Skill: `dipankar/hubspot-tickets` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dipankar/hubspot-tickets`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dipankar/hubspot-tickets/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: dipankar (https://skillmd.com/u/dipankar)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dipankar/hubspot-tickets

---


# 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 <name>`.

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

```bash
hubspot crm pipelines list tickets
hubspot crm pipelines stages tickets <pipeline_id>
```

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

```bash
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_pipeline` is omitted on create, HubSpot uses the default ticket pipeline — fine for most cases.
- `hs_resolution` is free text; standardize on values the team already uses.