- Integrations
- /
- Freshservice
- /
- Actions
- /
- Get Freshservice Ticket
ActionFreshserviceUpdated May 2026
How do I fetch a Freshservice ticket?
Short answer: Drop the "Freshservice → Get Freshservice Ticket" 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 |
|---|---|---|---|
Ticket ID ticket_id | string | Required | Ticket ID. Example: 123 |
Sample request
{"ticket_id": "e.g. 123"}
Returns
{"ticket": {"id": 123,"status": 2,"subject": "Laptop issue","priority": 1}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get Freshservice Ticket.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Freshservice Ticket.
What does the Get Freshservice Ticket action do in Freshservice?
Returns a ticket by ID with full detail — status, requester, agent, conversation history, custom fields. The standard lookup for ticket-context workflows.
What inputs does Get Freshservice Ticket require?
Required: Ticket ID. 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 Freshservice 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 Get Freshservice Ticket support batch operations?
Yes. Run Get Freshservice Ticket inside a Loop node to process arrays. Tiny Command handles Freshservice's rate limits automatically so you don't have to throttle manually.
More actions
Other Freshservice actions.
Action
Add Note to Freshservice Ticket
Posts a public reply or private note to a ticket. Useful for "AI-summarised context → log as private note for the agent" patterns.
ActionCreate Freshservice Ticket
Files a new IT ticket with subject, description, priority, requester, group. For "monitoring alert → auto-file ticket for the on-call team" or "user submitted via portal → create ticket" workflows.
ActionDelete Freshservice Ticket
Removes a ticket (soft delete in most configurations). For "duplicate ticket cleanup" or "spam filtering" maintenance workflows.
ActionList Freshservice Agents
Returns every agent with role, group memberships, contact info. Useful for resolving agent IDs in routing rules or for "show me agents currently on shift" workflows.
ActionList Freshservice Tickets
Paginated tickets with filters by status, priority, requester, agent, group, time range. For "open critical tickets" dashboards or "all tickets I'm the agent on" personal queues.
ActionUpdate Freshservice Ticket
Partial update on ticket fields — status, priority, assignee, custom fields. For "auto-route to the right team based on subject keywords" workflows or for "auto-resolve aged tickets" maintenance.
Send get freshservice ticket from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.