Jamworks_Login

ComfyUI doesn't know who you are, and that's the whole problem this node solves. If your brand assets, approved renders, or campaign files live in Jamworks - a B2B marketing platform built around DAM, production workflows, and automations - then Jamworks_Login is the handshake that lets ComfyUI talk to it. It does nothing by itself. It authenticates you against Jamworks' core API and hands back a token string you then wire into the other nodes in this pack. Think key card for the building: useless on its own, required for everything else.

It's not a generation node. It won't make a single pixel. All it does is turn credentials into a token, which is why it makes sense as the first node in any Jamworks-backed workflow.

How it works

Under the hood it's one HTTP call. The node POSTs your user and password (form-encoded, not JSON) to {JW2_CORE_URL}/auth/login, reads the token field out of the JSON response, and pushes that token out its single output. No session handling, no refresh logic, nothing to maintain. When the token eventually stops being accepted, you just re-run the login node and get a fresh one.

The inputs that matter

• user / password - your Jamworks credentials.
• JW2_CORE_URL - the base URL of your Jamworks core API, the thing /auth/login hangs off. Your org hands you this; there's no discovery.
• token - required in the schema and completely ignored by the code. The login() method receives it and never reads it. You can leave it blank; the node overwrites it anyway. I genuinely don't know why it's there. Some things we don't ask.

The output

token (STRING) - feed it into Jamworks_Download's token input and you're in business. That's the entire wiring story: login node out, download node in.

Install

The whole pack installs in one go:

# ComfyUI Manager: search "comfyui_jamworks_client" and hit install, or:
cd ComfyUI/custom_nodes
git clone https://github.com/celsojr2013/comfyui_jamworks_client

Then restart ComfyUI. The nodes land under a "Jamworks" category. The good news on weight: the only runtime dependency is requests, which virtually every ComfyUI install already has. No models to download, no requirements.txt full of torch sub-dependencies. The only real setup is getting the core URL from whoever runs your Jamworks tenant.

One expectation-setting note: this repo is a single commit from mid-2024 and hasn't been touched since. It works, but don't hold your breath for active maintenance.

Where people get burned

The password sits in your workflow JSON in plaintext. That matters more here than in most packs because ComfyUI embeds the whole graph into the PNG metadata - share a workflow with real credentials wired in and you've just handed out the login. Build with dummy values, fill in the real ones locally, and never share that PNG.

Also remember this runs server-side. The auth happens on the machine running ComfyUI, not in your browser, and the token is visible to anyone who can load that workflow on a shared box.