Overview
Templates are pre-built starting points for eight kinds of entity: workflows, playgrounds, forms, visualizers, agents, streams, data sheets, and MCP servers. Each template ships the reusable shape of its entity — a workflow's triggers + tasks, a playground's HTML/CSS/JS + seed data, a form's sections, a visualizer's schema + views, an agent's instructions, a stream's channels, a data sheet's columns + sample rows, or an MCP server's role and tool selection — with team-specific secrets and connections stripped out.
Finding templates
From the dashboard or the public catalog, open the template library and filter by type (workflow, playground, form, visualizer, agent, stream, data sheet, or MCP server), platform tool, AI model, or tag. Each template shows a short description and what it uses.
Creating from a template
Select a template and choose to create from it. Every type asks for a destination app; the surfaces with a public URL (playground, form, visualizer) also ask for a unique slug. The new entity is created as a draft with the template's content; secrets, connection bindings, and access passwords are never carried over (you re-bind them after creation), and playground asset uploads use placeholder image URLs you can replace.
A data sheet template creates a new database in your app with the template's sheets, columns, and a few sample rows — fresh and independent of any other data. An MCP server template creates a new hosted server with a freshly-minted access token and the template's role hint; its platform-tool selections are re-connected to your team's connections where you have them and skipped where you don't, so open the new server and finish wiring any tools, workflows, agents, or data sheets it should expose.
Duplicating an existing entity
Templates are for reusable, shareable starting points. To make a one-off copy of something you already own, use Duplicate instead — available on workflows, playgrounds, forms, visualizers, agents, streams, and Data Sheets (whole database or a single sheet). A duplicate copies the full configuration (and environment-variable overrides) into a fresh draft in the same team, regenerating unique slugs/codes and secrets so the copy is independent of the original.
Tips
Use templates to learn patterns or to get a head start, then customize for your app and data. Templates are authored by FlowFn admins; if you want to reuse one of your own builds within your team, Duplicate is the faster path.