Currently, it seems to be impossible to query a notion API resource in a workflow setting "start_cursor" parameter in the body JSON. This blocks the ability to treat pagination as it should.
It's only possible to set the "filter" body JSON parameter.
As a workaround, I'm using a generic HTTP Request Resource, which removes all the fun of having provider out-of-the-box integrations.
It would be nice to have the option of customizing this kind of fields.
Hi @airton_incognia Thanks for reaching out! 
I see what you mean. Unfortunately, I'd also recommend using our generic REST api integration instead of the notion integration as a workaround. I'll reach back out when our team ships a fix for this bug
This is still an issue.
Trying to get all Notion users in my company fails and I have to resort to calling via 2 separate API requests since I can't conditionally add a query parameter based on whether I have a cursor already or not, and Notion returns a 400 if start_cursor=null.
Please fix this
+1. It would be cool if this worked
This still doesn’t work, we still have to use a workaround. And this thread doesn’t even provide an example of the workaround. Our team is exploring alternative solutions with different platforms and they work out of the box with the newer API… The fact we can’t simply paginate with next_cursor (very common pattern) undercuts the value of having pre-configured API options.
This can be built with any coding agent in less than 4 minutes…
Hi @n8descript,
Our apologies, it looks like the engineers noted that this issue may have been caused by Notion not adhering to the OpenAPI which we have our resource connected to, so as to ensure that endpoint updates are automatically added on our end.
This ticket seems to have gotten lost in a re-org but I re-opened it and added your +1 to the ticket.