ActionZendeskUpdated September 2026

How do I search Zendesk tickets?

Short answer: You can search tickets in Zendesk by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Zendesk Search Tickets action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Search Tickets in Zendesk — start free All 17 Zendesk actions

Search Tickets in Zendesk — 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
Search Query query	string	Required	Zendesk search query (e.g. 'type:ticket status:open priority:high')
Sort By sort_by	options	Optional	Sort By. Options: Created At, Updated At, Relevance
Per Page per_page	string	Optional	Per Page. e.g. "25"

Sample request

{
  "query": "e.g. type:ticket status:open assignee:johndoe",
  "sort_by": "{{trigger.sort_by}}",
  "per_page": "25"
}

Returns

{
  "count": 5,
  "results": [
    {
      "id": 123,
      "status": "open",
      "subject": "Billing issue",
      "result_type": "ticket"
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for Search Tickets.

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

Google Sheets → Zendesk

2 Google Sheets triggers

HubSpot → Zendesk

18 HubSpot triggers

FAQ

Questions about Search Tickets.

What does the Search Tickets action do in Zendesk?

Searches for tickets using Zendesk's search query syntax (status:, assignee:, type:, tags:, created>). Powers SLA dashboards, segment reports, and upsert lookups.

What inputs does Search Tickets require?

Required: Search Query. 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 Zendesk returns an error?

The run history shows the failed step with its input and the error message Zendesk 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 Search Tickets support batch operations?

Run Search Tickets 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 Zendesk's rate limits.

More actions