List Changes

freshservice.list_changes
ActionBusiness appsconnection required

Calls the Freshservice API with the connection's credentials.

List Freshservice change requests, by query or by a saved view.

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

9 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
query
Filter expression over change fields, such as "status:1 AND risk:4".
stringNo———
view
Name or id of a saved Change Management view; cannot be combined with query.
stringNo———
updated_since
Return changes updated since this UTC timestamp.
stringNo—iso8601 format—
order_by
Field to sort by, such as priority or updated_at.
stringNo———
order_type
Sort direction; Freshservice sorts descending unless this says otherwise.
stringNo—one of "asc", "desc"—
workspace_id
Workspace to act in; defaults to the connection's workspace, then the primary one. Only accounts on the workspaces plan use it.
stringNo———
per_page
How many records Freshservice returns per page; it defaults to 30 and caps at 100.
numberNo—1–10030
page
Which page to start from; Freshservice numbers pages from 1.
numberNo—≥ 11
max_pages
How many 'rel=next' link-header pages to follow before stopping and reporting a cursor.
numberNo1≥ 1—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "max_pages": 1,
  "page": 1,
  "per_page": 30
}

Output

One shape.

result

FieldTypeExample
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 refuses query and view together; set one of them or neither.
  • 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 Changes 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.