Complete, runnable flows
A template embeds the full flow graph, including its nodes, connections, and configuration. You clone it, set your parameters, and run it. It carries the structure only and never any runtime data.
Template Hub
Clone the validated flow. Don't re-improvise it.
Templates are the unit of reuse in Flow. They are complete, working flows that teams clone, parameterize, and run. One central update propagates to every instance, and version pinning means the drift trap cannot fire.
Why templates
The version-drift trap, eliminated
Here is the classic failure mode. An engineer keeps a local copy of a toolkit, a scan procedure, or a job deck. Months later they run it against a system that has moved on. They then burn an afternoon on failures that have nothing to do with their actual task, because the toolkit was back-level.
A Flow template fetches and pins its dependencies per run. The flow that worked in validation is byte-for-byte the flow that runs in production. When the template owner publishes an update, every clone picks it up from the hub. There are no stale copies, no email attachments, and no tribal knowledge.
Versioned and pinned
Templates carry versions, and flows pin the version they validated against. Central updates propagate deliberately, not accidentally.
Reviewed like code
Flow DSL is plain text. Templates live in source control, go through pull requests, get code owners, and promote through branches.
Node-type guarded
Loading a template whose nodes reference an unsupported node type is rejected with a clear error, so templates cannot silently degrade.
Approval gates (roadmap)
The hosted Template Registry adds versioning history, approval gates, and validation that shared templates reference only approved model versions.
Vendor-neutral by rule
No vendor- or product-specific templates are hardcoded in the platform. Catalog entries describe patterns; your data stays your data.
In practice
Read the fleet-scan case study
From template to fleet
A security team publishes a scan template once. A batch operator clones it, adds a Cron node, and schedules it across the whole fleet monthly. The toolkit is fetched fresh on every run, so the fleet never drifts. When the scan procedure changes, one central template update reaches every instance.
That pattern is build once, validate once, and clone everywhere. It is how individual productivity wins turn into team-level standardization without a mandate.
Start from a working flow
Browse the Template Hub from the Flow Studio workspace rail, or save your own flows as templates.