HubSpot Tickets — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited HubSpot Tickets (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Tickets in HubSpot represent support requests, service issues, or tasks that need resolution. For MSPs, tickets are the backbone of client service delivery -- tracking everything from break-fix requests and password resets to complex infrastructure projects. Tickets belong to a pipeline (e.g., "Support Pipeline") and progress through stages (e.g., "New", "In Progress", "Resolved"). They can be associated with contacts (the person who reported the issue), companies (the client organization), and deals (if the ticket relates to a service agreement).
| Tool | Description | Key Parameters |
|---|---|---|
hubspot_retrieve_ticket | Get a single ticket by ID | ticketId (required) |
hubspot_create_ticket | Create a new ticket | subject (required), content, hs_pipeline, hs_pipeline_stage |
hubspot_update_ticket | Update an existing ticket | ticketId (required), property fields to update |
Call hubspot_create_ticket with the ticket's properties:
Example: Create a support ticket:
subject: Email delivery issues - Acme Corpcontent: Client reports intermittent email delivery failures since Monday morning. Affects 5 users on the acmecorp.com domain.hs_pipeline: 0 (default support pipeline)hs_pipeline_stage: 1 (New)hs_ticket_priority: HIGHhubspot_owner_id: 67890Call hubspot_update_ticket with the ticketId and the properties to change:
Example: Move ticket to In Progress:
ticketId: 77777hs_pipeline_stage: 2Example: Resolve a ticket:
ticketId: 77777hs_pipeline_stage: 4hs_resolution: Reconfigured mail relay settings. Confirmed delivery restored for all 5 users.Call hubspot_retrieve_ticket with the ticketId:
Example:
hubspot_retrieve_ticket with ticketId=77777Tickets can be found via the associations API. To find tickets for a specific contact or company:
hubspot_access_associations with the contact or company ID and toObjectType=tickethubspot_retrieve_ticketHubSpot's default support pipeline includes these stages (your account may have custom stages):
| Stage ID | Display Name | Description |
|---|---|---|
1 | New | Ticket just created, not yet assigned |
2 | Waiting on contact | Awaiting response from the client |
3 | Waiting on us | MSP team needs to take action |
4 | Closed | Ticket resolved and closed |
| Priority | Description | MSP Context |
|---|---|---|
LOW | Low priority | Non-urgent request, no business impact |
MEDIUM | Medium priority | Some business impact, can wait |
HIGH | High priority | Significant business impact, needs prompt attention |
MSPs commonly categorize tickets by type:
| Category | Examples |
|---|---|
| Break-Fix | Hardware failure, software crash |
| Service Request | Password reset, new user setup |
| Project | Network upgrade, server migration |
| Billing | Invoice question, contract change |
| Monitoring Alert | Automated alert from RMM/monitoring |
| Field | Type | Description |
|---|---|---|
subject | string | Ticket subject line |
content | string | Ticket description/body |
hs_pipeline | enumeration | Pipeline the ticket belongs to |
hs_pipeline_stage | enumeration | Current pipeline stage |
hs_ticket_priority | enumeration | Priority level (LOW, MEDIUM, HIGH) |
hs_ticket_category | enumeration | Ticket category |
hubspot_owner_id | number | Assigned owner (user ID) |
hs_resolution | string | Resolution description |
source_type | enumeration | How the ticket was created (EMAIL, CHAT, PHONE, FORM) |
createdate | datetime | Record creation date |
lastmodifieddate | datetime | Last modification date |
closed_date | datetime | When the ticket was closed |
hs_time_to_close_sla_due_date | datetime | SLA close deadline |
hs_time_to_first_response_sla_due_date | datetime | SLA first response deadline |
hs_last_message_received_at | datetime | Last client message timestamp |
hs_last_message_sent_at | datetime | Last agent message timestamp |
num_associated_contacts | number | Associated contacts count |
hubspot_search_contacts to find the person reporting the issuehubspot_search_companies to find the client organizationhubspot_create_ticket with subject, content, pipeline, stage, priority, and ownerhubspot_create_association from ticket to contacthubspot_create_association from ticket to companyhubspot_create_note to document initial triage findingshubspot_search_companieshubspot_access_associations with the company ID and toObjectType=tickethubspot_retrieve_ticket to get full detailshubspot_retrieve_ticket to confirm current statehubspot_update_ticket with the new hs_pipeline_stagehs_resolution describing the fixhubspot_create_note to log the status change detailshubspot_search_companieshubspot_access_associations to get all ticketshubspot_retrieve_ticket to review the current tickethubspot_update_ticket to set hs_ticket_priority to HIGHhubspot_update_ticket to reassign hubspot_owner_id to the escalation engineerhubspot_create_note to document the escalation reasonhubspot_create_task to create a follow-up task for the assigned engineerSingle Ticket:
{
"id": "77777",
"properties": {
"subject": "Email delivery issues - Acme Corp",
"content": "Client reports intermittent email delivery failures since Monday morning.",
"hs_pipeline": "0",
"hs_pipeline_stage": "2",
"hs_ticket_priority": "HIGH",
"hubspot_owner_id": "67890",
"source_type": "EMAIL",
"createdate": "2026-02-20T09:15:00.000Z",
"lastmodifieddate": "2026-02-21T14:30:00.000Z",
"closed_date": null,
"num_associated_contacts": "1"
},
"createdAt": "2026-02-20T09:15:00.000Z",
"updatedAt": "2026-02-21T14:30:00.000Z"
}| Error | Cause | Resolution |
|---|---|---|
| Ticket not found | Invalid ticket ID | Verify the ID by checking associations or searching |
| Invalid pipeline | Pipeline ID not recognized | Check your HubSpot account for available pipelines |
| Invalid pipeline stage | Stage ID not valid for the pipeline | Use a valid stage ID for the selected pipeline |
| Invalid priority | Priority value not recognized | Use LOW, MEDIUM, or HIGH |
| Rate limited | Too many requests | Wait 10 seconds and retry |
hs_resolution when closing ticketshs_time_to_first_response_sla_due_date and hs_time_to_close_sla_due_datehubspot_owner_id for accountability~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.