Look up which templates ship with your account
Every account ships with built-in templates. See what each one does, what you supply after you apply it, and the errors an apply can return.
What you start with
Every account's Templates list includes three built-in templates, marked with the Platform badge. You can apply them as they are. Any template you save from your own published workflows appears in the same list with the Tenant badge. See Save a workflow as a template to create your own.
Where templates come from
Every template in your list has one of two scopes, shown as a badge on the templates table and the template detail header.
| Scope badge | Who authored it | Re-publishable by you |
|---|---|---|
| Tenant | Your account, by saving a published workflow as a template | Yes |
| Platform | Built in, shipped to every account | No |
Built-in templates
Applying a built-in asks only for the workspace to put it in. The copy opens in the editor with every step filled in: the trigger and each app action are already chosen. What is left is what only you can supply, and Publish lists exactly those items until they are done.
| Template | What it does | What you supply |
|---|---|---|
| Onboarding email sequence | When a signup is posted to its webhook, sends a welcome email to the signup's email, waits a day, then sends a follow-up. | A Gmail connection on both email steps |
| Lead qualifier | When a lead is posted to its webhook, classifies it with AI and alerts a Slack channel when it is qualified, with the lead attached. | A model on Score lead; a Slack connection and a channel on Alert sales |
| Status digest | When a batch of records is posted to its webhook as a JSON array, counts them and posts one summary message to Slack. | A Slack connection and a channel on Post to Slack |
| Hand chats to Slack | When a website visitor writes in a chat, posts the message to a Slack channel, one thread per conversation, and shows no reply in the chat while your team handles it. | The chatbot on the trigger; a Slack connection and a channel on Reply in thread and Start a thread; your table on Find thread and Save thread |
| Slack replies to chat | When someone replies in a chat's Slack thread, sends the reply to the visitor's open chat as a person who joined. | A Slack connection on the trigger; your table on Find chat; the chatbot on Send to chat |
The first three start from a webhook, and each copy gets its own webhook URL once you publish it. Hand chats to Slack starts from a chatbot's chat, and Slack replies to chat from a Slack message; see Hand a chat to your team in Slack.
Publishing a workflow that sends through Gmail or Slack needs an OAuth app for that app that holds the permission each step uses: your own app keys with that scope ticked, or TaskJuice's app where it is available and approved for that permission. Until one does, Publish names the step and the missing permission. See Which OAuth app a connection uses.
When a built-in is updated, a copy you already applied shows Template update available in the editor. Steps you have not changed take the update; a step you changed and the update also changes is listed for you to choose which version to keep.
What happens when you apply a template
The template detail page shows an Apply template button once the template has at least one published revision. Applying it asks only which workspace to put the copy in. Nothing else is asked up front, for a built-in or for a template you authored.
On success, the template's graph is cloned into a new, independent workflow in the workspace you chose, and it opens in the editor as a draft. The Template applied message offers See what's left, which opens the workflow's setup page: it lists each connection to add and each step to fill in before the workflow can go live. You can also finish everything in the editor, where Publish names whatever is still missing.
Failure cases
| Code | HTTP | When it happens |
|---|---|---|
template.not_found | 404 | The template you tried to apply has no published revision yet, or does not exist. |
Invalid request bodies return HTTP 422 with a fieldErrors array, where each entry is { field, code, message } so you can map the error back to the offending field.
Related
- Find and apply a template walks through applying a template end to end.
- Save a workflow as a template is how every template in your list gets created.
- Expressions explains how a step references the trigger and earlier steps.