Potential bug in the HTTP Request Node when using pagination

Questions
1

Describe the problem/error/question

When using the HTTP Request node to make API calls to the Slack Web API to get a list of users, the request fails with an “invalid_auth” error when adding the pagination. Without the pagination the request is works as expected.

I believe something is going wrong with the authentication on subsequent requests. My first guess would be that the API key, which is passed in through Bearer authentication is not being properly set on subsequent requests.

Here’s the node setup:

image
image657×349 6.17 KB

Here’s the pagination specific setup:

image
image647×824 36.8 KB

Note: these are all green when I first setup the node and make the first request without pagination. But as soon as I add the pagination logic, and fire the request I get the error output you see below.

What is the error message (if any)?

The output of the node changes from the list of users to this:

image
image226×143 3.45 KB

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.98.2
  • Database (default: SQLite): :person_shrugging:
  • n8n EXECUTIONS_PROCESS setting (default: own, main): N/A
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: N/A