Notion "Get Many" node ignoring limit parameter - returns 100 items instead of 1

[abhiman]

Hey everyone,

I’m running into a really frustrating issue with the Notion “Get Many Database Page” node and I’m honestly stumped at this point.

The setup:

• I have “Return All” turned OFF

• Limit is explicitly set to 1

• I have filters configured (the filter itself is unique)

• The limit is set to 1 at the top of the node configuration

The problem: Instead of returning 1 item like it should, it’s returning exactly 100 items - which is Notion’s default pagination limit. It’s completely ignoring my limit setting.

The weird part: This doesn’t happen on every execution! Out of about 19k total executions across 2 workflows, only specific runs in each workflow are doing this. Most of the time it works perfectly fine, but when it does break, it returns those 100 items and completely breaks everything for my client’s project.

I’ve attached screenshots showing my configuration. Has anyone else experienced this? Is this a known bug with the Notion node, or am I missing something obvious here?

Any help would be massively appreciated - this is causing real issues in production and I can’t figure out why it’s inconsistent.

Thanks in advance!

[mohamed3nan]

Hi @abhiman, welcome!

@abhiman

The weird part: This doesn’t happen on every execution! Out of about 19k total executions across 2 workflows, only specific runs in each workflow are doing this. Most of the time it works perfectly fine, but when it does break, it returns those 100 items and completely breaks everything for my client’s project.

It also works on my end, I can’t reproduce the issue.

However, AFAIK n8n is using an old Notion-Version, and according to notion docs, there is a newer version available,

After spending some time looking into this, I discovered that the built-in Notion node “Get Many Database Pages” is using a deprecated endpoint to send the query, even though it still works, it shouldn’t be relied on long-term:

There is a new endpoint for making queries:

So IMO, I’d try this using an HTTP Request node and create the request body with the filters you need,

Here’s where you can start with this:

[abhiman]

@mohamed3nan

on-Version

Hey! Thanks so much for taking the time to look into this and test it out - really appreciate it!

Yeah, you’re absolutely right that it’s hard to reproduce. Even on my end, when I get those 100 items and then just re-execute the exact same workflow, it gives me 1 item as expected. It’s so bizarre and inconsistent, which makes it even more frustrating to debug.

Thanks for sharing the JSON example too - that’s super helpful to have as a reference!

Quick question though: I’m using quite a few other Notion nodes in my workflows (create, update, etc.). Do you recommend switching all of them to HTTP requests as well? I can definitely do it, but I’m a bit concerned about the field mapping situation. For the update and create nodes, I’m using the built-in field mapping feature, and there are like 20-25 fields I’m mapping in each. If I switch to HTTP, that’s going to be a bit of a nightmare to recreate manually.

Just want to know if you think it’s worth doing for all the nodes, or if I should maybe just switch the “Get Many” node and keep the others as-is?

Thanks again for your help on this!

[mohamed3nan]

@abhiman

If I switch to HTTP, that’s going to be a bit of a nightmare to recreate manually.

Just want to know if you think it’s worth doing for all the nodes, or if I should maybe just switch the “Get Many” node and keep the others as-is?

I’d just switch the node where you’re getting the unexpected behavior only for now,
because, it’s still only an assumption that the issue is caused by using a deprecated endpoint, especially since it’s still working and supported..

And like you said, converting everything to HTTP requests would really be a nightmare..