Publishing flows as templates
Once a flow works the way you want, save it as a template so other companies in your tenant – or you yourself, on a different setup – can spawn copies of it without rebuilding it from scratch. Templates you save this way are private to your tenant: only your AutoFlow users see them.
Save a flow as a template
From any flow card, open Template → Save as template. A wizard opens.
Step 1 – metadata
| Field | Notes |
|---|---|
| Name | Shown in the gallery list. Must be unique within your tenant – the wizard checks as you type and rejects a duplicate before you continue. |
| Tagline | A one-line description shown next to the name. |
| Language | The language the template is written for (e.g. de-de, en-us). Helps users filter the list by their own language. |
| Version | A version number like 1.0.0. Each new version has to be higher than the last one – the wizard takes care of bumping it for you when you update an existing template. |
| Icon URL | Optional. A link to an image you want shown next to the template's name. |
| Usage | Optional. Longer notes for the user, shown in the Template Details factbox. Uses the same Markdown formatting described under Creating flows from templates. |
| Changelog | Pre-filled with a default first entry (## v1.0.0 – <today> and Initial version.); replace it with notes that explain what's in this version. |
Step 2 – app pre-requisites
The wizard suggests AutoFlow Core (and AutoFlow itself, if installed) as the minimum requirements. Add further apps via the lookup arrow on the App ID column – it opens a picker of every app currently installed on the tenant, so you don't have to know GUIDs. Each row has an inline Remove link if you need to drop one again.
App pre-requisites determine which tenants can use the resulting template: anybody whose installation is missing a required app, or has it at a lower version than the minimum, sees the template disabled with an explanatory message in the factbox.
Finish
Click Finish to upload the template. The flow card now shows Template → Update template instead of Save as template – it remembers the template you created from this flow, so the next save becomes an update of that same template. The flow card also shows which template version is currently applied; that's a handy reference if you ever need help from support.
A flow has to be published to be saved as a template – the gallery only ever holds the published version of a flow. If you're still on a draft, the wizard offers to publish first and then continues straight to the upload.
Update an existing template
If your flow is linked to one of your own templates, Template → Update template is shown instead of Save as template. The wizard:
- Pulls the gallery's current copy of your template before doing anything (so a stale local cache cannot mask conflicts).
- Pre-fills with the gallery's metadata. The version field auto-bumps the patch number, the changelog gets a new entry prepended above the prior history, and the name is locked – use Disconnect from template if you really want to rename.
- Warns you if the gallery has moved past the version this flow was based on. That happens when somebody updated the same template from another company or environment in the meantime. You can choose to continue (your version becomes the new one in the gallery) or cancel and first pull their version onto your flow with Update from template.
The new entry's heading is rendered as a Markdown title in the changelog factbox, so the history reads like a release-notes page – newest version on top.
Things to know
- Credentials never travel with the template. Only the names of the credentials a flow needs are part of the template. Whoever spawns a flow from it has to set their own values, the same way you set yours.
- Each upload is a new version. The gallery keeps the latest version only; older revisions live in the version history of your local flow.
- Public templates come from mse Software and selected partners and are added through a separate process. As an end user you can only use them – there is no "publish to the public gallery" button for your own templates.