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.
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. |
Comment Body body | string | Required | The comment text (plain text or HTML) |
Visibility public | options | Optional | Visibility. Options: Public (visible to requester), Internal Note (agents only) |
Author ID author_id | string | Optional | Zendesk user ID of the comment author. Defaults to the authenticated agent. |
{"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"}
{"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.
Any of these apps can fire this action as part of a workflow.