JDCN_EnableDisable

JDCN_EnableDisable takes a boolean switch and outputs the string "enable" or "disable". One input, one output, that's the whole thing. And because the output is typed as * (any), a lot of people assume it actually enables or disables something. Let me save you the confusion: it doesn't. It's a flag emitter - it just turns a toggle into a word.

What it actually does

Input Enable (boolean) → output output, which is the string "enable" when the toggle is on and "disable" when it's off. The output type is * because the author left it flexible, but the value is always one of those two strings.

So where does that fit? Downstream logic nodes that make decisions based on string flags. If you're running a workflow that switches behavior on a word - a prompt condition, a filename component, a router node from another pack that matches on text - this gives you a UI toggle that produces the word it needs. It's the text-flavored sibling of JDCN_BoolInt, which produces the boolean and numeric forms of the same toggle.

A typical pattern: you want to conditionally include something in a filename or a prompt. Toggle Enable, and the output word gets concatenated into the string. Or feed it into a string-matching branch so the workflow takes one path when "enable" and another when "disable".

The honest take

For most people, JDCN_BoolInt is the more useful node of the two - True/False and 1/0 wire into more things than the words "enable"/"disable" do. This node's niche is string-driven logic. If you're new to this pack and just want to turn something on or off, start with BoolInt (or any of the dozens of general boolean nodes); grab EnableDisable specifically when a downstream node genuinely wants those words.

Installing it

Part of ComfyUI-JDCN:

• ComfyUI Manager → Install Custom Node → search JDCN → install ComfyUI-JDCN → restart.
• Or:

cd ComfyUI/custom_nodes
git clone https://github.com/daxcay/ComfyUI-JDCN.git
cd ComfyUI-JDCN
pip install -r requirements.txt

Restart; under 🔵 JDCN 🔵. Only dependency is piexif, no models.

Common issues

The main gotcha is the expectation mismatch: wire it up hoping it gates a whole node on or off, and nothing happens - it just emits a string. There's no state, no latch, no magic. Also, since the output is any-typed, ComfyUI won't warn you if you connect it somewhere that expects a boolean or an image; the string will flow in and probably error downstream. If a node in your workflow needed a real boolean, feed it from JDCN_BoolInt instead. For what it is - a toggle-to-word converter - it does the job cleanly.