Get the current value of the recursive trigger cursor

Invoke the current flow with the current cursor

Set the value of the recursive cursor for the next loop iteration or recursive trigger invocation

This component allows a flow to call itself with a cursor in order to process large amounts of data in serial.

The recursive flow component allows a flow to recursively call itself.
It is particularly useful if you have a long-running workflow that needs to process logs of records.

A `cursor` is passed between executions to track what data has been processed, and what data is left to process.

For example, suppose you have 100,000 records in a third-party app to process.
You know from experience that you can fetch 100 records at a time, and that each page of records takes about 5 seconds to fetch and process.
Processing all of the data would take 5 seconds x 1000 pages (or about 83 minutes).

An execution can run for a [maximum of 15 minutes](../integrations/integration-runner-environment-limits.mdx#execution-time-limitations), so you won't be able to process all pages in a single execution.
Instead, you can process a hand-full of pages in one execution, and then invoke another execution with a cursor indicating where you left off.

In the 100,000 records / 5 seconds per page example, you could build your to flow process, say, 10 pages per execution.
After 10 pages (or about 50 seconds; well under the 15-minute limit), it could call itself with a cursor of `11`.
The next execution would process pages 11 through 20, and send itself a cursor of `21`.
This could continue until you detect that there are no more records to process.

A general flow that processes large sets of records from a paginated API in serial using the recursive flow trigger would look something like this:

<div style={{textAlign: "center", width: "100%"}}>

```mermaid
flowchart TD
    trigger(["Recursive Trigger"])
    callSelf(["Call self with latest cursor"])
    subgraph loop["Loop 10 Times"]
        getCursor(["Get current cursor"])
        fetchData(["Fetch a page of records using the current cursor"])

        checkRecords@{ shape: hex, label: "Check if result was empty" }
        stop@{shape: dbl-circ, label: "Stop"}
        processData(["Process page of records"])
        saveCursor(["Save cursor for next iteration"])

        getCursor-->fetchData
        fetchData-->checkRecords
        checkRecords-->|Empty|stop
        checkRecords-->|Not empty|processData
        processData-->saveCursor
        saveCursor-->getCursor
    end

    trigger-->loop
    loop-->callSelf
```

</div>


Accept a request from an 'Invoke Recursive Trigger' step

When invoked manually or via webhook without a cursor value, the recursive trigger begins an execution using the **Default Cursor** input as its current cursor value.
If the API you're integrating with uses page numbers, you can set the default cursor value to `0`.
If you're using timestamps, Unix Epoch (`1970-01-01T00:00:00Z`) could work for an initial cursor.

When invoked by an [Invoke Recursive Trigger](#invoke-recursive-trigger) action, a cursor is passed to this trigger via POST request and is used for the current execution.


Recursive Flow Component

Integrate with customers’ other SaaS apps, fast

About the Recursive Flow Component

Actions

Triggers

Ready to get started?

Action Name	Action Description
Get Recursive Cursor	Get the current value of the recursive trigger cursor
Invoke Recursive Trigger	Invoke the current flow with the current cursor
Set Recursive Cursor	Set the value of the recursive cursor for the next loop iteration or recursive trigger invocation