Zendesk 422 response on Tickets -> Get All

Hello! Newbie here, but having a good time with n8n.

Having a little challenge with the Zendesk Connector, and pulling data from the Tickets → Get All function.

It works fine for up to 100 items, however once you set it to “return all” it fails with the below error:

ERROR: Your request is invalid or could not be processed by the service

expanding the error shows the below:

"message": "422 - {"error":"invalid","description":"Invalid search: Requested response size was greater than Search Response Limits"}",
"name": "Error",
"stack": "Error: Request failed with status code 422 at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15) at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:269:11) at IncomingMessage.emit (node:events:538:35) at endReadableNT (node:internal/streams/readable:1345:12) at processTicksAndRejections (node:internal/process/task_queues:83:21)"

The other functions such as getting users and organizations can go far in excess of 100 (ive copied out over 50K users)

Also, something else that might be of interest, Zendesk API supports sideloading of queries, to reduce API calls - see: Side-Loading | Zendesk Developer Docs

  • n8n version:0.170.0
  • Running n8n via Docker (have also tested on desktop app)


Hey @ubtams,

Welcome to the community :cake:

I have just given this a go here and I was able to get 900+ tickets using Get All with no issue, Do you have any properties set or is it just a Ticket > Get All with nothing else?

The include option is an interesting one and something that could be worth looking into in the future to remove extra nodes from workflows.

Hi @jon , Thanks!

As below:


Hey @ubtams,

I have just taken a look at Zendesks API docs and it looks like it is a limitation (“feature”) of Zendesk, They recommend for over 1000 items the export API is used instead which we don’t have an operation for yet.

Thanks @jon , i wondered if it might be this, but thought maybe n8n did have an operation for it as i was able to export so many users and orgs.

Thats cool, for now ill just use a direct query to the export (aka incremental) endpoint

Thanks again!

1 Like

Oddly enough Users and Orgs don’t have the same limitation, I suspect the reason behind it is there is more data in tickets than users and orgs.