ActionFreshserviceUpdated September 2026

How do I update a Freshservice ticket?

Short answer: You can update freshservice ticket in Freshservice by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Freshservice Update Freshservice Ticket action to a workflow, map its 8 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Update Freshservice Ticket in Freshservice — start free All 7 Freshservice actions

Update Freshservice Ticket in Freshservice — 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.

Field	Type	Required	Description
Ticket ID ticket_id	string	Required	The numeric ID of the ticket to update
Subject subject	string	Optional	Message subject line.
Description description	string	Optional	Updated HTML description
Priority priority	options	Optional	Priority. Options: Low, Medium, High, Urgent
Status status	options	Optional	Status. Options: Open, Pending, Resolved, Closed
Category category	string	Optional	Ticket category (e.g. Hardware, Software, Network)
Sub-Category sub_category	string	Optional	Sub-Category. Example: MS Office
Type type	options	Optional	Type. Options: Incident, Service Request, Problem, Change

Sample request

{
  "ticket_id": "e.g. 123",
  "subject": "e.g. Quick update",
  "description": "{{trigger.description}}",
  "priority": "{{trigger.priority}}",
  "status": "{{trigger.status}}"
}

Returns

{
  "ticket": {
    "id": 123,
    "type": "Incident",
    "status": 4,
    "subject": "Updated subject",
    "priority": 3
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Update Freshservice Ticket.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Freshservice

2 Google Sheets triggers

HubSpot → Freshservice

18 HubSpot triggers

FAQ

Questions about Update Freshservice Ticket.

What does the Update Freshservice Ticket action do in Freshservice?

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.

What inputs does Update 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 run history shows the failed step with its input and the error message Freshservice returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Update Freshservice Ticket support batch operations?

Run Update Freshservice Ticket inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Freshservice's rate limits.

More actions