ActionZendeskUpdated September 2026

How do I update a Zendesk ticket?

Short answer: You can update ticket in Zendesk by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Zendesk 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 Zendesk — start free All 17 Zendesk actions

Update Ticket in Zendesk — 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	Zendesk ticket ID — numeric. Find via Search Tickets.
Status status	options	Optional	Status. Options: New, Open, Pending, Hold, Solved, Closed
Priority priority	options	Optional	Priority. Options: Low, Normal, High, Urgent
Assignee ID assignee_id	string	Optional	Zendesk user ID of the agent to assign
Comment comment_body	string	Optional	Add a public comment to the ticket
Internal Note internal_note	string	Optional	Add an internal note (not visible to requester)
Tags tags	string	Optional	Comma-separated tags (replaces existing tags)

Sample request

{
  "ticket_id": "e.g. 123",
  "status": "{{trigger.status}}",
  "priority": "{{trigger.priority}}",
  "assignee_id": "e.g. 789",
  "comment_body": "{{trigger.comment_body}}"
}

Returns

{
  "ticket": {
    "id": 123,
    "status": "solved",
    "priority": "high"
  }
}

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 → Zendesk

2 Google Sheets triggers

HubSpot → Zendesk

18 HubSpot triggers

FAQ

Questions about Update Ticket.

What does the Update Ticket action do in Zendesk?

Updates an existing Zendesk ticket: status, priority, assignee, group, tags, custom fields, or add a new comment. 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 Zendesk returns an error?

The run history shows the failed step with its input and the error message Zendesk 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 Zendesk's rate limits.

More actions