Skip to main content

Creating flows from templates

Use a template as the starting point for a new flow. The template gallery hosts both your tenant's private templates and the public ones curated by mse Software and selected partners – pick anything you can see in the list.

The list​

Open AutoFlow Template Gallery from the BC search. Each row shows:

  • Publisher – the company name of the tenant that uploaded the template. For your own private templates this falls back to your registered company name.
  • Name and Tagline – a short identifier and a one-line description.
  • Language – the language the template was authored for (e.g. de-de, en-us).
  • Version – the gallery's current version of this template.

Select a row to see two factboxes:

  • Template Details – the rendered usage notes plus the pre-requisite status.
  • Changelog – the history of versions, newest first.

Create the flow​

Click Create flow from template on the row you want.

  1. The pre-requisites are re-checked. If something is missing or out of date, you'll be told which app and the action stays disabled until you fix it.
  2. For public templates a step-preview dialog opens. It lists every action in the flow plus the external endpoints they touch (HTTP request URLs, mail recipients, …). This is your chance to review what an unknown publisher's template actually does before it lands on your tenant.
  3. A new flow is created with the template's definition. The flow's description defaults to the template name; if a flow with that name already exists, a numeric suffix is added until it is unique.
  4. The flow card opens so you can adjust the description, fill in any missing credentials, and publish.

The new flow is linked back to the template. The flow card shows the template version it was created from, and you get two follow-up actions:

  • Update from template – pulls the gallery's current definition into a new draft. The published version of the flow is left untouched, so any flow that's already running keeps running until you manually publish the updated draft. If the gallery hasn't moved past the version you already have, the action tells you so and skips the apply.
  • Disconnect from template – severs the link. Use this when you've customised the flow heavily and no longer want to track the template's updates.

Credentials​

A template never carries credentials. The flow only knows the names of the credentials it needs; the actual passwords, tokens, or API keys live on each tenant separately and are never uploaded to the gallery. After spawning the flow, open the AutoFlow Credentials page and fill in the values for whatever names the flow expects. Steps that need a credential you haven't set yet won't run – they tell you which one is missing when they try.

Formatting the Usage and Changelog text​

The two factboxes accept a small set of Markdown for the Usage notes and the Changelog:

  • Headings with ## … (large) and ### … (smaller).
  • Paragraphs, separated by a blank line.
  • Bullet lists with -, *, or +.
  • Bold, italic, inline code.
  • Links like [Click here](https://example.com).
  • Horizontal rules with --- on a line by itself – useful between changelog versions.

Everything else shows up as plain text. That includes images and embedded HTML, which the factboxes don't render – good to know when you're writing your own templates.