In
Input port for a subgraph.
What it does
In marks an input port on the boundary of a subgraph container. Placed inside a Subgraph, it becomes a socket on the outside of that container: whatever is wired into it on the inside is fed from the parent graph on the outside.
The default mode is dynamic. A single + socket grows a new input slot each time something is wired into it. A fixed input_count exposes exactly that many slots, in order, whether or not they are all connected.
When to use it
Reusable Subgraphs that need values to enter from outside.
A subgraph interface that grows as things are plugged in: leave
input_countat its default of 0.A fixed, predictable set of inputs regardless of what is connected: set
input_countto that number.Renaming an exposed input so it reads clearly outside the container: click the node's title.
| Parameter | Type | Default |
|---|---|---|
name | String | "input" |
custom_name | String | "" |
input_count | Number | 0 |
enum_choices | String | "" |
opacity | Number | 1 |
Gotchas
The name shown on the outside of the container is picked in order: a title rename, then a name derived from the downstream connection, then input. Editing the underlying name field does nothing while a title rename or a downstream label holds priority. Rename via the title instead.
In dynamic mode, an input slot wired to nothing still passes a value through, its own last value or its default if it never had one, so downstream nodes inside the subgraph never see a socket go missing.
input_count is capped at 10 fixed slots. For more than that, leave it at 0 (dynamic) and let the + socket grow as needed.
Worked example
Open or create a Subgraph, then add an In node inside it.
Wire the In node's socket into whatever needs a value from outside. The
+socket appears, ready for the next connection.Close the subgraph and look at the container from outside: a new input has appeared, ready to be wired from the parent graph.
For a fixed set of inputs instead of one that grows, raise
input_countto that number.