> ## 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.

# Flows

> Published flows other creators have shared. Open one to try it, no canvas required.

**Flows** (`/community/flows`) is the community's catalog of published apps: one-purpose tools other creators have built on a canvas and shared publicly, like "Headshot generator" or a branded caption maker.

<Frame caption="Published flows you can run">
  <img src="https://mintcdn.com/flamapp/d-IQVAHPd1A_gxXA/images/community/flows.png?fit=max&auto=format&n=d-IQVAHPd1A_gxXA&q=85&s=d3418fa1b2b6f35bad406c3cdecb0b70" alt="Flows" width="2880" height="1800" data-path="images/community/flows.png" />
</Frame>

## Browse flows

Flows display as a grid of 16:9 tiles, each showing the flow's preview, title, category, and run count. Search narrows the grid by title, description, category, or tags; unlike Templates, flows carry their own category taxonomy (Essentials, Marketing & Ads, Video & Animation, and so on), separate from the community's template categories.

## Open and run a flow

Click a tile to open the flow at its public page, `/app/:slug`. From there you can run it with your own inputs without opening a canvas at all. The flow's author has already wired the workflow, so you only supply what it asks for.

<Tip>
  Flows are also runnable over the API. See [Run a flow](/api/running-apps) for the equivalent request/response flow if you're integrating rather than clicking through the UI.
</Tip>

## Flows vs. templates

Both surfaces let you build on someone else's work, but they hand you different starting points:

* A **template** ([Templates](/community/templates)) is a canvas you remix. It becomes your own editable project.
* A **flow** is a packaged tool you run. You get its output, not its canvas.

Community also shows a short Flows rail on [Explore](/community/explore), with a "Browse all" link through to this page.