Zendesk

Read Zendesk tickets, users, or organizations.

Category: Input
Connection: Zendesk

What it does

Reads Zendesk Support resources (tickets, users, organizations and the rest) through a saved Connection, following Zendesk's next-page links to the end. Pick the resource, and add any of Zendesk's own query parameters to sort or narrow the read. Each record becomes a row.

Inputs and outputs

Inputs	None. This node starts a pipeline.
Outputs	One.

When to use it

Analyze support volume and response times
Join ticket data with customer or product data
Archive tickets to a warehouse on a schedule

Examples

Tickets

Resource: tickets

The common case: every ticket the credential can see.

Users

Resource: users

The same node reads any Support resource; only this box changes.

Sorted

Extra parameter: sort_by = created_at

Zendesk's own parameters are passed straight through.

Bound a new connection

Max records: 500

Stops after 500 records while you're still working out the read.

Tips

The credential is an API token; Zendesk wants the account email with it, which is handled for you.
Use “Fetch sample” to fill in the columns so downstream nodes see them without a run.
Zendesk caps this style of paging at 10,000 records, so a run over a larger history stops with a 400 from Zendesk rather than reading on. Narrow it with a filter, for example on updated_at, so each run picks up only what changed.
Max records is a real cap: it stops mid-page rather than delivering the rest of the page you were on.
Nested fields arrive as dotted columns; pull anything deeper out downstream with the JSON parse node.