Stop Losing API Data in n8n (Pagination Explained with 2 Examples)

This video explains how to handle pagination in n8n workflows using the HTTP Request node. It demonstrates two public APIs (PokéAPI and Rick and Morty), shows techniques to retrieve full or partial datasets, avoid rate limits, and parse/clean results. The presenter walks through built-in pagination options, limit/offset parameters, stopping conditions, and practical node sequences to transform paginated responses into usable arrays.

– Pagination basics: why APIs split large datasets into pages, where to find next/previous links or tokens, and how count/limit/offset affect results.
– n8n implementation: configuring the HTTP Request node’s pagination mode, using expression-based response paths (e.g. response.body.next or info.next), and setting intervals/max pages to avoid rate limits.
– Data parsing: practical node chain (Edit Fields → Split Out) to extract desired fields and convert paginated JSON into clean rows without custom code.
– Examples covered: ~10 concrete cases demonstrating changing page size, starting offsets, stopping conditions, and sampling results for large data sets.

Quotes:

Pagination splits a large data set into smaller chunks returned across multiple API requests.

Throw away your calculator, as one of my professors said in college.

All you need is: how do you get from page to page and how do you know when the results stop?