List Tickets: Zendesk 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
Sort By sort_by	options	Optional	Sort By. Options: Created At, Updated At, Priority, Status
Sort Order sort_order	options	Optional	Sort Order. Options: Descending, Ascending
Page page	string	Optional	Page. e.g. "1"
Per Page per_page	string	Optional	Results per page (max 100)

Sample request

{
  "sort_by": "{{trigger.sort_by}}",
  "sort_order": "{{trigger.sort_order}}",
  "page": "1",
  "per_page": "25"
}

Returns

{
  "count": 42,
  "tickets": [
    {
      "id": 123,
      "status": "open",
      "subject": "Help!",
      "priority": "normal"
    }
  ]
}

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 Zendesk?

Retrieves a paginated list of Zendesk tickets. For complex filters or older tickets, use Search Tickets; this action returns the unfiltered queue with cursor pagination.

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 Zendesk 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 Zendesk's rate limits automatically so you don't have to throttle manually.

More actions