HTTP Pagination with POST Request Body Parameters - $pageCount not incrementing when in array

[spooner85]

Describe the problem/error/question

Using the HTTP Request Node Pagination with POST Body Parameters in an array like here not working:

{
"Ticket": "{{ $('Login Ticket').item.json.Ticket }}",
"TrimResponse": 0,
"Data": {
"CustomerId": 10162,
"SearchValue": "",
"EntriesPerPage": 5,
"Page": 1
}
}

This is the way i try to update the page by body-parameter:
Data.Page
{{ $pageCount + 1 }}

What is the error message (if any)?

The returned response was identical 5x, so requests got stopped
Check if "Pagination Completed When" has been configured correctly.

Please share your workflow/screenshots/recording

Share the output returned by the last node

The returned response was identical 5x, so requests got stopped
Check if "Pagination Completed When" has been configured correctly.

Debug info

core

• n8nVersion: 1.122.5
• platform: docker (self-hosted)
• nodeJsVersion: 22.21.0
• nodeEnv: production
• database: postgres
• executionMode: regular
• concurrency: -1
• license: enterprise (production)

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/142.0.0.0 safari/537.36 edg/142.0.0.0
• isTouchDevice: true

Generated at: 2025-12-06T22:22:48.696Z}

[n8n-assistant]

Hey @spooner85,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-5807".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-5807

[spooner85]

Have you checked the issue?

[sohamingle]

I was able to reproduce this.

When using JSON body pagination with a nested structure (e.g. { Data: { page: 1 } }) and setting the pagination parameter name to Data.page, n8n sends a request body containing both the original object and a new top-level "Data.page" key instead of updating the nested value.

requestData = { 
    'Data': {
      'page': '1'
      }, 
    'Data.page': '1'
  }

This causes the backend to send values for the same page which leads to this error:

The returned response was identical 5x, so requests got stopped
Check if "Pagination Completed When" has been configured correctly.

It’s not clear whether dot-notation for body pagination parameters is intended to be supported or not. Clarification on expected behavior would help determine whether this should be fixed or documented as unsupported.

[n8n-assistant]

Hi @spooner85 👋

Thanks so much for your patience while we’ve been improving n8n. We know it’s taken some time to review this issue, and we’re currently updating our triage process to better keep up with our growth.

There have been a lot of improvements in recent releases, so we’d really appreciate it if you could check whether this issue still occurs in the latest release.

When you have a moment, please copy and paste the checklist below as a comment so our system can update the status automatically:

[ ] I have updated to the latest stable version of n8n [please specify version number] and I am still experiencing this issue
[ ] Please close this issue – I am no longer experiencing it
[ ] Please close this issue – [please specify a reason]

If we don’t hear from you in the next 14 days this issue will be automatically closed, feel free to reopen - don’t forget to add the checklist above so that our automated systems notify us of the issue.

Thanks again for helping us keep n8n healthy and up-to-date 💚

[n8n-assistant]

As we haven’t heard back from you, we’re going to close this issue to keep things organized. But don’t worry, if you have more information or need further assistance, you’re welcome to reopen the issue anytime or create a new one. We’re always happy to help!

Thanks for reaching out and have a great day! If this was closed by mistake and you have been waiting for us let me know and I can also re-open it.