> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryflowy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Flowy is a node-based AI creative platform: you generate images, video, audio, 3D and vector on an infinite Canvas, refine on the Studio timeline, and export or publish from the same project.
> Prefer the Flowy MCP server (https://mcp.tryflowy.ai/mcp) or the REST API at https://apis.tryflowy.ai/v1 for programmatic work. Install with `flowy mcp install` from the @flowy/cli package.
> Credits are workspace-scoped. Generations reserve credits on start and only deduct on success, so failed runs refund automatically.

# Publishing

> Share a project as a remixable template, or a flow as a runnable tool, and undo either one anytime.

Two different things can go public from your workspace: a **project**, published as a template others remix, and a **flow**, published as a tool others run. Each has its own publish step and its own way back.

## Publish a project

From the canvas, open **Share** and choose **Publish to Community**. Publishing needs at least 2 nodes on the canvas, with fewer, the Continue button stays disabled.

The publish form asks for:

* **Title** and **description**: what you made and how you built it.
* **Category**: one of Canvas, AI Directed, Marketing, Social, Product, Education, Entertainment, or Other.
* **Tags**: up to 5, chosen from category-recommended suggestions or typed in yourself.
* **Cover**: pick from images already on your canvas, or upload your own image or video.

Once published, the project appears in [Templates](/community/templates) and can be remixed by anyone. What becomes public is the canvas itself (nodes, connections, settings) and the media it produced, copied to a public tier so signed-out visitors can preview it, separate from your private workspace copies.

Publishing again re-opens the same form, now labeled **Publish updates**: edit the title, description, category, tags, or cover and republish. An **Unpublish** action in the same dialog removes the project from Community immediately; the project itself stays in your workspace untouched.

## Publish a flow

Flows publish from the App Builder, with an extra layer: a **visibility** radio (Private or Workspace) that controls who can find it in your workspace's Library, plus a separate **Submit to Community** toggle. Turning that toggle on escalates the flow's visibility to Community regardless of the radio choice. That's what makes it show up in [Flows](/community/flows).

<Note>
  Every published flow gets a public run link (`/app/:slug`) the moment it's published, whatever its Library visibility. "Private" and "Workspace" control who finds it *listed*. Anyone with the link can still run it.
</Note>

A flow already published without Community submission can be promoted afterward: open the flow's own page and use its **Publish to Community** action there (owner-only). There's no separate downgrade action, deleting the flow removes it everywhere, including Community, and its public link stops working immediately.