Skip to content

Reusing your own workflows

Every workflow you save is already a template for your workspace. It appears under User Workflows in the editor's Templates card. There is no separate "save as template" step, and no way yet to publish a template outside your workspace.

Your workflows in the Templates card

Open any workflow and expand the Templates card in the node panel. Every other workflow in your current workspace is listed under User Workflows. Click or drag one to reuse it, as described in Using templates.

Workflows from other workspaces are not listed. To reuse a workflow in another workspace, export it and import it there.

Ways to reuse a workflow

Goal How
A one-off copy in the same workspace Duplicate from the workflow card's ⋯ menu
A copy in another workspace or instance Export JSON, then Import in the other workspace. See Import and export.
A shared building block that several workflows call Drag it onto the canvas and choose Use as Sub-Workflow, or add a Sub-Workflow node
Turn part of a workflow into a building block Select the nodes, right-click the canvas and choose Convert selection to sub-workflow

A copy is a fork: later changes to the original do not reach it. A sub-workflow is a link: changes to the called workflow reach every caller.

Convert a selection to a sub-workflow

  1. Select the nodes you want to move.
  2. Right-click the canvas and choose Convert selection to sub-workflow.
  3. Enter a Sub-workflow name.
  4. Review the Inputs (data the moved nodes read from this workflow) and Outputs.
  5. Click Convert.

Flero moves the nodes into a new workflow and replaces them with a Sub-Workflow node that runs it. The current workflow is saved when you convert.

The Convert to sub-workflow dialog with Invoice reading entered as the sub-workflow name, and the Inputs and Outputs sections listing the data that crosses into and out of the new workflow.The Convert to sub-workflow dialog with Invoice reading entered as the sub-workflow name, and the Inputs and Outputs sections listing the data that crosses into and out of the new workflow.

Tips & gotchas

  • Keep reusable workflows tidy. Clear names and sticky notes help the next person who copies them.
  • Don't hard-code secrets. Put keys in credentials and environment-specific values in workspace variables, so copies work without edits.
  • Exports leave secrets out. Credentials are stored separately, so whoever imports the file binds their own.

Found something out of date? This page lives in the Flero docs content set.