Flux Config (BFL)

Flux Config (BFL) doesn't generate a single pixel. What it does is hand every other node in the ComfyUI-FLUX-BFL-API pack its credentials. This is the node you'd reach for when you don't want to edit config.ini - when you're sharing a workflow, running two accounts, or hitting the regional endpoints that finetuning demands. In ComfyUI terms it's a "config provider": you wire its single output into the config socket on any generation, tool, finetune, or utility node in the pack, and that node uses your settings instead of the file.

How it works

Every generation node in the pack accepts an optional config input of type BFL_CONFIG. If you don't wire one, the node reads config.ini from the pack's directory and uses whatever X_KEY and BASE_URL you've stored there. Wire a Flux Config (BFL) node in, and its values override the file for that one node - a per-node key, per-node endpoint, per-node region. The override wins, the file stays untouched, and workflows stay shareable without leaking your key into someone else's copy.

The inputs

• x_key - your BFL API key, from api.bfl.ai. Paste it in and it's used instead of config.ini's key. (Leave it blank and the file key is used.)
• base_url - defaults to https://api.bfl.ai/v1/. This is where you'd point at a proxy, a reseller, or a custom gateway if you ever need one.
• region - none, us, or eu. This one matters more than it looks: the finetune endpoints are regional (api.us.bfl.ai, api.eu.bfl.ai), and the default global URL doesn't serve finetune routes at all. The moment you touch Flux Finetune Status, Flux My Finetunes, or the finetuned-generation nodes, set this to your region or those calls will fail.

The output is a single BFL_CONFIG object you can split to as many nodes as you like - one config node can feed an entire workflow.

Installing it

Same one-pack install as the rest:

cd ComfyUI/custom_nodes
git clone https://github.com/gelasdev/ComfyUI-FLUX-BFL-API.git

Restart ComfyUI and it's in your node list. No extra dependencies beyond what ComfyUI ships.

Where people get burned

• Forgetting it entirely. Nothing breaks - the pack silently falls back to config.ini, which is the intended behavior, but it means your carefully-entered key in the config node does nothing because you never wired the config socket.
• Finetune calls failing with region defaulted to none. This is the classic one. The finetune routes don't live on the default endpoint. Set region to us or eu (matching where your finetune was created) and the calls start working.
• Assuming it's global. It overrides per node. Wire it only to the nodes you want to reconfigure; anything left unwired keeps using the file.

The only gotcha that bites people the other direction: the pack ships with a placeholder X_KEY = your-key in config.ini. If you never set a real key or a config node, every call 401s. This node is your cleanest fix for that - drop it in, paste the key once, done.