Skip to content
Approval (Legacy) logoSub Flows logo

Connect Approval (Legacy) to Sub Flows

Move data between Approval (Legacy) and Sub Flows the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Approval (Legacy) triggers
0
Approval (Legacy) actions
2
Sub Flows triggers
1
Sub Flows actions
3

Automation ideas

What you can build with Approval (Legacy) and Sub Flows

A few flows teams run between Approval (Legacy) and Sub Flows. Use one as a starting point, or build your own from scratch.

  • Callable Flow in Sub Flows creates Wait for Approval in Approval (Legacy)

    Waiting to be triggered from another flow

  • Callable Flow in Sub Flows creates Create Approval Links in Approval (Legacy)

    Waiting to be triggered from another flow

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Approval (Legacy) and acts in Sub Flows, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.