ActionHubSpotUpdated September 2026

How do I fetch a HubSpot ticket by ID?

Short answer: You can get ticket in HubSpot by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the HubSpot Get Ticket action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Ticket in HubSpot — start free All 23 HubSpot actions

Get Ticket in HubSpot — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Ticket ID ticket_id	string	Required	HubSpot ticket record ID — a numeric string. Find via List Tickets.

Sample request

{
  "ticket_id": "e.g. 4567890123"
}

Returns

{
  "id": "123456",
  "properties": {
    "content": "I was charged twice",
    "subject": "Need help with billing",
    "hs_pipeline_stage": "1",
    "hs_ticket_priority": "HIGH"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Ticket.

Any of these apps can fire this action as part of a workflow.

Google Sheets → HubSpot

2 Google Sheets triggers

Stripe → HubSpot

10 Stripe triggers

FAQ

Questions about Get Ticket.

What does the Get Ticket action do in HubSpot?

Gets a HubSpot support ticket by ID with all of its standard and custom properties. The standard read after a ticket trigger fires.

What inputs does Get Ticket require?

Required: Ticket ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if HubSpot returns an error?

The run history shows the failed step with its input and the error message HubSpot returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Ticket support batch operations?

Run Get Ticket inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within HubSpot's rate limits.

More actions