Using templates
Click a template to copy it, or drag it onto the canvas to reuse it. Both start from the Templates card in the editor's node panel.


Click a template
Clicking a template opens the Import Workflow dialog:
| Option | What it does |
|---|---|
| Create New Workflow | Saves the template as a new workflow and opens it. Recommended. |
| Replace Current Workflow | Replaces the workflow you have open with the template. This cannot be undone. |
| Merge into Current | Adds all of the template's nodes to the workflow you have open. |
Drag a template onto the canvas
Dragging a template onto the canvas asks "How would you like to add this workflow?":
| Option | What it does |
|---|---|
| Use as Sub-Workflow | Adds a Sub-Workflow node that runs the template and returns its output. A prebuilt template is first copied into your workspace as its own workflow. |
| Inline Contents | Copies all of the template's nodes into this workflow. |
| Replace Contents | Overwrites the current canvas with the template. |
| Create New Workflow | Builds a new workflow alongside this one from the template. |
A sub-workflow stays linked: changes to the called workflow reach every workflow that calls it. The other options make an independent copy. See Sub-workflows.
Duplicate a workflow
- On the Workflows page, open the workflow card's ⋯ menu.
- Choose Duplicate.
Inside the editor, right-click the canvas and choose Duplicate. Flero creates the copy and opens it.


After you copy a template
- Open each node and check its configuration.
- Bind your own credentials on every connector and AI node. See Managing credentials.
- Set any workspace variables the workflow reads (
{{ $env.NAME }}). An unset variable fails the node before it runs. See Workspaces. - Test a run, ideally in sandbox mode.
- Activate the workflow when you are ready. See Versions and activation.
Tips & gotchas
- Expressions use node names.
{{ $node["Get Customer"].output.email }}looks up the node called "Get Customer". If you rename a node, update the expressions that point to it. - Webhook paths are shared across the instance. A copy keeps the original webhook path. Give the copy its own path before you activate both.
- Merging can create duplicate names. After Merge into Current or Inline Contents, check that node names are still unique, so expressions point to the right node.
Related
Found something out of date? This page lives in the Flero docs content set.