Search Tickets: Freshdesk 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	Freshdesk search query (e.g. "status:2 AND priority:3")

Sample request

{
  "query": "e.g. \"status:2 AND priority:4\" or \"tag:'billing'\""
}

Returns

{
  "total": 5,
  "results": [
    {
      "id": 123,
      "status": 2,
      "subject": "Login issue",
      "priority": 4
    }
  ]
}

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

Searches Freshdesk tickets using a query string (status, priority, agent_id, group_id, created_at, custom fields). Use for 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 Freshdesk 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 Freshdesk's rate limits automatically so you don't have to throttle manually.

More actions