The Template Library: A Vetted Catalog of Reusable Network Tasks

Every network team rebuilds the same handful of tasks: check interfaces, verify BGP, audit NTP, back up a config. The Template Library captures those tasks once — parameterised, vendor-aware, and reviewed — so you start from a known-good base instead of a blank file.

What a template is

A template is a self-contained, reusable unit of work with a unique code, a clear name, a target task category, and a set of typed parameters. Each one declares whether it is read-only or mutating, which vendors it supports, and what inputs it expects — so the platform can render the right form and the right safety rails automatically.

• Code + name — a stable identifier you can reference from a workflow.
• Category — diagnostics, compliance, provisioning, backup, and more.
• Parameters — typed inputs with defaults, so the same template adapts per run.
• Safety class — read-only templates run freely; mutating ones require confirmation.

Finding the right one fast

The library is built for retrieval. Search matches on both code and name, and category filters narrow the list to the kind of task you have in mind. The goal is the same as a good package registry: from intent to the right template in a few seconds, without scrolling a wall of files.

From template to running task

A template is only useful if it gets used. From any entry you can run it directly with its parameters, or add it to the canvas in the Workflow Builder to chain it with others. The same template definition powers both paths, so what you tested in isolation behaves identically inside an orchestration.