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

# Cloud Export Node

> Publish finished media out of Flowy to Google Drive, Dropbox, or your own device.

The Cloud Export node is a terminal publishing node: wire finished media into it, pick a destination, and sync. It's the one node type with no outputs. It generates nothing, it only publishes what's already connected.

## Connect it

Cloud Export accepts images, video, audio, 3D models, vectors, [Flam](/canvas/nodes/flam) clips, [Router](/canvas/nodes/router) fan-in, and the output of any [image tool](/canvas/image-tools/overview). Each connected input becomes its own row in the node, tracking its own sync state, so the header reads something like "3/5 synced" as items finish.

## Destinations

Pick one destination per node:

| Destination  | What it publishes to                                     |
| ------------ | -------------------------------------------------------- |
| Google Drive | A folder you pick with the Google Drive picker           |
| Dropbox      | A folder you browse to in your Dropbox                   |
| Local        | Downloads every connected output straight to your device |

Provider destinations (Drive, Dropbox) require that provider to already be connected under **Settings → Integrations**. **Local** needs no connection at all. It's the fastest way to pull a batch of generations off the canvas and onto your computer.

## Publish

Wire in everything you want to send out, choose a destination, and click **Sync**. Common patterns:

* Publish a batch of generations to a shared Drive folder for review.
* Download every connected output at once via Local, instead of saving each result individually.

<Note>
  Cloud Export is a terminal node. It has no outputs, so nothing downstream can connect from it. It's the end of a pipeline, not a step in the middle of one.
</Note>