- Integrations
- /
- Freshdesk
- /
- Actions
- /
- Search Tickets
ActionFreshdeskUpdated May 2026
How do I search Freshdesk tickets?
Short answer: Drop the "Freshdesk → Search Tickets" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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.
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
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.
ActionCreate Company
Creates a new company (B2B customer account) in Freshdesk. Used to mirror your CRM accounts into the helpdesk so contacts auto-link.
ActionCreate Contact
Creates a new contact (end-customer) in Freshdesk with name, email, phone, company, and tags. Used to provision contacts before ticket creation.
ActionCreate 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.
ActionDelete Contact
Deletes a Freshdesk contact by ID. Note that this hides the contact rather than permanently removing them, so their tickets are preserved.
ActionDelete 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.
Send search tickets from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.