List Ticket Conversations
freshservice.list_ticket_conversations
ActionBusiness appsconnection required
Calls the Freshservice API with the connection's credentials.
List the replies and notes recorded on a Freshservice ticket.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Freshservice
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- domain, workspace_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
ticket_id The Freshservice ticket to act on, by its numeric id. | string | Yes | — | — | 265 |
per_page How many records Freshservice returns per page; it defaults to 30 and caps at 100. | number | No | — | 1–100 | 30 |
page Which page to start from; Freshservice numbers pages from 1. | number | No | — | ≥ 1 | 1 |
max_pages How many 'rel=next' link-header pages to follow before stopping and reporting a cursor. | number | No | 1 | ≥ 1 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"max_pages": 1,
"page": 1,
"per_page": 30,
"ticket_id": "265"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The records Freshservice returned across the pages that were read. | array | — |
count How many records are in 'items'. | number | — |
pages How many pages were actually fetched. | number | — |
next_page The page number to resume from, or null at the end. | number | — |
next_url The 'rel=next' URL Freshservice sent, or empty at the end. | string | — |
{
"count": 0,
"items": [],
"next_page": 0,
"next_url": "",
"pages": 0
}Notes
- Freshservice sends a 'rel=next' link header only while another page exists, so an empty next_page is the end of the collection, not a truncated answer.
- A page holds 30 records by default and 100 at most.
See List Ticket Conversations run in a workflow.
In a technical demo we add the Freshservice connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.