🎈CCX Group Executor (Single)

Most of the nodes in WWWEN8's ComfyUI-CCXManager pack are about updating sd-ppp. These two - the "🎈CCX Group Executor" pair - are not. They're a generic way to run a named group of nodes repeatedly, and the pack just happens to use them to sequence its own update steps. If you've ever wanted to re-run one section of a big workflow without re-running the whole thing, this is interesting to you.

Start with the "Single" half, because it's the dumb half - in the good way. It's a data node: you describe what you want executed and it hands that description to the Sender node down the line. It doesn't execute anything itself.

What it does

ComfyUI groups are those colored boxes you make by selecting nodes and pressing Ctrl+G. Give this node a group's name and it builds an "execution item" for that group - then passes it along as a SIGNAL. The Sender node (CCXGroupExecutorSender) is what actually runs the group's nodes.

The group_name input is multiline, and it splits on commas or newlines, so you can list several groups and it'll build one execution item per group, in order. That's where "Single" gets its name - it's one way of packaging groups up, versus the Sender which runs them.

The inputs

• group_name - the name of the group(s) to run, one per line or comma-separated. Group names are case-sensitive and have to match the group title in your graph exactly.
• repeat_count - how many times to run each group, 1 to 100. Default 1.
• delay_seconds - pause between groups (and between repeats), 0 to 60 seconds. Default 0.

The optional signal input lets you chain executors: wire one node's SIGNAL output into another's signal input, and the new groups get prepended to the list before what arrived on the wire. Output is a single SIGNAL.

There's also a guard built in: if this node is already mid-execution, it refuses a second request and just passes the incoming signal through, so you can't stack up runaway runs by mashing the queue button.

Wiring it up

The pattern is: CCXGroupExecutorSingle → (SIGNAL) → CCXGroupExecutorSender. The Single node is where you edit group names and counts; the Sender is the output node you place last. Drop it into a workflow wherever you have a section you want to repeat without re-running upstream nodes - the pack's own workflow uses it to run the directory-creation, repo-update, and Photoshop-update steps as discrete, reusable groups.

Install

Same pack as everything else in this family:

cd ComfyUI/custom_nodes
git clone https://github.com/WWWEN8/ComfyUI-CCXManager.git

or ComfyUI Manager → "ComfyUI-CCXManager", then restart. It needs no extra dependencies beyond requests, and it ships frontend JS in the pack's web/ folder that the Sender relies on.

One trap: because it only produces a signal, nothing visibly happens if you run a workflow containing just this node without the Sender. If you hit Run and see nothing, you're missing the other half of the pair.