Flow Templates
Save a workflow's input once, then trigger it again later just by clicking a button — no need to remember what data to type in or which node to open. Templates make repeatable jobs, scheduled runs, and one-click re-runs possible without touching the canvas each time.
What Is a Template?
A Flow Template is a saved, named copy of everything an Execute action needs: the input data, any attached forms, and a couple of execution options. Once it's saved, running it again is a single click — you don't re-open the Studio, re-fill any fields, or remember what values you used last time.
Every template is tied to exactly one target — a whole workflow (Process), a specific run of that workflow (ProcessThread), or a single node on the canvas (ProcessElement). This is called the template's scope, and it's fixed the moment the template is created — see Creating a Template for how scope gets chosen.
Save Once, Run Many Times
Fill in the input data one time and save it as a template. Every future run reuses the same saved data — no retyping.
Scoped to One Target
A template always points at one Process, ProcessThread, or node. It runs that target and only that target.
Shared Across the Tenant
Anyone in your organisation with rights to the underlying workflow can find and run a template someone else created — it isn't locked to one app.
Predictable, Not Magic
If the node a template points to is later removed, the template fails with a clear error at run time instead of silently doing the wrong thing.
Where You'll Use Templates
There are two everyday places you'll work with templates:
- The Jobs screen in the left menu — a searchable list of every template you have access to, with one-click Execute and Config actions on each row. See Searching Templates.
- The Studio canvas itself — select a node, a thread, or nothing at all, then click Create Template to save exactly what you're looking at as a new template. See Creating a Template.
Templates can also be chained together into Pipelines, so several saved templates run one after another in order — see the Flow Pipelines guide for that.
Guide Pages
| # | Page | What You'll Learn |
|---|---|---|
| 1 | Creating a Template | The two ways to create a template — from Jobs, and from inside the Studio |
| 2 | The Five Tabs | A quick tour of Basics, Json, Data Items, Render Options, and Templates |
| 3 | Data Items Tab | The item grid, Add/Delete/Duplicate/Reorder, the property editor, and drilling into nested fields |
| 4 | Render Options & Templates Tab | Attaching Atlas Forms, and setting the default new-item template |
| 5 | Executing a Template | The Execute button, Concurrency Behavior (Allow/Block), and "already running" messages |
| 6 | Searching Templates | The Jobs screen, remembered search fields, and row actions |
| 7 | FAQ & Troubleshooting | Answers to common questions about templates specifically |