Griptape Combine: RAG Module List

If you're building retrieval-augmented generation (RAG) in ComfyUI, you'll eventually have a pile of RAG modules - text loaders, chunkers, response generators - and need to hand them to a RAG engine as one bundle. Griptape Combine: RAG Module List is the node that does that bundling. It's the same "collect and flatten" pattern as the Tool List and Rules List combine nodes, just aimed at the RAG side of the pack.

What it's for

The pack's RAG section is built around modules you assemble into a pipeline: a loader that ingests text, a chunking module, a response generator. A RAG engine wants those modules as a list, and this node collects them from however many branches your workflow has. The node description says it plainly: "Combine rag modules into a list to be used with RAG Engines."

Honest positioning: RAG in ComfyUI-Griptape is a more advanced corner of the pack, and the average user installing Griptape for chat-and-image workflows won't touch this node. You're here because you specifically want agents to answer questions from your documents - and this is the glue step that makes that work.

How it works

Identical mechanics to its siblings. Each module_1 input carries a list, and the node appends the first module from each:

module_list = []
for module in modules:
    module_list.append(module[0])

Connect one module and more inputs spawn as you plug in the next. The output is a flat MODULE_LIST you wire into a RAG engine node.

Inputs and output

• module_1 (MODULE_LIST) - a RAG module output to add. More inputs appear dynamically as you connect.
• Output: MODULE_LIST - the combined module list, ready for a RAG engine.

Installation

Ships in ComfyUI Griptape Nodes:

• ComfyUI Manager: search "Griptape" → install.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/griptape-ai/ComfyUI-Griptape, restart ComfyUI.

Same pack-level install as everything else, with the shared griptape[all]/python-dotenv/openai dependencies.

Gotchas

• RAG modules have real requirements - embedding drivers, vector store drivers, API keys for whichever provider you use. This node combines them but doesn't configure them; a RAG pipeline that "does nothing" is almost always a missing driver or key upstream, not a combine-node problem.
• It's a pure utility: no network calls, no state. If it works, it works instantly, and there's little that can go wrong inside it.

You won't use it often, but when you're assembling a document-answering agent, it's the one node that makes "several modules → one engine" a single tidy connection.