ActionZendeskUpdated September 2026

How do I add a comment to a Zendesk ticket?

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

Add Comment to 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.

FieldTypeRequiredDescription
Ticket ID
ticket_id
stringRequiredZendesk ticket ID — numeric. Find via Search Tickets.
Comment Body
body
stringRequiredThe comment text (plain text or HTML)
Visibility
public
optionsOptionalVisibility. Options: Public (visible to requester), Internal Note (agents only)
Author ID
author_id
stringOptionalZendesk user ID of the comment author. Defaults to the authenticated agent.
Sample request
{
"ticket_id": "e.g. 123",
"body": "e.g. We are looking into this issue and will follow up shortly.",
"public": "{{trigger.public}}",
"author_id": "e.g. 789"
}
Returns
{
"audit": {
"events": [
{
"body": "We are looking into this issue.",
"type": "Comment",
"public": true
}
]
},
"ticket": {
"id": 123,
"status": "open",
"subject": "Help with billing"
}
}

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

Triggered by

Apps that pair well as the trigger for Add Comment to Ticket.

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

FAQ

Questions about Add Comment to Ticket.

What does the Add Comment to Ticket action do in Zendesk?
Adds a public comment (customer-visible) or internal note to an existing Zendesk ticket. Used for AI summary notes, automated status broadcasts, or piping context from external systems.
What inputs does Add Comment to Ticket require?
Required: Ticket ID, Comment Body. 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 Add Comment to Ticket support batch operations?
Run Add Comment to 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

Other Zendesk actions.

Add Comment to Ticket in Zendesk — start free