Save a workflow as a template

Goal

Take a workflow you have already built and published, then snapshot it as a reusable template. Once published, the template is available to every Workspace in your Account, and you can apply it into a client Workspace as a new, independent workflow.

A template is a catalog entry that holds an immutable snapshot of a workflow graph. Each time you publish, you create a new revision (v1, v2, and so on). Workspaces that have already applied an older revision can review and pull your updates later.

When to use this

Save a workflow as a template when you have a working automation that you want to reuse across clients instead of rebuilding it by hand each time. Common cases:

• You run the same onboarding sequence for every new client and want one source you maintain.
• You want to hand a starting point to a teammate who will customize it per Workspace.
• You plan to ship updates over time and want each Workspace to decide when to adopt them.

If you only need to use a template someone has already published, see Apply a template instead.

Before you start

The Publish as template... action only appears once your workflow is published. If you have not published yet, the action is hidden and there is nothing to snapshot.

Steps

1. Open the published workflow in the editor

   Open the workflow you want to reuse. Confirm it is published. If you made edits after the last publish, save and publish again so the snapshot captures the current graph.

2. Open the workflow actions menu

   In the editor header, click the three-dots overflow button (labeled More workflow actions). Choose Publish as template... from the menu.

   If you do not see this item, the workflow is not published yet. Publish it first, then reopen the menu.

3. Name the template

   In the Publish as template dialog, enter a Name. This is what your teammates see in the Templates list, so make it specific:

   Client onboarding email sequence

   Copy code

   The name is required and accepts up to 120 characters.

4. Add a description (optional)

   Use the Description (optional) field to say what the template does and who it is for. It accepts up to 1000 characters and helps teammates pick the right template later.

   Sends a three-message welcome cadence when a new client signs up. Set the from-address per workspace.

   Copy code
5. Write the changelog

   The Changelog field is required and defaults to Initial revision. Keep that for your first publish, or describe what this revision contains. It accepts up to 4096 characters.

   Workspaces see this changelog when they decide whether to apply your updates, so write it for that audience.

6. Publish the template

   Click Publish template. TaskJuice creates the template catalog entry, then stamps revision 1 with a snapshot of the current workflow graph. When it finishes, you land on the template detail page at /templates/{id}.

What gets captured (and what does not)

Publishing captures the workflow graph as an immutable snapshot at revision 1. It does not collect template variables. Your first revision ships with an empty variable list.

To make the template configurable per Workspace (for example, a from-address or a Slack channel that each client sets), add variables on a later revision from the template detail page. You can define up to 50 variables per template, and they are read at run time as $vars.<key> in expressions. Use the Publish new revision action on the detail page to add them.

Verify it worked

After publishing, confirm the template is live:

1. You are redirected to the template detail page, and a toast reads Template published.
2. The header shows the template name, a Tenant scope badge, and a v1 revision badge.
3. The Revisions card lists v1 with your changelog and the publish time.
4. Open the Templates entry in the sidebar. Your template appears in the list with Latest rev showing v1.

The Client workspaces card reads "No client workspaces yet" until a Workspace applies the template.

Troubleshooting

The "Publish as template..." item is missing from the menu. The action is hidden until the workflow is published. Publish the workflow, then reopen the overflow menu.

The dialog says "This workflow version has no graph yet." The current workflow version has no saved graph to snapshot. Save the workflow, then try again. The Publish template button stays disabled until there is a graph to capture.

The Publish template button is disabled. Both Name and Changelog are required. The button enables only when both fields have content and the workflow has a saved graph.

You see "Failed to publish template." The publish did not complete. Check that the workflow is still published, then retry from the menu.

Keeping applied workspaces up to date

When you publish a new revision of a template, every Workspace that applied an older revision sees a Template update available banner in its workflow editor. From there an operator can apply the update, skip the revision, or detach the workflow from the template entirely. You do not need to push updates manually. Each Workspace adopts them on its own schedule.

Related

• Apply a template - clone a template into a client Workspace and fill its variables.
• Publish a workflow - the publish gate you must pass before you can save as a template.
• Start from a template - the end-to-end path from template to a live workflow.