Skip to main content
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.
Flows

The Flows gallery in Creator Studio

In the product this is called a Flow. The underlying REST resource is still /v1/apps, and every endpoint in the API reference uses apps and appId.

​
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:

Publishing

Mark inputs and outputs on a canvas project, fill in the publish form, and update it later.

Playground

Run a flow from its public page: fill in the form and watch the result come in.

Requests

Every run of a flow, and the detail view for one run’s inputs, output, and cost.

Recipe

A read-only diagram of the flow’s underlying node graph.

API

This flow’s own API reference, prefilled with its real input names.
Last modified on August 29, 2026