> For the complete documentation index, see [llms.txt](https://docs.pletor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pletor.ai/build-agents/nodes/logic-nodes.md).
# Logic nodes
You'll find these nodes under **Automate → Logic** in the node picker.
***
### Available logic nodes
| Node | What it does | Key inputs | Key outputs |
| ----------------------- | --------------------------------------------------------------- | ------------------------------------ | --------------------------------------------- |
| **Split Text** | Break a text string into separate parts based on a delimiter | Text input + delimiter character | Multiple text outputs (one per split segment) |
| **List Selector** | Pick a specific item from a list of text outputs | List of text items + selection index | Single text output |
| **Prompt Concatenator** | Merge multiple text inputs into a single combined prompt | Two or more text inputs | Single merged text output |
| **Human Review** | Pause the workflow for manual quality control before continuing | Any asset (image, video, text) | Approved or rejected asset |
| **Rename Asset** | Set custom filenames for generated assets | Asset + naming pattern | Same asset with new filename |
| **Router** | Reuse any node's output anywhere else in your flow | Any node output | Routed output to multiple downstream nodes |
***
### Split Text & List Selector
These two nodes work together for workflows that need to process multiple items from a single text input.
**Split Text** takes a block of text and breaks it into parts using a delimiter (like a comma, newline, or custom separator). Each part becomes a separate output that can feed into parallel downstream nodes.
**List Selector** picks one specific item from a list by index. Use it after Split Text when you only need one of the split outputs, or to select from any list-type output.
**Example flow:** A Text Assistant generates 5 ad headline variations separated by newlines → Split Text breaks them into 5 separate strings → List Selector picks headline #3 → Generate Image uses it as the prompt.
See more: [Split text & List Selector](/build-agents/nodes/logic-nodes/split-text-and-list-selector.md)
***
### Prompt Concatenator
Merges multiple text inputs into a single prompt. This is useful when you need to combine outputs from different branches of your workflow — like merging a user prompt with brand guidelines and a style description — before feeding them into a generation node.
Unlike a Text Assistant (which uses an LLM to intelligently process inputs), the Prompt Concatenator is a simple mechanical join. It's faster, costs no credits, and is predictable — but it won't rephrase or restructure the text.
See more: [Prompt Concatenator](/build-agents/nodes/logic-nodes/prompt-concatenator.md)
***
### Human Review
Inserts a manual checkpoint into your workflow. When the agent reaches a Human Review node, it pauses and waits for a human to approve or reject the output before continuing.
This is essential for production workflows where quality control matters — ad campaigns, client-facing content, or anything where you need a human eye before publishing.
See more: [Human review](/build-agents/nodes/logic-nodes/human-review.md)
***
### Rename Asset
Sets custom filenames for your generated assets. Useful when you need organized, predictable file names — especially for workflows that output multiple assets or integrate with external systems like Google Drive.
Supports dynamic naming patterns using variables from your workflow (e.g., combining brand name + asset type + date).
***
### Router
The Router lets you reuse any node's output at multiple points in your flow without duplicating the node. Connect a Router to a node's output, then route that output to as many downstream nodes as you need.
This keeps your canvas clean and avoids redundant processing — the source node only runs once, but its output is available everywhere the Router connects to.
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.pletor.ai/build-agents/nodes/logic-nodes.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.