Workflow Templates

Workflow templates let you turn an existing workflow into a reusable blueprint. Save a workflow once, and anyone in your organization can create new workflows from it with a single click.

FlowTrux ships with 15 curated System templates (email triage, lead scoring, weekly reports, etc.). On top of those, your organization can save its own Private templates - same UI, same plan-aware gallery.

Template sources

Each template belongs to one of three sources. In the gallery, filter chips (All / System / My org) narrow the list:

Your own templates show a small emerald Your org badge on the card, so you can tell them apart from curated ones at a glance.

Saving a workflow as a template

1. Open the Workflows list in the sidebar.
2. Click the … menu on any workflow you have edit access to.
3. Choose Save as template.
4. Fill in the dialog:
   • Name - short, descriptive (3–100 chars)
   • Description - what does it do, when to use it (10–1000 chars)
   • Category - pick one of the 14 categories (Customer Support, Sales & Marketing, DevOps, etc.)
   • Tags - up to 10 free-form tags (optional)
5. Click Save template.

What happens under the hood

• A snapshot of the workflow's nodes and edges is stored as a new template.
• Required MCP servers, AI providers, and models are auto-detected from the nodes and attached to the template - so when someone uses it, they see upfront what needs to be configured.
• The original workflow stays independent. Editing the original later doesn't change the template, and vice versa.
• The template starts with visibility Private (org-only) and status Published - it's immediately usable by teammates.

Who can save? Any user with canEdit permission on their current workspace. That's OWNER, ADMIN, and MEMBERs whose workspace grants canEdit.

Using a template

1. Click + (Create Workflow) in the sidebar, or use the Templates tab in the create dialog.
2. Browse or search the gallery. Filter by source or category.
3. Click Preview to inspect nodes, or Use to create a new workflow from the template.
4. The new workflow is a copy - change anything you want; the source template stays intact.

Every time a template is used, its internal usageCount is incremented. This is surfaced in Settings → Templates so you can see which of your templates are actually popular.

Managing your org's templates

Settings → Templates lists every template your organization owns. From there, OWNER/ADMIN can:

• Edit metadata - change name, description, category, tags, long description. Workflow structure (nodes/edges) is frozen at creation and can't be changed here; if the underlying workflow evolves, save it as a new template.
• Delete - removes the template from the gallery. Workflows already created from it keep working - they're independent copies, not references.

Plan limits

The number of templates an organization can save is capped by its subscription plan:

System templates don't count against your limit. You can see current usage in Settings → Usage (Templates bar), and when you hit the cap the Save dialog shows an Upgrade action that takes you straight to Billing.

Good patterns for templates

Templates shine when you have:

• A workflow shape you run repeatedly with small variations (invoice processing, lead scoring, weekly reports)
• Onboarding flows for new team members - turn your best workflows into a library
• "Standard ways to do X" in your org (e.g., how to escalate a support ticket)

Don't turn into a template:

• Highly customized one-off workflows with hard-coded secrets or personal configs
• Half-finished drafts - save them as regular workflows first, template once stable

Related

• Workflows overview
• AI Workflow Builder - alternative way to bootstrap new workflows via natural language