Get Ticket: HubSpot action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Ticket support batch operations?

Yes. Run Get Ticket inside a Loop node to process arrays. Tiny Command handles HubSpot's rate limits automatically so you don't have to throttle manually.

More actions