⚙️ HiTem3D Config
The boring node that makes every other HiTem3D node work
- config_status
- config_data
No downloads, no flashing lights, no 3D magic. HiTem3D Config is where you type your API keys so that the HiTem3D Generator and Downloader actually get permission to talk to the service. It's the least glamorous node in the pack and the one you'll almost certainly touch first, because nothing else works until it does.
HiTem3D is a paid cloud API for image-to-3D mesh generation - your GPU never sees the model. That means the whole pack is gated behind a pair of credentials: an Access Key (ak_...) and a Secret Key (sk_...) from your hitem3d.ai account. This node is the polite way to give them to ComfyUI instead of hand-editing a JSON file.
How it works
The node holds your credentials in memory for the current session and can optionally write them to the pack's config.json so every future run picks them up automatically. You get two strings out:
config_status- a human-readable message telling you whether the config was accepted, saved, or is still missing (it helpfully refuses to store the literal placeholdersYOUR_ACCESS_KEY_HERE).config_data- a JSON string of the whole config, which you can pass into the Generator'sconfig_datainput if you want to wire credentials through the graph explicitly.
The two checkboxes are where people get confused, so:
save_config-truewrites the keys toconfig.jsonon disk.false(default) keeps them in memory only. For a workflow you're going to publish or share, leave it off so you don't leak your keys in a file that gets exported.override_config- tells the other nodes to prefer this runtime config over whatever's in the file. Useful when you're testing a second account without clobbering your saved one.
What a beginner actually does
Simplest reliable path: open the node, paste both keys, flip save_config to true, and queue the workflow once. From then on, the Generator and Downloader read the saved config automatically and you never have to think about it again. api_base_url stays at https://api.hitem3d.ai - change it only if you're pointed at a mirror or proxy.
The official setup wizard (setup_wizard.py / setup_wizard.bat in the pack folder) does the same thing with more hand-holding, and the pack's example workflows all include this node already wired in.
Installing
Install the pack via ComfyUI Manager (search "ComfyUI HiTem3D Integration") or:
cd ComfyUI/custom_nodes
git clone https://github.com/GeekatplayStudio/comfyui-hitem3d
cd comfyui-hitem3d
pip install -r requirements.txt
Then restart ComfyUI. Dependencies are minimal - just requests and Pillow - and there are no model downloads. The pack even ships a config.json with sample keys already in it; those are not yours, so replace them before you do anything real.
Where people get burned
- Credentials "not being picked up." The Generator instantiates its API client from the saved config file, so if you entered keys with
save_configoff and then restarted ComfyUI, they're gone. Flipsave_configon, or editconfig.jsondirectly. - "Invalid credentials." Both keys must be present - a missing secret key fails auth even with a perfect access key. Double-check for a stray space when pasting.
- Leaking keys. The pack's
config.jsonis in.gitignorefor a reason. If you share a workflow with the config node baked in, setsave_configtofalseand scrub any keys before exporting.
It's not exciting, but it's the difference between a 10-second setup and a long afternoon of Invalid credentials errors. Do it once, save it, move on.
Inputs (5)
| Name | Type | Default | Description |
|---|---|---|---|
| access_key | STRING | YOUR_ACCESS_KEY_HERE | — |
| secret_key | STRING | YOUR_SECRET_KEY_HERE | — |
| api_base_urlopt | STRING | https://api.hitem3d.ai | — |
| save_configopt | BOOLEAN | false | — |
| override_configopt | BOOLEAN | false | — |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| config_status | STRING | — |
| config_data | STRING | — |