AZAll Text Combine
Two strings in, one string out
- combined
Plumbing. Pure, honest plumbing, and the pack is better for it. AgentAZAll_TextCombine takes two strings and joins them with a separator - nothing more, nothing less. If you've built any LLM workflow in ComfyUI, you already know why this exists: you've got a recalled memory in one node and a user prompt in another, and the LLM wants them in one string. This is the node that glues them.
It's the most unglamorous node in the pack, but it's the one that appears in nearly every demo - the Character Design Studio, the Novel Crafter, the RAG pipeline all reach for it when context needs assembling.
How it works
It concatenates text_a, the separator, and text_b. The default separator is "\n\n" (a blank line), which reads well when you're joining prose blocks. It's a pure function - no side effects, no state, nothing written to disk. Both text inputs are typeable widgets that also accept upstream connections, so you can either type a value or wire a node into each.
The inputs that matter
text_a- first block. Wire this from Recall, a Note, or the System Prompt output.text_b- second block. Your user prompt, an LLM's previous output, whatever.separator(default"\n\n") - what goes between them. Change it to"\n"for tight lines,"\n\n\n"for clear section breaks, or anything else - it's just a string.
The combined output is text_a + separator + text_b, a plain STRING ready for the LLM's user_prompt or any other text input.
Installing it
Part of cronos3k/comfyui-agentazall - Manager search "AgentAZAll", or:
cd ComfyUI/custom_nodes
git clone https://github.com/cronos3k/comfyui-agentazall.git
pip install "agentazall>=1.0.13"
# restart ComfyUI
No models, no keys.
Common issues
Honestly, the failure modes are "joined wrong." Forgetting you set a separator to something weird and then wondering why your prompts merged without spacing is the classic one. If you need to join more than two strings, chain them - combine A+B, then combine the result with C (there's no N-way mode here). And if your text is empty on one side, you'll get a leading or trailing separator in the output; that's cosmetic for an LLM but can look odd in a Text Display. For heavier formatting needs, the pack's Prompt Template node is the fancier cousin - this one is for quick joins.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| text_a | STRING | — | |
| text_b | STRING | — | |
| separatoropt | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| combined | STRING | — |