Next URL Error with Parameters

The API I’m using includes all the query parameters in the “nextLink” value so it seems that the parameters are getting doubled up when moving to the next page in the pagination. Here is a screenshot showing it. It doesn’t matter if I use the key/value or JSON for the parameters. Any thoughts/help as I’ve tried about everything I can think of.

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

Welcome to the community @iobinary !

Tip for sharing information

Pasting your n8n workflow


Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.

```
<your workflow>
```

That implies to any JSON output you would like to share with us.

Make sure that you have removed any sensitive information from your workflow and include dummy or pinned data with it!


If you remove the query parameter will pagination work fine or you cannot test it like that without the initial querystring?

If the query parameter is removed then all works as expected, but the initial returned nextLink wouldn’t have the parameter either and I get data that isn’t wanted/needed and in this case it’s a scenario of needing about 20 fields from about 700 in a full response. The $top parameter was just the simplest one for the example of the issue.

Also, thanks for the welcome!

Think I may have found a solution using a regex on the returned nextLink to remove the parameters so that the ones from the node settings can be used. Hopefully further testing proves this true.

Hey @iobinary , thanks for checking this.

Could you also give an example of nextLink value before you apply the fix? Additinally, what version of n8n do you use?