DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to turn a complex workflow into a simple app or API with Comfy UI

Use App Mode and the local API to run a saved workflow from a form or a production pipeline.

  • Content
  • Advanced
  • 120 minutes
  • From the README
  • Any agent

Authorization notice. Comfy UI is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer or operations lead who wants non-technical teammates or a pipeline to run a fixed generation workflow without opening the node graph.

The problemComplex node graphs are hard for people who only need to change one or two inputs, and pipelines need a stable way to call the same workflow.

The outcomeA workflow that is available through App Mode for simple use and through the local API for automated runs.

What you need first

  • A Windows or macOS computer for the desktop app, or a Windows, Linux, or macOS machine with a supported GPU for the manual install
  • A GPU with enough VRAM for the model you pick (the README says large models can run on as little as 4GB VRAM with 8GB RAM)
  • Disk space for the model files you choose to download
  • Optional: a Comfy Cloud account or partner node access for paid hosted models

Steps

  1. Open the workflow you want to share and save it with Ctrl + S as JSON.
  2. Enable App Mode and choose which inputs (such as prompt and seed) appear in the simple UI.
  3. Start Comfy UI locally with python main.py and confirm the local API is reachable on the server address shown in the log. (inferred, check the README)
  4. Send the saved workflow to the local API from your application, changing only the inputs you exposed.
  5. Collect the output files and check them against a test prompt before you hand the app to users.

Prompt for your agent

Using the ComfyUI repo at https://github.com/Comfy-Org/ComfyUI, save the workflow <workflow name> as JSON, expose its prompt input through App Mode, and submit it to the local API with the prompt <prompt text>. Expected output: one generated file returned by the API and the saved workflow JSON. Verify the API response status and that the output matches the prompt.

Caveat. The README mentions a local API and API endpoints for production pipelines but does not document the endpoint paths or request format, so check the official docs before you write the integration.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page