- Documentation
- Use cases
- Find and apply a template
Find and apply a template
Open your templates list, pick a template, choose a target workspace, then finish what is left to create a live workflow.
Goal
Turn one of your account's templates into a working workflow inside a client workspace. You pick a template and choose which client workspace gets a copy. The copy is a new workflow in that workspace, it can take the template's later changes when you choose, and you finish what is left for that client (its connections and step settings) afterwards.
When to use this
Use this when you have already saved a workflow as a template and want to reuse it for another client. A template is a snapshot you author once and apply to as many workspaces as you need; each copy gets its own settings (the from-address, the Slack channel, the connection to use) after you apply it.
Your templates live on the Templates page, in the account sidebar and in each workspace's sidebar right after Workflows. This is your own catalog, scoped to your account, not a public gallery. It always includes the three built-in templates (From TaskJuice badge); see Look up which templates ship with your account for what each does and what you supply.
To add a template of your own, choose "Save as template" from a workflow's … menu on the Workflows page, or from the ⋮ menu in the editor. See Save a workflow as a template.
Before you start
- At least one template with a published revision. The Apply template button only appears once a template has a revision; an unpublished template shows the badge "Unpublished" and cannot be applied.
- At least one workspace to apply it into. The workspace picker is empty otherwise, and you will see "No workspaces available. Create one before applying templates."
- The build capability on the target workspace. Without it the apply call returns a permission error (see Troubleshooting).
Find a template
Open Templates from the account sidebar, or from a workspace's sidebar right after Workflows. The page shows one card per template with:
- The template name and description, linked to its detail page.
- A From TaskJuice badge on built-in templates, and an Agent badge on agent templates.
- How many workspaces use it, and when its latest revision was published (or Not published yet).
Narrow the cards with the search box, or the All, Yours and From TaskJuice filters. Click a template to open its detail page, where you check the Workflow preview, confirm the revision and read its changelog before applying.
Apply a template
From the template detail page, the Apply template button (it carries a play icon) starts the flow. The dialog asks only which workspace to put the copy in.
Open the template detail page
Click the template's name in the Templates list. The header shows the name, a scope badge, and the latest revision badge (for example
v3). The Revisions card lists each published revision with its changelog so you can confirm which version you are about to apply.Click Apply template
The dialog opens with the title "Apply template" and the description "We'll add a copy of this workflow to that client. When you update the template, you'll be able to apply the changes there."
Choose the target workspace
Pick a workspace from the Workspace selector. This is the client workspace that will own the new workflow. If the list is empty, create a workspace first.
Submit
Click Apply template. The button shows "Applying..." while the template's workflow is copied into the workspace. On success you see a "Template applied" toast and the editor opens on the new workflow.
Finish what is left
Click See what's left on the toast to open the workflow's setup page. It lists each app connection the workflow needs and each step you still have to fill in, with an Open link to where you finish it. You can also set each step's fields in the editor.
The new workflow is the client's own copy in status draft, version 1, named after the template. Editing it does not change the template or any other workspace that applied the same template. When you save a new revision of the template, the copy shows an Update available notice and you choose whether to apply it. When you are ready, publish the new workflow the same way you publish any workflow.
Finishing the copy
Applying never asks for a client's details up front. Whatever the copy still needs is finished after it exists:
- Connections. A step that sends through an app needs a connection for that app in the target workspace. The setup page lists each one; to add a connection, see Connect an account.
- Step settings. Values such as a from-address or a Slack channel are set on the step itself, in the editor. The setup page links to each step that still needs something.
Publish in the editor also names anything still missing, so nothing goes live half set up.
Verify it worked
- The "Template applied" toast appears and the editor opens on a new workflow named after the template.
- On the template detail page, the Client workspaces card now lists the target workspace with the note "On template revision N. The workflow is not turned on.", a Not running badge, and a Clean badge (it stays Clean until you edit the copied workflow, which flips it to Modified). After you publish the workflow, the row reads Live with the version that is running.
- The new workflow is in
draft. To make it live, publish it. See Publish a workflow.
Troubleshooting
The Apply template button is missing. The button only shows once the template has a published revision. If the header reads "Unpublished," publish a revision first.
"No workspaces available. Create one before applying templates." The target workspace selector is empty. Create a workspace, then reopen the dialog.
Apply template is disabled. No workspace is chosen yet. Pick one in the Workspace selector.
"Failed to apply template" with a permission message. Applying a template needs the build capability on the target workspace. If you lack it, the call returns HTTP 403, "You do not have permission to apply templates in this workspace." Ask an account admin to grant access or choose a workspace where you have build permission.