ActionZendeskUpdated May 2026

How do I list comments on a Zendesk ticket?

Short answer: Drop the "Zendesk → Get Ticket Comments" 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 ticketId	string	Required	Ticket ID

Sample request

{
  "ticketId": "{{trigger.ticketId}}"
}

Returns

{
  "comments": [
    {
      "id": 1,
      "body": "Thanks for reaching out",
      "type": "Comment",
      "public": true,
      "author_id": 123,
      "created_at": "2026-04-12T10:00:00Z"
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for Get Ticket Comments.

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 Get Ticket Comments.

What does the Get Ticket Comments action do in Zendesk?

Returns all comments and replies on a Zendesk ticket in chronological order, with public/internal flag and author. Used to feed AI summaries or build transcript exports.

What inputs does Get Ticket Comments 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 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 Get Ticket Comments support batch operations?

Yes. Run Get Ticket Comments 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