After you group nodes into a ComfyUI subgraph, the parent workflow can connect only to the subgraph’s exposed input and output slots. Grouping creates an initial interface from the selected nodes’ inputs and outputs, but you can edit that boundary: add connections through the default empty slot, rename or remove slots, and disconnect a slot from its internal node. A visible slot is not a type override; connections still follow ComfyUI’s standard data-type validation. See the official subgraph guide.
What the parent workflow can connect to
Treat the subgraph boundary as an interface, not as a view of every port inside. An internal node input or output is externally connectable only when represented by an exposed slot on the subgraph. Ports that remain inside without a corresponding slot are available to the internal graph, not directly to the parent workflow.
The automatically created slots are only a starting interface. The documentation does not specify a one-to-one mapping rule or guarantee that every selected-node port is exposed as a separate slot. After grouping, enter edit mode and inspect the input and output slots individually, especially when the selected nodes have several inputs or outputs or when you intend to hide implementation details. Slot names help identify purpose, but do not change the underlying data type.
Inspect and edit the boundary
Use this sequence when a wire that used to reach an internal node no longer has an obvious destination outside:
- Open the subgraph by double-clicking an empty area inside it, avoiding widgets, or use its edit button.
- In edit mode, inspect the input slots and output slots. Match each needed parent connection to an actual exposed slot rather than to an internal node port.
- To expose another connection, use the default slot, labeled
1. Connect an input slot to the intended internal node input, or an output slot to the intended internal node output. The guide describes this empty slot as the way to add new input or output connections. - Right-click a slot’s connection point to rename or delete that exposed slot. Use a name that identifies the signal’s role, such as
ImageorMask, when those names accurately describe the port. - If a slot should no longer point to its current internal node, right-click it and use the documented disconnect action. Do not assume from that action alone that the slot remains usable or has a particular parent-level state; return to the parent workflow and inspect the resulting port before reconnecting it to an intended internal port.
- Exit to the parent workflow using the navigation bar or
Esc. Check that the intended slot is present on the subgraph node and try the external connection there.
Slot controls are available in edit mode; changing a widget in the parameters panel is a separate operation and is not a substitute for exposing a port.
Diagnose a missing or rejected wire
Use the symptom to decide what to inspect next:
| Observation | Likely boundary issue | Next check |
|---|---|---|
| The parent node has no port for the needed internal input | No exposed input slot represents it | Re-enter edit mode and add a connection using the default slot |
| A slot exists but has an unclear label | The interface is difficult to identify, not necessarily disconnected | Right-click the slot and give it a descriptive name |
| A slot is visible but its internal destination is wrong or absent | The slot is disconnected or linked to another internal port | Right-click it and inspect whether it is connected to the intended original node |
| A candidate wire is refused | The two ports may not pass standard data-type validation | Compare the source output and exposed slot’s connected internal port; choose a compatible port rather than assuming the slot changes type |
| An internal output is not available outside | It has not been exposed as an output slot | Add an output connection through the default slot and check the parent node again |
For example, suppose a hypothetical subgraph contains a node with an IMAGE output and another with a MASK output. If the parent needs the image but only a mask output slot is exposed, the image is not reachable through that slot merely by renaming it. Add a separate output slot connected to the image output, then check the parent interface and type compatibility. These names and signals are an illustrative scenario, not a claim about a particular workflow.
Verify the interface with a port list
Before considering the boundary ready, compare the internal ports you need against the exposed slots. The following hypothetical checklist uses two internal outputs; it does not report a software test.
| Internal port | Expose to parent? | Slot name | Data type | External connection check |
|---|---|---|---|---|
| Image-producing node output | Yes | Preview Image | IMAGE | Try the connection in the parent workflow and confirm ComfyUI accepts the wire |
| Mask-producing node output | No | None | MASK | Confirm no parent output is expected for this internal result |
| Downstream node image input exposed as a subgraph input | Yes | Source Image | IMAGE | Try the connection in the parent workflow and confirm ComfyUI accepts the wire |
This is a hypothetical worksheet, not an official test result. IMAGE and MASK labels, port colors, or other visual cues can help identify a candidate connection, but they are not by themselves proof that a particular connection will be accepted. The acceptance check is the actual connection attempt in the target parent workflow, followed by checking that the intended internal port is still connected.
Limits and common questions
If the default slot does not produce the intended boundary, confirm that you are in subgraph edit mode and are using the empty slot for the correct direction. Right-click the existing slot to check whether it is linked to the original node, or disconnect and reconnect it. Then return to the parent and inspect the exposed port again.
The feature requires ComfyUI frontend version 1.24.3 or later according to the official documentation. If the subgraph controls are absent, check the frontend version and update guidance. The guide also notes that displayed images were made with a nightly frontend, so the interface may differ from what you see. This guide covers boundary slots, not parameter-panel widget ordering or publishing blueprints.
Does grouping expose every internal port automatically?
Grouping automatically creates a subgraph based on the selected nodes’ inputs and outputs. Inspect the resulting slots and add or adjust the boundary for the connections your parent workflow actually needs; do not assume an internal port is externally reachable unless a slot represents it.
Does renaming a slot make an incompatible connection valid?
No. Slot connections follow standard data-type validation rules. Renaming changes the slot label, not the data type; use a compatible port if a connection is rejected.
How do I remove or detach a slot?
In edit mode, right-click the slot’s connection point. The documented actions include renaming or deleting exposed slots and disconnecting a slot from its original node. Choose deletion when the interface should no longer have that slot. For disconnection, treat the resulting slot state as something to verify rather than assume: return to the parent workflow and inspect the exposed port before deciding whether to reconnect or remove it.
Three follow-up questions
- Which internal inputs and outputs does the parent workflow actually need, and which should remain implementation details?
- After renaming, deleting, or disconnecting a slot, does the parent workflow still show the intended port and accept the intended wire?
- If a candidate wire is rejected, have you checked the source output and the exposed slot’s connected internal port, rather than relying only on a label or color?
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.