🎈GroupExecutorSingle

Ever wanted to press Run and have only part of your workflow execute - not the whole graph, just the box you care about? That's the whole reason this node exists. GroupExecutorSingle is the workhorse of the Comfyui-LG_GroupExecutor pack: it's a "call one ComfyUI Group" node, the way other packs give you function calls. You point it at a group, tell it how many times to run and how long to wait, and hand the plan downstream to a GroupExecutorSender, which actually fires it.

Let me be straight about what this pack is first, because it colors everything: it's a niche, mostly-Chinese-audience utility pack from LAOGOU-666 (v1.3.6, no extra Python dependencies, no model downloads). There's essentially no English community chatter about it - the reddit signal is zero. So you're on your own a bit more than with rgthree or Impact Pack, but the source is simple and readable, and the group-execution idea is genuinely useful once you've built a graph too big to re-run whole.

How it works

This node doesn't generate anything. It schedules. Here's the mechanism:

• You give it a group_name. That name must match, character-for-character, the title of a ComfyUI Group - the grey box you make with right-click → "Add Group" in the canvas.
• The node appends an execution item {group_name, repeat_count, delay_seconds} to a SIGNAL list and passes it on. Wire several GroupExecutorSingles in a chain and the order of the chain becomes the order of execution.
• The trigger happens elsewhere: a GroupExecutorSender at the end of the chain receives the list, pokes the browser via websocket, and the frontend finds the group (app.graph._groups.find(g => g.title === groupName), if you want the implementation detail), builds an API prompt containing only that group's nodes, and queues it.

So on its own, GroupExecutorSingle is half the story. Think of it as writing the to-do list; the Sender is the hand that hits execute.

The inputs that matter

Only three of them, which is part of the appeal:

• group_name - must exactly match a Group's title. This is where people get burned: a trailing space or a renamed group and the node just silently has nothing to run.
• repeat_count (1–100) - how many times that group runs back-to-back. Useful for, say, looping a batch through one detailer group.
• delay_seconds (0–60) - pause before this item executes, for staggering or rate-limiting.

There's also an optional signal input: chain Singles by feeding each one's SIGNAL output into the next's signal input.

Output

One output, SIGNAL, holding the execution item (or the accumulated list). Wire it into the next GroupExecutorSingle to extend the chain, or straight into a GroupExecutorSender to run it.

Install

ComfyUI Manager → search "Comfyui-LG_GroupExecutor", or:

cd ComfyUI/custom_nodes
git clone https://github.com/LAOGOU-666/Comfyui-LG_GroupExecutor

Then restart ComfyUI. No models, no pip requirements worth worrying about - the pyproject declares an empty dependency list, which is exactly the right amount for a control-flow pack.

Gotchas

• It needs the browser. The whole group system works by the Sender telling the frontend to build sub-prompts. If you're driving ComfyUI headless through the API only, this node does nothing.
• group_name must match exactly. This is the #1 failure mode, and the README calls it out too: unique names, exact match.
• The delay is per item, not a global timer - each Single carries its own.