<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
0D51Y00008vfCm7SAEOkta Identity EngineWorkflowsAnswered2026-03-11T09:02:04.000Z2020-07-16T19:44:59.000Z2021-08-23T02:03:53.000Z
  • 2u0la (2u0la)

    This could probably be achieved by:

     

    1. Creating a separate child Flow that takes a URL and an object/list as inputs.
    2. Use the Custom API Action card, you can then call this Flow recursively by encapsulating it in an if/else condition (check response headers for the rel=next link).
    3. If rel=next, you know there is more data, so append the user data to your object/list, extract the URL and call your function again.
    4. Once there is no rel=next link, you have got all of the results, so you can return the object to your original Flow via the "Else" block of the if/else card.
    Expand Post
    • 1fj3q (1fj3q)

      It worked for me. Just an FYI, if someone is trying to implement the same and return the collated data after recursive flow then make sure the parameter name of the recursive flow match with the variable name used to pass the list.

  • Hi Sandeep,

    It would be awesome if you could share your flow (Pagination) with the community ? 😃

    Even a screenshot would be great !

  • 1fj3q (1fj3q)

    Here's the recursive child flow. This is always scope to optimize this further. Hope will helps.

    Image is not available

    Expand Post
    • WilliamH.77860 (Arctic Wolf Networks)

      I am a little late to this party. As Stephane mentioned, the image is quite small and I am not able to make out the steps. I have not built a recursive workflow yet, so I was looking for a bit of help here.

       

      I tried to access the flopack Stephane linked to, but it looks like Okta has a known issue with exporting/importing recursive workflows. I appreciate any help.

      Expand Post
  • WilliamH.77860 (Arctic Wolf Networks)

    I have managed to get the recursive workflow running, but for some reason the parent workflow isn't getting the final, union list. It's getting the first list. If I look at the recursive history, there's only one return and that is when there is no next url. It shows the list that should be returned, but that's not the list that shows in the parent workflow.

  • Hi William,

    On our side we have revamped a bit recursive flow provided by Okta and now we are using it with a bunch of specific API calls (Mappings, Network zones, etc.) .

    I uploaded it. Give it a try and any feedback would be appreciated

    • WilliamH.77860 (Arctic Wolf Networks)

      My apologies for the long delay. Thank you for the file. I have imported it and will run though it!

  • 6wnkd (6wnkd)

    Hello I'm facing the same issue, I would like to DELETE, Deprovisoned accounts that have not logged-in in the last 366 days. Preventing the API stop at 200 hits, I was looking also for pagination in the Workflow (or a mother solution to go through all the account on a daily basis with e scheduled workflow) I'm already halfway, but the pagination I'm not able to get it to work for me. The workflow from Sandeep is too small and the Attached file from Stephan I'm unable to import in the Okta Workflow control.

    Expand Post
10 of 11
This question is closed.
Loading
Is it possible to create a while loop structure for pagination through workflows?