Templates

A flow you publish publicly becomes a template: anyone can read its definition and fork a copy into their own workspace to run and edit. It's how a good flow stops being a one-off and becomes a starting point.

Publish a flow as a template

Set a flow's visibility to public and it's listed in the public gallery. Its definition becomes readable, and its fork count tracks how many people have started from it. You're publishing the flow's structure — the nodes and how they're wired — as something others can learn from and build on.

Fork a template

Forking copies a public flow's definition into your workspace as a new, editable flow — optionally pinned to a specific published version of the source. You land in the editor with the fork open, free to change anything; it's yours now, with its own stable id, disconnected from the original.

This works from the browser and from the API: