Button

Every other control node in the ComfyUI_webapp pack hands a value downstream. This one hands a click. WebApp_Button defines a button in the web app your workflow becomes - the thing your user presses to trigger something - and it's the rare node here with no data output at all. If you wire it expecting a trigger signal, you'll be looking for a wire that doesn't exist.

That's not a bug. The button's only backend input is app_event_name: a string naming the event the app framework should fire when the button is clicked. The pack doesn't ship the framework - you pair it with something like Simian WebApps, which reads your exported workflow API and renders the actual UI. So app_event_name is a contract with that framework: type the event name the app knows how to run, and clicking the button triggers it.

The two inputs that matter

• app_event_name (STRING) - the web app event to execute on click. This is the whole reason the node exists.
• order (INT, default 10) - control position in its section; lower numbers first.

Both parent (attach to a WebApp_Grouping) and tooltip are optional and behave like everywhere else in the pack. The single output is Order + 1, the auto-sequence chaining slot - wire it to the next control's order input and positions take care of themselves. That's the only way this node affects your graph data at all.

The honest "why would I use this"

If you're building a public or shared workflow app - a form where a non-ComfyUI person uploads an image, picks options, hits "Generate" - you want a visible action button that says go, and WebApp_Button is how you declare one. If you're running a workflow for yourself in the ComfyUI canvas, skip it entirely: it does nothing there. It's pure app definition.

Installing it

Same one-time install as the rest of the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/MonkeyProof-Solutions-BV/ComfyUI_webapp

Then restart ComfyUI, or use ComfyUI Manager and search ComfyUI_webapp ("WebApp API"). No models, no extra dependencies beyond pillow and torch.

Gotchas

The two things that trip people up: (1) there's no value output, so don't hunt for one - the button's effect lives entirely in the app framework, and (2) this pack targets the newer backend node API (comfy_api.latest), so a stale ComfyUI won't load it. Update ComfyUI before you blame the button.