List Tickets: 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
Limit limit	number	Optional	Limit. Example: 100

Sample request

{
  "limit": "e.g. 100"
}

Returns

{
  "paging": {
    "next": {
      "after": "100"
    }
  },
  "results": [
    {
      "id": "123",
      "properties": {
        "subject": "Help with billing",
        "hs_pipeline_stage": "1"
      }
    },
    {
      "id": "456",
      "properties": {
        "subject": "Feature request",
        "hs_pipeline_stage": "3"
      }
    }
  ]
}

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

FAQ

Questions about List Tickets.

What does the List Tickets action do in HubSpot?

Lists HubSpot support tickets with optional property selection. For complex filters use Search; this is the simple paginated read.

What inputs does List Tickets require?

List Tickets has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Tickets support batch operations?

Yes. Run List Tickets 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