Text¶
Captures user-provided text and emits it to the workflow while also updating the run UI with the entered value. Supports both single-line and multi-line input and passes the text through unchanged.
Usage¶
Use this node at the start of a workflow or anywhere you need manual text input (e.g., prompts, configuration strings, messages). Connect its output to downstream nodes that consume strings, such as LLMs, text processors, or formatting utilities.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| input | True | STRING | The text to pass into the workflow. Accepts single or multiple lines. | Summarize the following article... |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| output | WILDCARD | The text that was entered, passed through unchanged for downstream nodes. | Summarize the following article... |
Important Notes¶
- UI output: In addition to emitting data, this node posts a UI entry showing the submitted text.
- Multiline supported: You can enter multi-line text; it is emitted as a single string.
- Empty behavior: If no text is provided, the node emits an empty string.
- Display name: Appears in the editor as “Text”.
- Type flexibility: Output is declared as WILDCARD for broad compatibility; most consumers treat it as a string.
Troubleshooting¶
- No text appears downstream: Ensure the node’s output is linked to the next node’s input and that the downstream node accepts STRING input.
- UI panel doesn’t update: Re-run the workflow and confirm the node is executed; UI updates occur when the node runs.
- Unexpected empty output: Verify that the input field isn’t blank; the node intentionally emits an empty string if no text is entered.
- Formatting lost: Downstream nodes may alter text; check those nodes if line breaks or spacing appear different.