Templates and organization.

A template is a starting graph you can instantiate as another project. Changing the resulting project does not update the source template automatically.

#Follow a template into separate projects

One reusable template can start two independent projects, such as a detail crop and a monochrome variation. Save each under its own name. Edits do not automatically update the template or the other copy. Collections organize projects, albums organize media, and Node Kits organize nodes; none supplies missing credentials.

The plant-portrait source template forks into project A’s closer framing and project B’s monochrome treatment. Each branch retains its own identity; neither change flows back to the source template or its sibling.

#Use a template

Open Browser → Templates, select a card to inspect its details, and double-click to instantiate it. Save the resulting temporary project under its own name before treating it as a saved project.

A template with bundled data can show results immediately. Without that data, the recipient needs to run it. Either way, check the providers, plugins, and files the workflow needs before executing it.

#Create a template

Open Save as Template from the save controls. Give it a useful name, description, category, tags, and thumbnail. Decide whether to include output data, then save.

Including data can help someone see an example without rerunning, but it also includes material you are choosing to share. Check source files and outputs for private or licensed content before publishing a template.

#Share a template link

Built-in and community template details provide a shareable link and Copy control. Opening it takes the recipient through sign-in when needed and then loads that template. Private user templates do not gain a public share link just because they have been saved.

#Organize the library

Use Node Kits to group the nodes you reach for together and filter node browsing. Use project collections to organize projects, and media albums to organize browsed outputs. These are organization tools; a template is the reusable workflow itself.

For a visitor-facing runnable tool, publish a Station. For calls from another application, create a workflow API endpoint.

#Choose the right kind of reuse

Template: instantiate a reusable starting graph and save the new project separately. Station: present controlled inputs and results to a signed-in visitor. API endpoint: expose an explicit application contract. Project collections, media albums and Node Kits organize material but do not replace these execution or sharing surfaces. Check bundled data and recipient access.

#Checks and next steps

Before saving or sharing a template, inspect its required files, provider access, plugins, and exposed inputs and outputs. Including output data may make an example visible without rerunning, but it can also bundle material you did not intend to distribute. It does not configure recipient credentials.

After instantiating a template, save the resulting project independently and check its current inputs before running. Use a Station for controlled visitor execution and a workflow endpoint for an external application. A collection, album, or Node Kit organizes material; none is a published runnable workflow.