Logic

Run another flow

Run another flow hands the items that reach it to one of your other flows, once with all of them or once per item like a loop, and can carry on with what comes out of that flow. Build a step once (checking, scoring, a site report) and use it from many flows. The other flow takes the items in through a From another flow start: when it has none, one click in this block’s settings, Let it take items from other flows, adds it. Each of its runs is a run of its own.

In the editor: Runs one of your other flows with the items that reach this block, once with all of them or once for each (a loop), and can carry on with what that flow found. The other flow takes the items in through a From another flow start (one click here adds it when it has none). It runs as its own run, with its own credits.

Settings

Flow to run

A setting

The flow to run. It takes the items in through a From another flow start; if it has none, the button under the list adds one, linked to its first step.

A flow in your organization that you can see. It cannot be this flow.

Needed before the flow can run.

Run it

Pick one

Once with every item, or one run for each item.

One run, with every item that reaches this block.

  • Once, with all the items
  • Once per item

Then

Pick one

Whether to carry on with what the other flow found, or with the items as they were.

What reaches the end of that flow comes back here and goes on to the next block.

  • Use its results
  • Just start it

What comes out

Each item that leaves the block carries these fields, to use in the blocks after it as {{field}}.

Then: Use its results

What reached the end of the other flow comes back and goes on to the next block (from each of its runs, when run once per item).

  • every field: As the other flow left them: for a scoring flow, the places with their fit_score and reason.
  • fit_score: For example, added by an xMap LLM block in the other flow.

Then: Just start it

The items go on exactly as they came; the other flow runs on its own.

  • every field: Unchanged.

How to use it

Sales

One scoring flow for every city

A sales team has a flow per city and wants them all to score places the same way, with one set of AI instructions to keep up to date.

Before: Three flows had three copies of the scoring blocks, and they drifted apart.

With the flow: The Singapore, Kuala Lumpur and Bangkok flows run one scoring flow; a change to it reaches all three.

Retail

A site report for each new store

An expansion team keeps a site report flow (competitors, weather, a satellite picture) and runs it for every new store added to its table.

Once per item runs the other flow for each store, up to 25 a run, and each run gets that one store.

Logistics

Start a follow-up flow, then carry on

A courier company starts its customer notice flow for each batch of closures, and keeps going with its own route update.

Just start it: the other flow runs on its own and the items go on unchanged.

Marketing agencies

One enrichment flow for every client

An agency runs a flow per client; each sends its places to one shared enrichment flow (place details, then a category clean-up).

Banking and payments

The same checks before every CRM

The checks live in one flow that every lead source runs, so no source skips them.

Government and cities

Each district runs its own follow-up

A city team sends each district’s new incidents to that district’s follow-up flow, owned by the district team.

Good to know

  • Only real runs run other flows. A test run says what a real run would do, for example Would run the other flow once with 12 items.
  • Once per item runs the other flow up to 25 times a run, each with one item. A long list carries on in parts if the run needs more time.
  • The other flow must be in your organization; a private flow only when it has the same owner as this one. A flow cannot run itself, and flows can run flows 3 levels deep.
  • The person running this flow must be allowed to run the other one, with its own connections.
  • A flow with a Wait or an Approval block cannot be run by another flow: it would wait with nothing to carry its results back.
  • Each run of the other flow is its own run, in its own history, linked from this run’s step. It uses its own credits, which count toward this run’s limits; a failed run there sends no failure email of its own.
  • If every run of the other flow fails, this step fails too; if only some fail, the step says how many.
  • To connect two flows: add Run another flow to the one that finds things and pick the other. If the other flow has no way in, press Let it take items from other flows. Or, in the other flow, open the ... menu and pick Start from another flow.
  • A From another flow start has no public address: only flows of your organization can hand it items.
  • Run another flow itself is free.

Works well with

  • Webhook / API: Starts the flow when another system sends a POST request with a JSON body to this flow’s webhook URL.
  • xMap LLM: Tell the AI what to do in plain words.
  • Branch: Splits items in two.
  • New rows: Starts the flow when new rows appear in a Google Sheet or in a table in My data.
  • Only new: Lets through only the items this flow has not found before, so a daily flow sends only what is new.
  • Email: Sends one email per run with all the items, or one email per item.
  • Filter: Keeps only the items that match a rule.
  • My data: Brings in a table you uploaded or a list you saved on the My data page: your stores, customers, target accounts or sites.

Stories with it

Help articles

Try it

Build a flow with Run another flow on the home page, no account needed, or book a call. Try it live