应用参数管理
AppParams and the WeChat app platform hiding inside this pack
AppParams (应用参数管理, "app parameter management") is the node that lets you publish a workflow as a chat app. It's part of the lam pack's hidden second life: alongside the image utilities, this pack contains a whole mini-platform that turns ComfyUI workflows into applications served over WeChat-style messengers - you register an app, define its input parameters, and the backend exposes the workflow behind a chat interface.
I'll be straight with you: if you didn't come here for that platform, this node is a dead end. It's the registration form for the app system, not a utility you slot into everyday workflows. But it's worth understanding what it does so you can spot the system it belongs to (and so you don't install it into a graph expecting image output).
How it works
The node's real work happens through backend endpoints the pack registers on ComfyUI's server. When you fill in the node and run the workflow, it calls /lam/setAppParams, which writes the current workflow JSON to config/workflow/<appName>.json and records the app in the pack's configuration - name, type, description, and the list of parameter widgets that should be exposed to the end user. The appType selects the presentation layer: default, paint-board (a drawing surface), or picture-book (a page-flip viewer). Downstream, the pack's chat frontend (the WeChat integration configurable in config/weChat.yaml.template) maps incoming messages to the app and runs the workflow with the user's parameters.
Inputs and output
appName- aSTRINGname for the app; becomes the config filename.appType-default/paint-board/picture-book.appDesc- description text shown to users.- Outputs: none. It's a side-effect node - it writes config and reports success through the backend.
Install
In yanlang0123/ComfyUI_Lam - Manager search "ComfyUI_Lam", or:
cd ComfyUI/custom_nodes
git clone https://github.com/yanlang0123/ComfyUI_Lam
restart. Here's where the README's warnings actually bite: this pack's full app platform expects the "modify files" step (修改文件.bat / 修改文件.sh) that runs changeRestore.py, which patches ComfyUI's own server.py and comfy/cli_args.py to add extra server flags (--cluster, --isMain, --basePath, etc.). That's a modification of core ComfyUI files - do not run it casually, and know that 还原文件.bat (restore) reverses it. For the standalone app system you'll also want the pack's config directory populated and its heavier requirements.txt installed (it pulls in a lot).
The honest take
This node only makes sense inside the pack's app-publishing ecosystem, which is Chinese-first, expects a server deployment, and is a whole project on its own. If you found this page because a workflow is asking for AppParams, you're either building one of those apps or you loaded a workflow from the pack's ecosystem. If it's the latter and you don't want the platform, remove the node and the config it wrote - the workflow itself is often runnable without the app layer. It's a real feature, just not a general-purpose one.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| appName | STRING | — | |
| appType | COMBO | 3 options: default, paint-board, picture-book | |
| appDesc | STRING | — |
Outputs (0)
No outputs