Workflows

Your project's collection of ComfyUI workflows, and the libraries you copy them in from.

The Workflows view is a project view. It holds the ComfyUI workflows this project can run, and lets you copy more in from a library.

Your project's collection is what your recipes draw on. Copying a workflow in is the deliberate step that makes it available -- much like turning on a model on the AI Models view. Everything in a library is complete and ready to run, so anything you copy in works as it stands.

The four sources

The left of the page selects where you are browsing:

  • Project Library -- what this project already has. These are the workflows your recipes can use.
  • OA Catalog -- the workflows that ship with the platform. Copy one in to use it.
  • Local Comfy -- workflows in a folder on your own machine. You pick the folder; your browser asks permission once.
  • Comfy Cloud -- workflows saved in your Comfy Cloud account.

Adding and updating workflows

From the OA Catalog, each workflow shows what your project has:

  • Add to Project -- it is not in your collection yet.
  • Upgrade to vN -- your copy is older than the catalog's. You choose the version; upgrading is never automatic, so a workflow you rely on cannot change under you mid-shoot.
  • Reinstall -- you already have the current version, and want a clean copy.

Import from Workbench brings several in at once, reconciling what you have against Comfy Cloud, your local folder, and the catalog together. Where the same workflow exists in more than one place, the Comfy Cloud copy wins and the others fill gaps.

Single workflows can also be imported from Local Comfy or Comfy Cloud, and checked before they land: Ordinary Animator reads the workflow and tells you what it will be able to fill in.

Moving a workflow between cloud and local

Copy to Comfy Cloud and Copy to Local move a workflow from your project into the place you generate. A workflow may exist in versions tuned for where it runs -- one for Comfy Cloud, one for your own machine using a smaller build of a model -- and the right one is chosen for you at run time.

Inspecting a workflow

Selecting a workflow shows what it declares: its inputs, which models it uses, and its version history. This is also where you check whether a workflow's models are ones your project has turned on -- a workflow whose models you do not have will not appear in a recipe step's dropdown until you enable them.

Where to go next