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

# Router Node

> Bundle fan-out and fan-in connections into one hub that stays wired as the canvas changes.

The Router node (<kbd>⇧</kbd> <kbd>R</kbd>) is an n↔n broadcast bus: wire multiple sources into it, and it fans everything out to multiple targets. Every content node type can connect to and from a Router. It's the one node designed to sit in the middle of a busy graph.

## Transparent to generation

A Router doesn't hold or transform content itself. A node downstream of a Router resolves the Router's real upstream sources exactly as if they were wired to it directly. The Router is invisible to the generation itself, it only manages the wiring.

## Use it to

* **Compare variants**: fan one prompt or reference out to several Image or Video nodes with different settings, and judge the results side by side.
* **Share references**: feed the same set of references into many targets without drawing every edge by hand.
* **Keep wiring stable**: the fan-out survives swapping or deleting a source, so a busy graph doesn't collapse mid-iteration.
* **Bundle a messy fan-out into one hub**, instead of a dozen crossing edges, route them all through one Router node.

## Connect it

A Router accepts every content node type as an input, and outputs to every content node type plus [Cloud Export](/canvas/nodes/cloud-export), but it never carries Cloud Export as an input, since that's a terminal node with no output of its own.

Some nodes only accept a Router as an input: [Sketch](/canvas/nodes/sketch) is the notable example, since it has no toolbar button and instead usually arrives via the AI assistant or by connecting from a Router's output.