Ticket Resolution

A complete workflow for managing HubSpot support tickets through the CLI, from creation through triage to resolution. It walks you through pipeline discovery (critical, since stage IDs differ per portal), bulk ticket creation from JSONL queues, filtering by priority and assignment status, and moving tickets between stages with dry run protection. The enum probing technique is clever: send an invalid value to get HubSpot to return the valid options list, since the properties API won't give them to you. Most useful when you need to process tickets at scale or automate common triage patterns like bulk reassignment or stage advancement based on category filters.

skills.sh installs: 2.1K
GitHub stars: 29
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add hubspot/agent-cli-skills --skill ticket-resolution --agent claude-code

Installs into .claude/skills of the current project.

Files

Read bulk-operations/SKILL.md first — JSONL piping, batch read, pagination, dry-run/digest/confirm, and hubspot history recovery live there. hubspot <command> --help is authoritative. Tickets use the tickets object type (plural, e.g. tickets:45123).

1. Discover pipeline + stages (portal-specific, run every session)

Stage IDs differ in every portal — never hard-code them.

hubspot pipelines list --type tickets --format table
hubspot pipelines stages --type tickets --pipeline <pipeline_id> --format table

The stage table prints each stage's ID and Label ("New", "Waiting on contact", "Closed", etc.). pipelines list/get also return each pipeline's full stages array in jsonl/json, so one call is enough to map a hs_pipeline_stage value to its label.