Search 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
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.

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

Yes. Run Search 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