Creating a Template
There are two doors into the same template editor — starting cold from the Jobs screen, or starting warm from wherever you already are in the Studio. Either way you land in the same five-tab editor with the same fields.
Way 1 — From the Jobs Screen
Open Jobs in the left menu (see Searching Templates) and click Add at the top of the list. This opens a brand-new, blank template in the editor. Because you didn't come from a specific node or workflow, you choose the scope yourself on the Basics tab — pick whether this template targets a whole workflow, one specific run of it, or a single node.
Use this route when you already know exactly which workflow, thread, or node you want to template, and you'd rather search for it by name than navigate to it on the canvas first.
Way 2 — From Inside the Studio
While you have a workflow open in the Studio, a Create Template action is available. Where it points depends on what's currently selected on the canvas — you don't have to set the scope by hand:
| What's selected in the Studio | Scope the new template gets |
|---|---|
| A specific node is selected | Node — the template runs that one node |
| No node selected, but a thread is open | Thread — the template runs that specific run/instance |
| Nothing selected — viewing the workflow at the top level | Process — the template runs the whole workflow |
Click Create Template and the editor opens as a panel on top of the canvas — you never leave the workflow you were working on. The scope is shown to you as a read-only badge (for example, "Scoped to: Node Send Invoice Email") so you can confirm what you're about to save a template for, but you can't accidentally change the target mid-creation. If you decide not to save, close the panel and you're back exactly where you left off, canvas untouched.
Studio canvas, node "Send Invoice Email" selected
│
▼
Click "Create Template"
│
▼
Editor panel opens over the canvas
│ Scope badge: "Scoped to: Node — Send Invoice Email" (read-only)
│ Configuration starts blank: { inputData: { items: [{}] } }
▼
Fill in Basics / Json / Data Items / Render Options / Templates
│
▼
Save → panel closes, toast confirms creation
with a link to open it in JobsWhat Starts Filled In, and What Doesn't
- Scope is pre-filled and locked, resolved automatically per the table above.
- Configuration (the input data) always starts from the same blank skeleton — it is not pulled from whatever data the node last ran with. If you want to reuse real values, add them yourself on the Data Items tab after creating the template.
- Every other field — Name, Description, Concurrency Behavior, attached forms, and so on — starts empty, exactly the same whichever door you came in through.
Permissions
Creating a template needs the same access rights as editing the workflow, thread, or node it targets. If you already have the Studio open in edit mode, or you can already see the item in Jobs, you already hold that right — there's no separate permission prompt.