The HiTem3D nodes now support two ways to provide API credentials:
- Use the HiTem3D Config Node in your workflow
- Enter your API keys directly in the node
- Set
save_configtoFalseto keep credentials in memory only - ✅ Secure: No credentials saved to disk
- ✅ Flexible: Different keys per workflow
- Use the HiTem3D Config Node with
save_configset toTrue - Or manually edit
config.jsonfile - ✅ Convenient: Set once, use everywhere
⚠️ Note: Credentials saved to disk
- Runtime Config (from Config Node) - Highest Priority
- File Config (from config.json) - Fallback
[HiTem3D Config Node] → [Generator Node] → [Downloader Node]
↓ ↓ ↓
config_data config_data config_data
- Add Config Node to your workflow
- Connect the
config_dataoutput to:- Generator Node's
config_datainput - Downloader Node's
config_datainput
- Generator Node's
- Enter your API keys in the Config Node:
- Access Key:
your_actual_access_key - Secret Key:
your_actual_secret_key
- Access Key:
- Set save_config to
False(default) - Run the workflow - credentials stay in memory only
- Add Config Node to your workflow
- Connect as above
- Enter your API keys in the Config Node
- Set save_config to
True - Run once - credentials saved to
config.json - Future workflows will use saved credentials automatically
Every example workflow now includes the HiTem3D Config Node:
- ✅
hitem3d_basic_workflow.json - ✅
hitem3d_showcase_preview_workflow.json - ✅
hitem3d_complete_preview_workflow.json - ✅
hitem3d_multiview_preview_workflow.json - ✅
hitem3d_test_preview_simple.json
- Use File Configuration for convenience
- Keep
config.jsonin.gitignore(already included)
- Use Runtime Configuration only
- Never save credentials to file when sharing workflows
- Set
save_config = Falsein shared workflows
- Always use placeholder values in repository
- Use
.envfiles for development credentials (not implemented yet)
| Setting | Description | Recommended |
|---|---|---|
access_key |
Your HiTem3D Access Key | Required |
secret_key |
Your HiTem3D Secret Key | Required |
api_base_url |
API endpoint | https://api.hitem3d.ai |
save_config |
Save to config.json | False for security |
LoadImage ──IMAGE──> HiTem3DNode ──task_id──> HiTem3DDownloaderNode ──model_path──> HiTem3DPreviewNode
↑ ↑
config_data config_data
↑ ↑
HiTem3DConfigNode ──config_data──┴─────────────────┘
Solution: Use Config Node with runtime configuration
Solution: Check your API keys in the Config Node
Solution: Ensure config_data output connects to both Generator and Downloader
Solution: Use updated workflow examples that include Config Node
If you have old workflows without Config Node:
- Add HiTem3D Config Node to workflow
- Connect
config_dataoutput to Generator and Downloader inputs - Enter your API credentials
- Set save_config according to your security preference
- ✅ No more missing config errors
- ✅ Flexible credential management
- ✅ Better security with runtime-only config
- ✅ Backward compatibility with file config
- ✅ All workflows ready-to-use with config included
Get HiTem3D API Keys: hitem3d.ai/?sp_source=Geekatplay
Created by: Geekatplay Studio by Vladimir Chopine
Website: www.geekatplay.com