Browsing and installing templates

What a template is

A template is a ready-made setup you can install into your store instead of building it from scratch. It always includes workflows, and it can also include search indexes, data tables, MCP servers, assistants and data privacy rules, so one install can give you a whole working feature.

Templates are provided to you. You can't publish your own from the designer. To reuse something you built, use Export and Import on the Workflows page instead. Which templates you see can depend on your organisation.

Finding a template

There are two ways in, and they show the same templates:

• The Templates page in the sidebar.
• Browse templates on the Workflows page (and on the dashboard), which opens the same gallery in a window so you stay where you were.

Narrow the list with the filters on the left:

• Filter by tag: tick one or more tags. A template matches if it has any ticked tag. Use Search tags… to find a tag, and Clear to reset.
• Filter by type: API, Webhook, Batch Job, Scheduler or File Event, according to how the template's workflows are triggered. Ticking several types matches templates with any of them. Tag and type filters narrow each other.

Each card shows the template's name, a short description, and chips for its types and tags. Select a card to open it.

Reading a template

The template page tells you what you would get and what you need to do:

• Overview: what the template is for.
• Features: the main things it does.
• Configuration: what you will need to supply, such as a connection or a value, in a table of Field, Key, Type and Notes (a red asterisk means required). This is guidance only; nothing is entered here. If a route runs on setup, a Runs automatically on setup notice lists it: that route fires once as soon as you finish configuring the workflow.
• What's included: the assistants, search indexes, MCP servers and data tables it creates, with their fields, tools and starter prompts. A Data privacy card lists fields that are masked in execution logs once installed. Connects to names the connectors it relies on.
• Workflow or Workflows (N): each workflow's routes (with their methods and paths), variables and test cases.

Installing a template

1. Choose the store in the header, then select Install (on the template page, or in the gallery window).
2. Confirm. The dialog says what will be added, for example "1 search index, 3 workflows and 1 assistant". Workflows are added as drafts. Nothing is published.
3. If your store already has something the template would create, a second dialog lists it. Checked items are overwritten with the template's version. Untick any you want to keep, and the template then uses yours. Overwrite all and Keep all of mine switch every item at once.

What you overwrite	What happens
Search index	Its settings and fields are updated. Documents and prices are kept; if fields change, it is rebuilt in the background.
Data table	Its settings are replaced. Its rows are kept.
Workflow	Its draft is replaced. The live version keeps running until you publish again.
MCP server	Its tools and settings are replaced. Existing API keys keep working.
Assistant	Its instructions, appearance and settings are replaced. Its embed code keeps working.

After installing, one new workflow opens in the editor. Several take you to the workflow list. A template with no workflows leaves you where you are. Some messages, such as an index being rebuilt or a connection needed for agentic search, appear as toasts that stay a little longer.

After you install

1. Open the draft workflow and review it.
2. Set the connections and variables it needs. Templates don't create connections; the Configuration table and the Connects to line on the template page tell you what to expect. See Connections.
3. Try it with the workflow's tests, then publish and launch it. See Launching workflows.

If you install the same template again, you are asked what to overwrite, because nothing marks a template as already installed.

If an install fails

• "This template depends on workflows or connections not in your store." Something it needs is missing. Add it and try again.
• "Workflow limit reached for your plan." You have reached your plan's workflow limit. Remove a workflow or upgrade.
• Anything else shows the message from the server.