Start free
ActionFreshdeskUpdated June 2026

How do I search Freshdesk tickets?

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

Search Tickets in Freshdesk — start free All 15 Freshdesk actions
Search Tickets in Freshdesk — 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.

FieldTypeRequiredDescription
Search Query
query
stringRequiredFreshdesk 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.

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.

Gmail → Freshdesk
1 Gmail triggers
Slack → Freshdesk
13 Slack triggers
Google Sheets → Freshdesk
2 Google Sheets triggers
HubSpot → Freshdesk
18 HubSpot triggers
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. TinyCommand handles Freshdesk's rate limits automatically so you don't have to throttle manually.
More actions

Other Freshdesk actions.

Action
Add Note to Ticket
Adds a note (private or public) or a reply to an existing Freshdesk ticket. Used for AI-summary notes, automated status updates, or piping context from external systems.
Action
Create Company
Creates a new company (B2B customer account) in Freshdesk. Used to mirror your CRM accounts into the helpdesk so contacts auto-link.
Action
Create Contact
Creates a new contact (end-customer) in Freshdesk with name, email, phone, company, and tags. Used to provision contacts before ticket creation.
Action
Create Ticket
Creates a new support ticket in Freshdesk with requester, subject, description, source, priority, status, group, and agent. The entry point for converting external alerts or forms into trackable tickets.
Action
Delete Contact
Deletes a Freshdesk contact by ID. Note that this hides the contact rather than permanently removing them, so their tickets are preserved.
Action
Delete Ticket
Deletes a Freshdesk ticket by ID. Tickets move to trash for 30 days before permanent deletion, so this is recoverable in the short term.
Search Tickets in Freshdesk — start free