ActionZendeskUpdated May 2026

How do I add a comment to a Zendesk ticket?

Short answer: Drop the "Zendesk → Add Comment to Ticket" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 17 Zendesk actions

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

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.

Google Sheets → Zendesk

2 Google Sheets triggers

HubSpot → Zendesk

18 HubSpot triggers

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Add Comment to Ticket support batch operations?

Yes. Run Add Comment to Ticket inside a Loop node to process arrays. Tiny Command handles Zendesk's rate limits automatically so you don't have to throttle manually.

More actions