Playbook Boolean (External)

The name says "External," which sounds like it's going to phone home or open a socket. It doesn't. Playbook Boolean is a plain checkbox that outputs a true/false value - the "external" part is about who drives it, not about any network call happening on your machine.

Playbook Boolean ships in the Playbook Nodes pack, the ComfyUI side of Playbook3D, a cloud 3D rendering service. Their pitch is that you build or render a 3D scene in their web app, and the render passes stream into your ComfyUI workflow for retexturing, style transfer, or whatever you're cooking with IP-Adapter and ControlNet. The "External" nodes are the reverse channel: when you run a workflow on their platform, their web UI injects values into these nodes. Your checkbox on their site becomes a real ComfyUI boolean, and your workflow reacts to it. Locally, they're mostly just passthroughs.

What it does

Three inputs, one output:

• id - a string identifier, default "Node ID". This is the binding key the Playbook3D platform uses to match the node to its control in the web UI. Locally it does nothing.
• label - the human-readable name shown in their UI. Also inert locally.
• default_value - a boolean, default off. This is the actual output.

The output, Boolean, is exactly default_value. That's the whole mechanism: parse_boolean returns what you typed. If you're running this on your own machine, it's a glorified light switch - useful for toggling a branch in the graph, but you could get the same result from any number of utility packs. Its real purpose is being a control surface when the workflow runs in Playbook3D's cloud, and nothing about that requires an API key from you.

Install

The pack is a standard custom node install. Either search for Playbook Nodes in ComfyUI Manager and install it, or:

cd ComfyUI/custom_nodes
git clone https://github.com/playbook3d/playbook3d-comfyui-nodes

Then restart ComfyUI. No models to download, no requirements.txt to satisfy - the node itself is a few lines of Python. Only the render-pass nodes (Beauty, Depth, Mask, Outline) need a Playbook3D API key from beta.playbook3d.com; the utility nodes like this one never touch their servers.

Troubleshooting

Honestly, there's not much to break. If the node outputs false when you expected true, you changed the wrong widget or forgot the toggle. One thing people trip on: if you wire this into a workflow that someone else built for the Playbook3D cloud, the id matters - two nodes with the same id on their platform can fight over the same control. Leave the defaults if you're experimenting locally and you'll be fine.