Nodes/WebApp API/Boolean input
ComfyUI Node

Boolean input

WebApp Boolean input

By MonkeyProof-Solutions-BV·Created 6 months ago·Updated 3 months ago· 2
Boolean input
  • parent
  • value
  • Order + 1
value_in
defaulttrue
order10
advancedfalse
value_from_interface
tooltip

The name sounds like a widget, but the real job of WebApp_Booleaninput is to hand a checkbox to someone who doesn't know what a KSampler is. It's one of the input-definition nodes in the ComfyUI_webapp pack, which lets you describe a web app interface inside your workflow graph instead of in a separate config file. You design the controls in ComfyUI, export the workflow API, and a framework like Simian WebApps turns that definition into a real app with form fields your users click.

So the honest first take: this node does almost nothing by itself. Run it in plain ComfyUI and it's a pass-through - no checkbox magically appears on your canvas. The UI lives in the app framework. What this node does is describe one boolean control and carry the value the user picks back into the workflow.

What it actually is

WebApp_Booleaninput is part of the api/app category in this pack. Like every node in it, its output is a list (the whole pack leans on ComfyUI's list processing, so one control can feed many values). The two inputs that matter most:

  • value_in (BOOLEAN) - the value used when you run the workflow in ComfyUI. Wire this in and the node behaves as a normal graph value.
  • default (BOOLEAN, default true) - the value the web app starts with. This is what your end user sees pre-selected.
  • order (INT, default 10) - where the control sits in its section. Lower numbers float to the top.

The optional parent input attaches the control to a WebApp_Grouping node (tabs, columns, sections) - everything without a parent lands at the app root. The tooltip field is the little hover text the app shows, and advanced (default false) hides the control unless the app is in advanced mode. There's also value_from_interface: a JSON string the app injects to override the value without touching the graph, which you'll almost never set by hand.

The output value (a BOOLEAN list) is what you wire downstream - into an if/else, a switch, or anything that takes a boolean. The second output, Order + 1, is a chain trick: plug it into the next control's order input and controls auto-sequence themselves, no manual numbering.

Installing it

This pack ships with three helper nodes and a pile of api/app controls, so you install once and get all of them:

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

Then restart ComfyUI. Or use ComfyUI Manager → Install Custom Nodes → search ComfyUI_webapp (listed as "WebApp API"). No model downloads, no API keys - dependencies are just pillow and torch, which ComfyUI already has.

Gotchas

One real trap: this pack is written against ComfyUI's newer backend node API (comfy_api.latest, the comfy_entrypoint style), so it needs a recent ComfyUI. If the nodes show up as missing after a clean install, update ComfyUI first - it's a compatibility thing, not a broken pack. And remember: if you want the toggle to actually appear, you need the app framework side of the deal. Without it, you've drawn a checkbox nobody can see.

Categoryapi/app

Inputs (7)

NameTypeDefaultDescription
value_inBOOLEANThis value is used when running the workflow in ComfyUI.
defaultBOOLEANtrueWeb app control default value.
orderINT10Control order in its section. Lowest value at the top. Highest at the bottom.
advancedoptBOOLEANfalseControl is only shown when advanced is True.
value_from_interfaceoptSTRINGTo be used when modifying the workflow API json from an external interface. Note that this string is interpreted as a json string.
parentoptPARENTWeb app parent to add the node to.
tooltipoptSTRINGWeb app control tooltip.

Outputs (2)

NameTypeDescription
valueBOOLEANOutput value.
Order + 1INTOrder number for the next control.