InstaSD API Input - Boolean

There is no API call happening here. InstaCBoolean takes a boolean, passes it through, and calls itself an "InstaSD API Input". The point is that this node is a flag - one of the inputs InstaSD's API builder recognizes so you can expose it to the people using your published workflow.

The context: InstaSD (instasd.com) is the service that turns a ComfyUI workflow into a public one-page app or API endpoint. When you build one, you decide which inputs end users can fiddle with. These InstaSD/API_inputs nodes are how you declare them. A boolean is the most useful knob to hand over: "face fix on or off", "use the upscaler or not", "high quality vs fast". The person on the other end gets a checkbox or toggle, and your workflow just receives True or False.

What you set

• boolean - defaults to True. Flip it, wire the output into anything that takes a BOOLEAN, and the value flows through unchanged.

That's genuinely the whole interface: one input, one output, both named boolean, type BOOLEAN. Internally the node just returns what it got - the source is a few lines. If you're not publishing through InstaSD, this is nothing but a labelled pass-through and you can skip it. If you are, it's how a toggle becomes a checkbox on your demo page.

A small tip since it applies here: keep the node's title descriptive. The InstaSD builder surfaces these by title, so a node titled "Face Detailer" reads a lot better in the published UI than a bare "boolean" ever will.

Install

Standard for this pack:

cd ComfyUI/custom_nodes
git clone https://github.com/WaddingtonHoldings/ComfyUI-InstaSD

Restart ComfyUI, or use ComfyUI Manager and search for "InstaSD". The pack installs boto3, Pillow, requests, and numpy; nothing here needs a model download or an API key.

Gotchas

• If nothing visibly "happens", you're not broken - the node is doing its one job (passing the value). The magic only appears once the workflow is deployed through InstaSD.
• It's easy to wire a boolean into an INT input by accident; ComfyUI is lax about this and you'll just get a confusing 1/0 or a silent mismatch. Match types, or the demo page will behave oddly.