ComfyUI Meets ShotGrid: Now Keep the Receipts

For those who don’t know the tool: Flow Production Tracking for ComfyUI is an open-source pair of ComfyUI nodes that publish generated images and video into Autodesk’s Flow Production Tracking, formerly ShotGrid, and load tracked versions back into a graph.

ComfyUI generates images (Among other things, yes, but this isn’t the topic here) ; production teams still need to track the model, seed, prompt and approval history behind each result. Developer ksallee’s sg-comfyui project connects ComfyUI to Version records in Autodesk Flow Production Tracking. Its two custom nodes are called SG Publish and SG Load. The nodes publish and retrieve results rather than generating new images.

Publish the result, and the reason it exists

SG Publish takes an IMAGE or VIDEO from a ComfyUI graph and creates a Flow Production Tracking Version linked to a Shot, an Asset or another configured target. Project, link, Task and status choices are read from the production site’s data. The node uploads browser-playable review media and can register the original still, frame sequence or movie as PublishedFiles under a configured local storage root. Artists and supervisors can refer to the same tracked deliverable instead of trading files named final_v7_use_this_one_REAL.png.

Nine typed provenance fields can be configured on the Version: AI generator, model, positive prompt, negative prompt, seed, sampler and scheduler, step count, CFG setting, and upstream Version lineage. The prompt is traced along the generating branch rather than guessed from unrelated text elsewhere in the graph. Seed is stored as text, not a numeric field, because ComfyUI seeds can reach 2^64 minus one. A .provenance.json attachment carries the record, and a workflow JSON file is attached when the submitting client actually supplies one. Standard ComfyUI frontends usually include workflow data; API clients and external automation may submit only an executable prompt graph. The node reports missing provenance instead of inventing it.

The project README says that if the nine custom Version fields do not exist, the node puts their values into the Version description, or uses available fields and records the remainder in the description. Settings includes SG Site Setup, which inspects and creates the missing fields. Teams can inspect the settings and workflow even before their site defines all generation-specific fields.

Getting a tracked version back into the graph

SG Load retrieves media by project, link, Task, status and name, or by a specific pinned Version ID. It outputs image, video and mask data together with the resolved Version ID, code and declared colour space. Image sequences can include 16-bit PNG or 32-bit float EXR. When an SG Load result feeds another SG Publish, the new Version records which tracked Version it came from. That lineage is scoped to the actual branch used, so unrelated nodes are not credited simply because they happened to be on the same canvas.

The loader can resolve the newest matching Version at run time, optionally filtered by status or a code substring; there is also an ordering option based on version naming. A later graph can consume a tracked result without somebody copying Version IDs between graphs by hand. The pipeline still needs its own approval rules: Flow statuses vary by project, and ‘approved’ is not a universal field.

Media, bit depth and colour: important fine print

The publish node can write frames as 8-bit PNG, 16-bit PNG or 32-bit float EXR using ComfyUI’s own media functions. A connected mask becomes frame alpha, following ComfyUI’s convention in which white mask areas are transparent. Video supplied from an existing file is uploaded byte for byte; other generated movie output uses ComfyUI’s own VideoInput.save_to(). Review copies are 8-bit even when a higher-precision source has been published. One tracked Version can have a review upload and path references to source frames or movie, with original image sequences registered as PublishedFiles when requested.

The colour-space value stays metadata: the system records the declared space on the PublishedFile and returns it on load, but does not infer or convert pixel values. Nor does core ComfyUI provide a full colour-management solution by itself. Pipelines still need explicit colour-management steps around these nodes. The installation guide explains the requirements and known limitations.

Login without hiding another password in a node

Artists connect from ComfyUI’s Settings → SG panel by entering the site URL, opening the browser approval page and authorizing access with their Autodesk identity. Publications can then be attributed to the human user. A farm can use a configured script name and application key instead. The site profile controls field mappings, file paths, version naming, storage roots and publish defaults; these values can differ across productions. Python and site administration are not made redundant, but the first-time setup is in a predictable place.

The Comfy Registry entry allows installation through ComfyUI Manager or comfy node install sg-comfyui; cloning the repository into ComfyUI/custom_nodes remains an option for development. Current published requirements are ComfyUI 0.34.0 or newer, Python 3.11 and access to a Flow Production Tracking site. The project describes itself as alpha. A Windows publishing workflow is untested, and it does not yet publish a ZIP bundle when shared storage is absent. Plan the deployment around those constraints.

Why this could be genuinely useful

The nodes give multi-artist teams a traceable hand-off. Editorial and VFX can review a Version instead of an anonymous folder; a downstream artist can identify its prompt, model, sampler and source Versions; pipeline scripts can select a tracked result. A repeatable generation is more useful than an attractive thumbnail with no record of how it happened. Our earlier ComfyUI coverage examined assistants that generate graphs. This project tracks the results worth keeping.

Before putting this alpha integration into a live show, test image sequences, masks, EXR precision, permissions and publish paths against a representative project and your site’s actual schema, then verify the resulting Version and PublishedFile records.

https://github.com/ksallee/sg-comfyui