Burve Variable Injector
The other half of Burve's variable prompt system
- variables
This node has one job: collect up to fourteen string values and hand them to Burve Prompt Database as a VARIABLE_DICT. It's the input side of the pack's variable-injection system - the database holds templates with [[V1:default]] placeholders, and this node supplies the values that fill them.
It looks boring because it is. Fourteen text fields, V1 through V14, all optional, one variables output. You type values, it bundles them into a dict, done. But boring is exactly what you want from this kind of node: it's the thin, predictable layer that lets the interesting parts - the prompt templates and the image generation - stay reusable. Fill in V1 = 12, V2 = "1920s", and the same database prompt becomes a twelve-image period-piece grid instead of the default nine-image modern one.
How it works
Nothing clever, and that's the point. The node collects whatever's in the provided fields and passes them through as a dictionary - empty slots simply don't make it in. That behavior matters downstream: Burve Prompt Database treats a variable that's present-but-empty as absent and falls back to the template's default, so leaving a field blank is the intended way to "use the default." If you want to force an empty string into a template, you can't do it from here - the node filters empties.
Inputs and outputs
V1…V14- optional single-line string inputs. All empty is legal but useless; connect at least one.variables- one output of typeVARIABLE_DICT, wired into the Prompt Database'svariablessocket.
The VARIABLE_DICT type is a custom socket type, so it only plugs into nodes that know it - within this pack, that's Burve Prompt Database. Don't try to route it into a generic text node; that's not what it is.
Using it well
The real payoff is when the values aren't static. Nothing stops you from feeding the V fields from upstream nodes - a seed-driven selector, a text generator, or Burve Prompt Selector 14 - so the variable values can change per run while the template stays fixed. That turns this from a "fill in the blanks" widget into a building block for prompt variation at scale. Install is the standard pack route - clone https://github.com/Burve/ComfyUI_Burve_Tools.git into custom_nodes or use ComfyUI Manager, then restart. No models, no keys, no setup beyond that.
Inputs (14)
| Name | Type | Default | Description |
|---|---|---|---|
| V1opt | STRING | — | |
| V2opt | STRING | — | |
| V3opt | STRING | — | |
| V4opt | STRING | — | |
| V5opt | STRING | — | |
| V6opt | STRING | — | |
| V7opt | STRING | — | |
| V8opt | STRING | — | |
| V9opt | STRING | — | |
| V10opt | STRING | — | |
| V11opt | STRING | — | |
| V12opt | STRING | — | |
| V13opt | STRING | — | |
| V14opt | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| variables | VARIABLE_DICT | — |