Workflow Templates

Workflow templates are reusable blueprints. Start a new workflow from one with a single click - or turn a workflow you built into a template that anyone in your organization can reuse.

FlowTrux ships with 35 curated System templates: general-purpose automations (email triage, lead scoring, weekly reports, document processing, …), a large fleet management / telematics collection built around Wialon (20 templates - geofence alerts, daily trip logs, fuel reports, silent-unit detection, …), and a couple of demo workflows used for onboarding. On top of those, your organization can save its own private templates - same gallery, same flow.

Where to find them

Click Create workflow in the sidebar. The Create Workflow dialog offers three starting points:

• Blank - start from an empty canvas. Build it yourself or describe what you want to the AI assistant.
• Templates - browse the template gallery (described below).
• From file - import a workflow you previously exported as JSON.

The gallery is also one click away from an empty canvas (Browse Templates).

The gallery

• Source filter - chips All / System / My org separate curated templates from your organization's own. Your templates carry a Your org badge on the card.
• Category filter - 15 categories (Customer Support, Sales & Marketing, Reports & Analytics, DevOps & Monitoring, Fleet Management, …) narrow the list.
• Search - free-text search across names and descriptions.
• Preview opens a read-only look at the template's nodes and lists its Requirements (MCP servers, AI providers) so you know upfront what needs to be configured; Use template creates your copy.

Using a template

When you click Use template:

1. A new, independent workflow is created from the template - a copy, not a reference. Change anything; the template stays intact.
2. All internal cross-references are carried over automatically - node IDs are regenerated and every {{steps.…}} reference (including those inside Transform code) is remapped to the new IDs, so the copy works out of the box.
3. The editor opens with the AI assistant already active. It checks the template's requirements against your workspace - missing global variables, unconfigured MCP servers, or a missing AI provider are listed, and you can fix them directly from the chat (save a variable, configure a server) without leaving the editor. When everything is in place you'll see a green "ready to run" confirmation.

Saving a workflow as a template

1. Open the Workflows list in the sidebar.
2. Click the … menu on a workflow you have edit access to.
3. Choose Save as template.
4. Fill in the dialog:

• Name - short and descriptive (min 3 chars)
• Description - what it does, when to use it (min 10 chars)
• Category - one of the 15 categories
• Tags - up to 10 optional free-form tags

5. Click Save template.

A snapshot of the workflow's nodes and edges is stored. Required MCP servers, AI providers, and models are auto-detected from the nodes and attached to the template, so future users see the prerequisites upfront. The original workflow stays independent - editing it later does not change the template.

Saved templates are private to your organization and immediately usable by teammates.

Who can save? Any user with edit permission in the workspace: OWNER, ADMIN, and MEMBERs whose workspace grants canEdit.

Managing your org's templates

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

• Edit metadata - name, description, category, tags. The workflow structure (nodes/edges) is frozen at creation; 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.

Usage counts are tracked per template, so you can see which ones your team actually reuses.

Plan limits

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

System templates don't count against your limit. When you hit the cap, the Save dialog shows an Upgrade action that takes you 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 personal configuration
• Half-finished drafts - save them as regular workflows first, template once stable

Related

• Node Types
• Workflow Examples