ActionFreshdeskUpdated September 2026

How do I update a Freshdesk ticket?

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

Update Ticket in Freshdesk — start free All 15 Freshdesk actions

Update Ticket 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.

Field	Type	Required	Description
Ticket ID ticket_id	string	Required	The numeric ID of the ticket to update
Subject subject	string	Optional	New subject for the ticket
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
Group group_id	dynamic-options	Optional	Group. (select from available options)
Assign To Agent responder_id	dynamic-options	Optional	Assign To Agent. (select from available options)

Sample request

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

Returns

{
  "id": 123,
  "status": 4,
  "subject": "Updated subject",
  "priority": 3,
  "updated_at": "2024-01-02T00:00:00Z"
}

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

Triggered by

Apps that pair well as the trigger for Update Ticket.

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

Google Sheets → Freshdesk

2 Google Sheets triggers

HubSpot → Freshdesk

18 HubSpot triggers

FAQ

Questions about Update Ticket.

What does the Update Ticket action do in Freshdesk?

Updates an existing Freshdesk ticket: status, priority, assignee, group, type, or custom fields. The standard hook to reflect downstream actions back into the helpdesk.

What inputs does Update 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 Freshdesk returns an error?

The run history shows the failed step with its input and the error message Freshdesk 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 Ticket support batch operations?

Run Update 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 Freshdesk's rate limits.

More actions