Nodes/Quality of Life Nodes for ComfyUI/ComfyDeploy API Boolean Parameters (Soze)
ComfyUI Node

ComfyDeploy API Boolean Parameters (Soze)

Bundle toggles for a ComfyDeploy run

By SozeInc·Created 2 years ago·Updated 5 days ago· 10
ComfyDeploy API Boolean Parameters (Soze)
    • api_parameters
    more_parameters
    name_1
    boolean_value_1false
    name_2
    boolean_value_2false
    name_3
    boolean_value_3false
    name_4
    boolean_value_4false
    name_5
    boolean_value_5false

    Quick context if you haven't run into it: ComfyDeploy is a separate hosted platform (unrelated to comfy.icu) that lets you take a ComfyUI workflow and expose it as an API - deploy the workflow, call their endpoint, and it kicks off a run using whatever input overrides you pass along, often with a run_id handed back for anything that isn't instant. If your deployed workflow exposes boolean toggles as external inputs (upscale: yes/no, use a second pass: yes/no), those need to travel as parameters in that API call. Typing that payload by hand every time is exactly the kind of busywork this pack exists to remove - this node gives you five named boolean slots and bundles them into one parameter string.

    How it works

    Each of the five slots is a name_N (the parameter's key) paired with a boolean_value_N (true/false). Fill in as many as you need - leave a name blank to skip that slot. more_parameters is a free-text field for anything the five named slots don't cover: additional parameters, non-boolean values, or raw text you're building elsewhere and want appended. Everything gets combined into api_parameters, a single string meant to be handed to whatever node in your graph actually fires the request against ComfyDeploy's API.

    This node itself makes no network call - it's pure string assembly. The pieces of this pack that actually talk to ComfyDeploy's API need CD_API_KEY set as an environment variable (or in a .env file at the repo root, per the README); this one doesn't touch the network, so it doesn't need the key, but you'll need the rest of the ComfyDeploy-flavored group configured for the overall pattern to do anything.

    The inputs and outputs that matter

    • name_1name_5 / boolean_value_1boolean_value_5 (all optional) - up to five named boolean parameters.
    • more_parameters (optional, STRING) - anything beyond the five slots.

    Output: api_parameters (STRING) - the assembled payload piece.

    How to install it

    ComfyUI Manager → search "ComfyUI_Soze" → install → restart. Manual:

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

    then restart. This node needs no credentials itself; set CD_API_KEY per the README only for the nodes in this group that actually call ComfyDeploy.

    Common issues & troubleshooting

    The exact serialization this node produces - a JSON object, a query string, something matching ComfyDeploy's own parameter schema specifically - isn't spelled out in the node's schema itself. If whatever consumes api_parameters downstream rejects it or the boolean doesn't land where you expect on ComfyDeploy's side, route api_parameters into a text preview node and compare it against ComfyDeploy's own API documentation before assuming this node is the broken link.

    If a toggle isn't showing up in the output at all, check that its name_N field is actually filled - an empty name is almost certainly what causes that slot to be skipped, since there's no separate "enabled" flag per slot beyond the name being present.

    CategorySoze Nodes

    Inputs (11)

    NameTypeDefaultDescription
    more_parametersoptSTRING
    name_1optSTRING
    boolean_value_1optBOOLEANfalse
    name_2optSTRING
    boolean_value_2optBOOLEANfalse
    name_3optSTRING
    boolean_value_3optBOOLEANfalse
    name_4optSTRING
    boolean_value_4optBOOLEANfalse
    name_5optSTRING
    boolean_value_5optBOOLEANfalse

    Outputs (1)

    NameTypeDescription
    api_parametersSTRING