> 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/ai-nodes/text-assistants.md).

# Text Assistants

While "Generate Text" nodes come with empty instructions, Text Assistants are pre-built expert prompts paired with powerful LLMs. 

Instead of engineering prompts yourself, you select an assistant, add your own context, and get production-ready text outputs.

### How it works

1. **Add a Text Assistant node** from the node picker (under Use AI → Text Assistants).
2. **Choose an assistant** — each one is optimized for a specific task (prompt enhancement, ad copy, content analysis, etc.).
3. **Connect inputs** — feed in text, brand context, or other data from upstream nodes.
4. **Configure** — add custom instructions to tailor the assistant's behavior to your use case.
5. **Run** — the assistant processes your inputs through the selected LLM and outputs text.

### What you can do

Text Assistants handle a wide range of text tasks within your workflows:

* **Enhance prompts** — improve a rough user prompt before it reaches an image or video generation node.
* **Generate copy** — write ad copy, social captions, product descriptions, or email content.
* **Analyze content** — process uploaded documents, summarize information, or extract key data.
* **Transform text** — reformat, translate, or adapt content for different channels or audiences.
* **Combine inputs** — merge multiple inputs (user prompt + brand context + reference data) into a single, structured instruction for downstream nodes.

### How to use Assistants

{% embed url="<https://youtu.be/J5A1dlSucNw>" %}

### Tips

* **Use Text Assistants as glue between nodes.** Place one between your input and your generation node to process, enhance, or restructure data before it reaches the AI model.
* **Refine them to fit your context**. Tweak instructions, connect Brand Voice and Brand Context nodes to ensure the assistant writes in your brand's tone and style.
* **Stack multiple assistants** when you need multi-step text processing — e.g., one to analyze a brief, another to write the prompt.
* **Try different models** for the same task. Balanced models are fast and cheap for simple transformations; advanced models handle nuanced creative writing better. Check the Text models guide for recommendations.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.pletor.ai/build-agents/nodes/ai-nodes/text-assistants.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.