Skip to content
Docs
flero.ai

Saving your own templates

Reuse a working workflow as a template, keep it private to your workspace, share with your org, or publish to the public marketplace.

Save as template

From the workflow editor:

  1. Open the workflow you want to templatise.
  2. Workflow settings (gear icon) → Save as template.
  3. Fill in:
    • Template name.
    • Description, what it does and when to use it. Markdown supported.
    • Difficulty, Beginner / Intermediate / Advanced.
    • Categories, one or more.
    • Tags, free-form.
    • Visibility, Private (workspace), Organization, Public marketplace.
  4. Flero scans the workflow and lists credentials and connector references that will need to be re-bound on clone. For each, choose:
    • Bound at clone time (user picks during cloning), default.
    • Workflow variable (cloner sets a workflow-level variable instead).
  5. Optionally redact sensitive defaults, Flero highlights any field that contains a literal value matching a "looks like a secret" pattern; clear them out.
  6. Save.

The template is now visible in /templates filtered to your scope.

Visibility levels

Level Who sees it
Private Just your workspace
Organization Every workspace in your organization
Public marketplace Everyone, via the Marketplace

Public marketplace submissions go through a brief review for safety and quality before appearing.

Versioning

Each Save as template creates a new version. Cloners get the latest version by default; advanced users can pin to an earlier version.

To publish a new version:

  1. Open the source workflow (the one the template was created from).
  2. Make your changes; save.
  3. Workflow settings → Templates → Publish update.
  4. Fill in changelog notes.

Existing clones are unaffected, they were forked at clone time.

Submitting to the public marketplace

If you toggle Public marketplace at save time, your template goes into a review queue:

  • Automated checks for known issues (placeholder secrets, broken references).
  • Manual review for quality and category fit (typically 1–3 business days).
  • Approval / rejection with feedback.

Once approved, the template appears in the marketplace, with you as the listed author. You can update or unpublish at any time.

Reusable templates inside workflows

For internal reuse rather than external sharing, prefer the Sub-Workflow pattern:

  1. Build the reusable piece as its own workflow.
  2. In parent workflows, drag the Sub-Workflow node and reference the reusable workflow.
  3. Updates to the reusable workflow propagate to every parent (unless they've pinned a version).

Templates are for forking (one-shot clone), sub-workflows are for referencing (live link).

Tips & gotchas

  • Redact aggressively. A leaked token in a public template is a real problem. Flero's pattern-matching catches common shapes but not all, eyeball each node before publishing.
  • Document required scopes / permissions. Templates that need elevated OAuth scopes in the external service should say so in the description.
  • Test the clone path. Clone your own template into a new workspace and walk through the setup. Catch sharp edges before users do.
  • Internal templates with workspace-specific URLs (a webhook target, an internal API host) need to be parameterised, make them workflow variables in the template, not hardcoded.

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