Nodes/ComfyUI-aihub-workflow-exposer/AIHub Meta Set Exported Workflow Image
ComfyUI Node

AIHub Meta Set Exported Workflow Image

The thumbnail for your exported AIHub workflow, set after the fact

By otavanopisto·Created about a year ago·Updated 22 days ago· 7
AIHub Meta Set Exported Workflow Image
  • image
    workflow

    In the otavanopisto ComfyUI-aihub-workflow-exposer pack, a workflow gets exported to the ComfyUI/aihub/workflows folder - and like models and LoRAs, it can carry a same-named PNG that acts as its card image. That image is what a client app shows when the user browses available workflows. AIHubMetaSetExportedWorkflowImage is the node that writes that PNG to an already-exported workflow, without re-exporting the workflow itself.

    There's a parallel here worth noticing. The AIHubWorkflowController node has an "Export to AIHub workflows" button that validates and exports the workflow to the aihub folder, and the README says it "optionally also requests for a png image that would represent the workflow." This node is the standalone version of that optional request: you exported a workflow, it has no image (or a bad one), and you want to fix it without touching the export. It's the same pattern as the pack's AIHubMetaSetExportedModelImage and AIHubMetaSetExportedLoraImage - one id + one IMAGE, write a PNG, done.

    How it works

    • workflow - the id of an exported workflow, from a dropdown populated by ComfyUI/aihub/workflows. Only already-exported workflows appear.
    • image - any IMAGE from the graph. First frame is saved as {id}.png in the workflows folder. Missing image → the source raises "No image specified."

    No outputs; it's a fire-and-forget output node.

    Why you'd use it

    The exported workflow's image is your storefront. A client lists workflows with name, description, and this thumbnail - get a good one and the workflow reads as "finished and curated"; skip it and users see a blank card. Because the file overwrites in place, you can iterate: generate a representative output image, load it back into the graph, and stamp it on. It's the cheapest way to keep the catalog looking professional.

    Gotchas

    The workflow id must already be exported, or it won't be in the dropdown - run the controller's export first and confirm the file landed in ComfyUI/aihub/workflows. Keep the id alphanumeric plus _/- as the pack's validation expects, because the client matches image to workflow by that exact id. And the usual pack caveat applies: deleting or renaming is filesystem work; this node only adds or overwrites.

    Install, same as everything in this pack - no requirements.txt, no model downloads:

    cd ComfyUI/custom_nodes
    git clone https://github.com/otavanopisto/ComfyUI-aihub-workflow-exposer
    

    Restart ComfyUI. If you're shipping AIHub workflows to a client, make a habit of stamping a real preview on each one - it's one node and it's the difference between a catalog that looks like a product and one that looks like a dev folder.

    Categoryaihub/meta

    Inputs (2)

    NameTypeDefaultDescription
    workflowCOMBOThe id of the workflow to set the image for
    imageIMAGEThe image to set for the workflow

    Outputs (0)

    No outputs