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

> Publish a canvas project as a runnable tool with a typed input form, so anyone can run it without opening the canvas.

A **Flow** takes a canvas project you've built and turns it into a standalone tool: a form of inputs in, a result out, at a public link anyone can open and run. Instead of sharing a canvas and asking someone to understand your node graph, you mark which nodes are inputs and which are outputs, publish it, and hand over a link to `/app/:slug`: a page with its own Playground, docs, and API, styled around your flow rather than the canvas editor.

<Frame caption="The Flows gallery in Creator Studio">
  <img src="https://mintcdn.com/flamapp/d-IQVAHPd1A_gxXA/images/creator-studio/flows.png?fit=max&auto=format&n=d-IQVAHPd1A_gxXA&q=85&s=e23ae25f71b95ce2c360c240b15d4fba" alt="Flows" width="2880" height="1800" data-path="images/creator-studio/flows.png" />
</Frame>

<Note>
  In the product this is called a **Flow**. The underlying REST resource is still `/v1/apps`, and every endpoint in the [API reference](/api/running-apps) uses `apps` and `appId`.
</Note>

## How it fits together

* **Publishing** happens inside the canvas editor, in the App Builder sidebar: pick which nodes are inputs and outputs, fill in a title/description/category, and publish.
* **Running** happens on the published flow's own page at `/app/:slug`, the Playground tab, either by a visitor filling in the form, or by calling the REST API directly.
* Every run is billed in credits to whoever's running it, and is recorded so it can be revisited later.

## The flow page

A published flow's page has its own tabs:

<CardGroup cols={2}>
  <Card title="Publishing" icon="rocket" href="/flows/publishing">
    Mark inputs and outputs on a canvas project, fill in the publish form, and update it later.
  </Card>

  <Card title="Playground" icon="play" href="/flows/playground">
    Run a flow from its public page: fill in the form and watch the result come in.
  </Card>

  <Card title="Requests" icon="clock-rotate-left" href="/flows/requests">
    Every run of a flow, and the detail view for one run's inputs, output, and cost.
  </Card>

  <Card title="Recipe" icon="diagram-project" href="/flows/recipe">
    A read-only diagram of the flow's underlying node graph.
  </Card>

  <Card title="API" icon="code" href="/flows/api">
    This flow's own API reference, prefilled with its real input names.
  </Card>
</CardGroup>