Workflow Templates
A template is a workflow used as a starting point. Using one always produces a new workflow in your workspace — a copy with its own key and version history — that you then edit and activate like any other.
Two sources
| Source | What it is | Where |
|---|---|---|
| Workspace templates (My Templates) | Your own workflows that have an Active version. | Templates › My Templates |
| Store templates (From Store) | Workflows published to the Burdenoff Store by Burdenoff or third-party publishers, with a description, category, tags, screenshots, and compatibility metadata. | Templates › From Store, and the Marketplace |
What a store template carries
A store template packages the workflow graph plus its node dependencies — the store nodes it needs. On import FluidGrids checks each dependency: already Installed, Will install (installed for you as part of the import), or Purchase required (a paid node you must buy in the Marketplace first). It also lists the connections you will need to add and any required configuration values.
Imported workflows keep a lineage link to the template they came from, which the Store uses for download counts and which you can use to trace where a workflow originated.
Categories
Templates are grouped as Data Processing, Integration, Automation, AI/ML, and Communication. Store templates declare their category; workspace templates are categorised from their tags, name, and description.
Templates and quotas
A workflow created from a template counts against the workspace's workflow quota exactly like one created blank.
Publishing
Publishing a workflow as a Store template is a Developer Portal submission with review — the same channel as publishing a node. There is no one-click Save as template in the builder yet.
Next steps
- Templates — using the screen
- Understanding Workflows