# Tip: HTTP Request node pagination without a loop

**URL:** <https://community.n8n.io/t/tip-http-request-node-pagination-without-a-loop/321829>\
**Category:** Docs & Tutorials\
**Created:** [October 16, 2026, 10:40am UTC](https://community.n8n.io/t/tip-http-request-node-pagination-without-a-loop/321829 "2026-10-16T10:40:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![stackshortlist](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/stackshortlist/32/195183_2.png) [@stackshortlist](https://community.n8n.io/u/stackshortlist)\
**Post date:** [October 16, 2026, 10:40am UTC](https://community.n8n.io/t/tip-http-request-node-pagination-without-a-loop/321829/1 "2026-10-16T10:40:46Z")

</div>

If your API returns a cursor, you can skip the manual loop and use the built in Pagination option on the HTTP Request node. Under Options add Pagination, pick Update a Parameter in Each Request, set the query parameter name to cursor and the value to {{ $response.body.next\_cursor }}. Then set Pagination Complete When to Other and use a condition like {{ !$response.body.next\_cursor }} so it stops on the last page. Adding a small interval between requests also keeps rate limits happy.