---
title: "Recursive Flow Connector"
slug: "recursive-flow-connector"
description: "Use the Recursive Flow connector in Lansweeper Flow Builder to let a workflow call itself with a cursor and process large amounts of data in serial."
updated: 2026-07-17T15:46:55Z
published: 2026-06-12T15:07:57Z
canonical: "docs.lansweeper.com/recursive-flow-connector"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lansweeper.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Recursive Flow Connector

Note on third‑party tools

              

We aim to provide accurate and helpful details about third‑party tools, but we can’t guarantee that this information is always complete or up to date. If you notice any discrepancies, feel free to share them in the feedback section below. For the most reliable information, please always refer to the third‑party tool’s official documentation.

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

## Triggers

### Recursive Trigger

Accept a request from an 'Invoke Recursive Trigger' step

| Input | Comments | Default |
| --- | --- | --- |
| Run on Deploy? | Run this flow automatically when an instance is deployed. | false |
| Default Cursor Value | The default value to return as a cursor if no cursor was supplied in a trigger payload. For example, you could set this to '1970-01-01T00:00:00Z' (Unix Epoch) if your cursor is a creation timestamp, or '0' if your cursor is a page number. |  |

## Actions

### 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

| Input | Comments | Default |
| --- | --- | --- |
| Cursor | The programmatic cursor to set for the next loop iteration or recursive trigger invocation. |  |