Fix nested n8n pagination before building a manual loop

If you are using n8n’s HTTP Request node to fetch records from a POST API, a nested page number can turn a small configuration task into an unnecessary workflow redesign. You put page.current in the p