Workflows

The ComfyUI workflows your project can run -- the ones that ship with Ordinary Animator, and your own.

The Workflow Library is a project view: the ComfyUI workflows this project can run, and where they come from. Which of them it actually runs for an operation belongs to a visual style.

The operations you run draw on two places: your project's own workflows first, then the ones that ship with Ordinary Animator. The shipped ones are always available and always the latest version -- there is nothing to copy in, and a fix to one reaches your project straight away. Your project's own are the ones you import, the ones the assistant makes, and the snapshots you save of shipped ones.

If your project holds a workflow with the same name as a shipped one (a copy saved by an earlier version, or an import you named that way), yours is used wherever the shipped one would have been. Remove it and the shipped version is back. A snapshot (see below) does not do this: it keeps your project on the latest shipped version and holds the old one beside it.

Workflows and visual styles

A workflow runs one model at one build, and performs one or more operations -- "Remove Background" with RMBG 2.0, or one Qwen Image Edit graph that does six different edits. A workflow card does not say which look uses it: a visual style lists recipes, and a recipe names the workflows its steps run. The Visual styles page is where you see and change that.

A workflow that is part of a recipe your styles list is the one that recipe runs. Where the catalogue holds the same model packaged another way, the recipe on a style's list offers Change build.

When a workflow cannot be used

Every workflow is checked the moment it enters your project, whichever way it got there: imported from your machine or from Comfy Cloud, copied in from the OA Catalog, made by the assistant, or re-imported as a new version. A workflow that passes says nothing about it -- that is the normal case and a badge on every card teaches nobody anything.

When you import a workflow, you see its full report before anything is saved: every problem, in plain terms, with what to do about it -- The OA Workflow Metadata note is missing, This workflow file is not valid JSON. A report with an error has no Import button, only Cancel. Fix the workflow in ComfyUI, export it again and import the new file. A report with only warnings imports, and the warnings stay visible. If the note is the problem, copy the workflow from OA again (Copy to ComfyUI keeps the note) or add the note as described in Workflow Metadata. "Import all" does the same for each file: one with an error is left out, and the message says why.

A workflow that was saved as invalid before this rule, or that became invalid when you restored an older version, sits under an Invalid heading at the bottom of your Project Library with a small issue chip on it. Open the card's menu and choose Inspect, and it opens with what is wrong at the top. It is not offered anywhere until it is fixed -- not in an operation's model list, and not by the assistant, which will say why if you ask about it by name. You can still open it, inspect it and delete it.

The four sources

The left of the page selects where you are browsing:

  • Project Library -- your project's own workflows: ones imported from your computer or Comfy Cloud, copies you saved of shipped ones, and ones the assistant made.
  • OA Catalog -- the workflows that ship with Ordinary Animator. They are available to every project already.
  • 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.

Each one starts with a sentence saying what it holds, and has the same filter row as the list you choose an operation from: type part of a name to narrow the cards (Remove finds Remove Background), and in Project Library and OA Catalog narrow further by what the workflow Takes, where it Runs on and which Model it uses. Local Comfy and Comfy Cloud have the name search only, because a file you have not imported yet has not been read. What you type stays when you switch between the four, so you can look for the same workflow in each.

Adding and updating workflows

Upload workflow file, above the Project Library cards, is the usual way to add your own ComfyUI workflow. If the Project Library already has a workflow with the same filename, you are asked whether to overwrite it; the version it replaces stays in that workflow's version history. Download in a Project Library card's menu saves the workflow file back to your computer.

Local Comfy and Comfy Cloud list the workflows you can import from those places, each with Import to Project in its menu. Refresh List at the top right re-reads the list; it changes nothing in your project. Its menu opens that source's settings and has Import all from Local Comfy (or Import all from Comfy Cloud), which brings in every workflow whose filename starts with oa- from that one place. Only oa- files are imported, so other workflows you keep there are left alone. Importing adds and updates; it never removes anything from your project. The OA Catalog is not part of this: shipped workflows are not copied into projects.

You do not have to add a shipped workflow to use it. Every OA Catalog workflow is already available to every project, always at the latest version, and a fix Ordinary Animator makes reaches your project with nothing for you to do.

You can keep one exactly as it is today if you ever need to, but you don't have to. Snapshot to project, in the menu on an OA Catalog card, saves a copy into Project Library. The copy keeps the shipped workflow's filename with the day's date on the end, for example oa-catalog-i2i-remove-bg-20260927.json (a second snapshot the same day ends in -2), so you can see where it came from and when.

A snapshot does not replace the shipped version: your project keeps using the latest one. The snapshot is listed beside it in the operation list, where you can pick it for a single run.

Every card shows its filename in small print under its name.

There is one shipped version of each workflow and no version numbers to choose between. A snapshot is how you hold a workflow still -- newer workflows sometimes need newer ComfyUI releases, so a version number on its own would not be enough to promise a workflow still ran.

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.

A workflow you built yourself has a few things to get right before it behaves like the catalog ones. OA Workflow Metadata is the note that gives it a name and a menu to appear in, App inputs and outputs is what the platform is allowed to fill in, and Adding your own workflow covers the nodes -- which loaders to use for images, video and audio, and whether the nodes exist where you intend to run it.

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.

Changing a workflow in ComfyUI and bringing it back

This is the usual way to tune something: copy a workflow out to ComfyUI, change a setting, run it there until you like the result, then import it back.

What comes back is your workflow, not a replacement for the shipped one. It keeps doing the same job for the same model, so it appears under that model in the operation list -- as a second form of it, beside the shipped one, not as a separate model and not as a new operation. You can run it exactly as you run anything else.

It is named after the workflow it came from with -- custom on the end -- Upscale 4x (ClearReality V1) -- custom. A second copy of the same one is -- custom v2, a third -- custom v3, so several attempts at the same tune can be told apart. The suffix is only added when the name would otherwise be the same as one already there. Rename it to anything you like; it stays linked to where it came from.

Ordinary Animator never guesses what a workflow is. If you deleted the OA Workflow Metadata note in ComfyUI, or the file is an old export from before the note existed, the import report says the note is missing and the file is not imported -- see When a workflow cannot be used. The note is what the workflow does, so change the operation in the note and the workflow does what the note says.

A workflow nothing recognises is not filed under any model. It keeps the name you gave it and sits in the Custom workflow group at the end of its operation list, which is where anything you built from scratch lives. A workflow file is never an operation of its own.

Inspecting a workflow

Inspect shows what a workflow declares and what it would cost you to run, whether it is one of yours or one from the OA Catalog you have not copied in:

  • Requirements -- the build's precision, how much there is to download, and how much video memory it wants, where those are recorded. Nothing is guessed: a workflow whose figures nobody has recorded simply has no Requirements section.
  • Runs on -- your own Local and Cloud answer, in the same words the model list uses: Local: ready, Local: not checked, Cloud: ready. The Local clause is checked live against your ComfyUI when it is running. It is about your machine, so a teammate opening the same workflow sees their own line.
  • Its inputs and outputs, its OA Workflow Metadata, and its Version history -- every version of it this project has saved, newest first.

Going back to an earlier version

Every time you upload a workflow over one your project already has, the file it replaces is kept. Version history in Inspect is the only place those earlier files appear, and the only place you can act on one: press Restore beside a past version and your project goes back to that file. Nowhere else in Ordinary Animator asks you to choose a version -- picking a workflow always means picking the one your project is on now.

Restoring adds the older file to the top of the history rather than winding it back, so the version you were on is still there and you can restore that one just as easily. Anything that runs this workflow keeps running it, and will now run the restored file.

Asking the assistant what is wrong with one

If a workflow of yours will not run, ask in chat. "I uploaded a workflow and it doesn't work -- what's wrong with it?" is enough, and so is "my last render failed, why?" -- the assistant can find the workflow behind your most recent failed job without you looking up anything.

You get an answer in plain terms about your own file: that it is missing its OA Workflow Metadata note, that one of the inputs points at a node that is not there, that it uses a node Comfy Cloud does not have. Where a check could not be run -- node settings need a local ComfyUI connected, for instance -- the assistant says so rather than reporting a clean bill of health it cannot back up.

Telling you what is wrong is the whole answer. The assistant will offer to fix it, but you never have to accept a change to hear the diagnosis, and nothing is installed or changed unless you say so.

Workflows the assistant made

Most models in the catalog have no workflow of their own, and you do not have to build one. Ask for a model that has none -- "make a workflow for Real-ESRGAN", or just "try the other upscalers on this image" -- and the assistant makes one, usually by copying a workflow that already runs a model of the same kind and pointing it at the new model's file. See The AI Assistant for how that works and what it does when there is nothing to copy from.

What lands in your Project Library is a workflow like any other. It carries the name the assistant gave it (which names the model, so two upscales are never confused for each other), it appears in the same pickers, a recipe can use it the same way, and inspecting it shows its inputs, its models and its version history exactly as for a workflow you imported yourself. Its entry also records which workflow it was made from and which model it was made for, so you can always see where it came from.

It goes through the same checks as an imported workflow. One that does not pass lands under Invalid like any other, where you can see what is wrong -- and the assistant will not offer it to you until it does pass.

Where to go next