InstaSD API Input - String
The single-line prompt box for your demo
- string
InstaCText is a text field that passes whatever you type straight through - no API call, no key, no trickery. What it actually is, for the InstaSD crowd: the input that becomes a single-line text box on your published workflow's page.
Here's the setup. InstaSD (instasd.com) takes a ComfyUI workflow and turns it into a public one-page app or API endpoint. The InstaSD/API_inputs nodes in this pack are how you tell the platform which inputs to expose to the people using it. A string is the obvious choice for the most important control of all: the prompt itself. When you publish a text-to-image workflow, this is the node your visitors type into.
What you set
- string - the text, defaulting to an empty string. Whatever you enter comes out the other side as the output string (type
STRING).
That's the whole node: one input, one output, both named string. Single-line only - if you need paragraphs, wildcards, or multi-token prompts with line breaks, use InstaCTextML from the same pack, which is the multiline twin.
Two workflow-level habits that make this node useful rather than decorative:
- Wire the output into a CLIP Text Encode (or a positive/negative conditioning pair) so the published prompt box actually drives the generation.
- Because the value passes through untouched, you can build a more complex default - a string that already contains wildcards or partial template text - and still let the end user override it.
Install
cd ComfyUI/custom_nodes
git clone https://github.com/WaddingtonHoldings/ComfyUI-InstaSD
Restart ComfyUI, or use ComfyUI Manager and search "InstaSD". The pack installs boto3, Pillow, requests, and numpy; no models, no credentials required for this node.
Gotchas
- Locally this is just a pass-through text node. If you're not publishing through InstaSD, ComfyUI's built-in primitive text input does the same job without the pack.
- Since the text passes through verbatim, trailing spaces and stray newlines from a copy-paste will reach your CLIP encoder. Trim in the widget if your outputs start looking subtly off.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| string | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| string | STRING | — |