Playbook Render Result

Playbook Render Result closes the loop. Where the render-pass nodes stream from Playbook3D's cloud into ComfyUI, this one streams back: it takes the image your workflow produced, uploads it to Playbook's servers, and returns a shareable URL as a string.

That's a genuinely useful shape if you think about how this pack is meant to be used. Playbook3D is a cloud 3D render service that hands you beauty, depth, mask, and outline passes to retexture or restyle. Once your ComfyUI pipeline is done, the result is a new image of a 3D scene - and in Playbook's world, that image belongs back in their app, composited onto the render or shared from the platform. This node is the return address. It's the OUTPUT_NODE of a Playbook workflow, the thing you put at the end instead of a plain Save Image.

How it works

Two required inputs: images (an IMAGE) and api_key.

The flow is three API calls:

1. Exchange api_key for a user token at accounts.playbook3d.com/token-wrapper/get-tokens/<key>.
2. Ask for an upload URL (get-upload-urls) and PUT your image - converted to a PNG in memory - to it.
3. Request download URLs and return the resulting save_result URL as the output URL.

Unlike the single-frame render-pass nodes, this one does not fail quietly. A bad or missing key raises "API Key not found/Incorrect", and any upload problem raises "Error with uploading Result". That's actually the right call for an output node - you want to know when your result didn't make it to the cloud, not silently ship nothing.

Two implementation notes worth knowing. The image goes up as a PNG, so if you feed it a batch (multiple frames), the node squeezes it down to a single frame before saving - np.squeeze on the batch dimension, then the first remaining image is encoded. A multi-frame batch won't upload as multiple files; keep it to one image per node, or chain multiple nodes. And because it's marked as an output node, ComfyUI shows the returned URL in the UI after the run.

Install

Same as the rest of the pack. ComfyUI Manager → Playbook Nodes, or:

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

Restart ComfyUI. No models, no extra dependencies - requests and PIL are already in ComfyUI. You need the Playbook3D API key from beta.playbook3d.com; there's no way around it, because without valid auth the upload simply cannot happen.

Troubleshooting

The two errors above are your whole diagnostic surface. "API Key not found/Incorrect" means the token exchange failed - check the key is current and not copy-pasted with whitespace. "Error with uploading Result" wraps any failure in the upload or download round trips, and the cause is usually a server hiccup or a quota issue on the Playbook side; retry the queue. And remember the single-image squeeze: if your images input is a batch, only the squeezed single frame gets uploaded, so size your input accordingly or you'll wonder where the other frames went.