2 Pagination logics on http node zoho CRM custom module

Questions
, ,
1

Describe the problem/error/question

i am using the http node to get records from a custom module in Zoho CRM
In Zoho API there are two separated logics of pagination :

  1. normal pagination where is used the page parameter
  2. after 2000 records you need to use another pagination parameter called “page_token”
    The problem is that Zoho does not allow to send them both on the request , so i need to create a request the run with the normal pagination for 10 pages , and then send the next_page_token on the 11’s request

Had anyone managed to do something similar in N2N ?

Please share your workflow

Information on your n8n setup

  • n8n version:
    Cloud
  • **Running n8n via cloud **
2

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:
3

Hello @idan_cohen
I think its possible to split the task into two http nodes:
First http node will collect results for the first 10 pages (until the next_page_token appears)
Then you need a aggregate node to combine results into one item (so the next http node won’t be execute for each of the first one result) and next http node that will start to fetch data from this next_page_token untill the end

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.