Operating Flux

Templates

Templates are saved workflows you can start from. Flux ships a marketplace of them, and anything you build can be saved as one.

The three tabs

Tab	Holds
Marketplace	Templates published for everyone, searchable by name and plan
My Templates	The ones you saved yourself
Favorites	Marketplace templates you starred

The templates dialog on the Marketplace tab, showing template cards with name, description, access type and plan badge

Screenshot to be added

Start from a working workflow instead of an empty canvas.

Using one

Open Templates from the module.
Search, or browse the marketplace.
Check the plan badge — templates are marked Free, Basic, Premium or Enterprise, and you need that plan to use them.
Use Template.

The workflow is created with its nodes and wiring in place. You still supply your own credentials and adjust the prompts — a template carries the structure, not the secrets.

Saving your own

Save as template takes the workflow you are in and stores it under My Templates, with a name and description.

Worth doing when:

You build the same shape repeatedly for different clients.
A workflow is a good starting point that colleagues should not rebuild.
You want a known-good version to fall back to before a risky change.

Templates make a reasonable safety net before a big edit: save the working version as a template first, then change the live one. If it goes wrong you have somewhere to return to.

What a template carries

Included

The nodes, their wiring, their configuration and the template expressions between them.

Not included

Your API keys. Credentials are referenced by id, so the secret never travels with the template.

That is why a template is safe to publish, and why the first thing to do after using one is select your own credentials on the nodes that need them.

Plans

Each template is tagged with the plan it belongs to — Free, Basic, Premium or Enterprise. The badge on the card tells you before you open it.