<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009Jb1CrCAJOkta Identity EngineWorkflowsAnswered2024-04-15T10:19:24.000Z2023-06-14T16:53:02.000Z2023-06-15T11:18:09.000Z

8422m (8422m) asked a question.

Recursive workflow taking into account pagination

I am trying to set up a recursive child flow that calls an API to run through thousands of lines of users info. The max request limit is set to 500, but I get a nextPageToken. How would I set up the child flow to then include the newly generated nextPageToken everytime it runs until the nextPageToken field is blank?


  • DonF.81354 (Customer)

    Hi! Yes, from what I understand this is indeed possible, and I use it pretty frequently when accessing the Okta API using Python or something similar. As for Workflows, this process would obviously be a bit different, but I found the below link to be quite useful for your use case.. please read it over and let me know if this helped or at least got you a little bit closer. If not, I am happy to work with you to get closer to a solution that will work for you - thanks!!

     

    Functions in Workflows, specifically, Paginate: API Endpoint

     

     

     

    Expand Post
  • NiallM.34104 (Atlas Identity)

    Don's link is excellent and I used it as a basis for supporting pagination. Note, there is no standard for pagination in APIs so you will need to support multiple patterns are you connect to different APIs that provide pagination support.

This question is closed.
Loading
Recursive workflow taking into account pagination