See it happen
Section titled “See it happen”A Tools Agent with Wikipedia and Web Search is asked for three facts about a company. Its output lists the tool calls it made in steps, in order, next to the final response.
Example run: Get All Text, 1 item → Tools Agent, 1 item → Display Markdown, shows the answer. Illustration of a run. Each entry in steps also has result and truncated; tool names depend on the tools you connect.
{
"response": "1. Founded in 1843 (page). 2. Based in London (Wikipedia). 3. …",
"steps": [
{
"name": "wikipedia-api",
"args": {
"query": "Analytical Engines Ltd"
},
"status": "ok",
"durationMs": 812
},
{
"name": "web_search",
"args": {
"query": "Analytical Engines Ltd headquarters"
},
"status": "ok",
"durationMs": 1430
}
]
}Which AI node to use
Section titled “Which AI node to use”- Basic LLM Chain One call to the model: rewrite, draft, translate, answer from text you pass in. Example Turn page text into a short reply.
- Q&A Agent Answer a question from a connected knowledge base. Example What does our refund policy say about gifts?
- RAG Agent Answer from your documents, with memory and an output parser if you need them. Example A help-desk answer that cites its sources.
- Tools Agent The model must choose between actions, several times if needed. Example Research a company with Wikipedia and Web Search.
For common one-call tasks there are ready-made chains: Summarization, Text Classifier, Sentiment Analysis and Information Extractor.
How an agent works
Section titled “How an agent works”flowchart TD
Goal[Prompt and system message] --> Decide[Model decides the next step]
Decide --> Tool{Needs a tool?}
Tool -->|Yes| Call[Calls a connected tool] --> Result[Reads the result] --> Decide
Tool -->|No| Answer[Returns the answer]
class Decide awf-ai
class Tool awf-flow
class Call awf-io
class Answer awf-ok
The agent can only use what you connect to it. Max iterations (10 by default on the Tools Agent) limits how many tool calls it may make before it must answer. The Tools Agent needs a chat model that supports tool calling.
What you can connect
Section titled “What you can connect”| Slot | Basic LLM Chain | Q&A Agent | RAG Agent | Tools Agent |
|---|---|---|---|---|
| Model (required) | Yes | Yes | Yes | Yes, with tool calling |
| Knowledge | — | Yes | Yes | Yes |
| Memory | — | — | Yes | Yes |
| Tools | — | — | — | Yes |
| Output parser | Yes | Yes | Yes | Yes |
Check each node’s page for the exact options.
When to use an agent
Section titled “When to use an agent”Use an agent when you can’t know in advance which tool the step needs, or when each action depends on the last result. Use a chain or regular nodes when the task is the same every time, or when a wrong action would be costly. If you still need an agent there, rely on action approval.
Write a prompt that can finish
Section titled “Write a prompt that can finish”“Research this company” is too vague. A stronger prompt:
Find three facts about this company and give the source of each. Use the page text first. Search Wikipedia only if the page doesn’t say enough. Return a short list with links.
It gives the agent a goal, an order for its tools, a point to stop, and the shape of the answer.
You’ll notice this when…
Section titled “You’ll notice this when…”The agent never calls a tool
The model doesn’t support tool calling, the tools aren’t connected to the Tools slot, or the prompt doesn’t say when to use them. Name the tools in the prompt and say when each one helps.
The agent stops with a partial answer
It reached Max iterations. Tighten the prompt so it knows when it’s done, or remove tools it doesn’t need. Raise the limit only after that.
The agent picks the wrong tool
Too many tools, or tools with overlapping jobs. Keep two or three, with clear names and descriptions. See Tool selection.
The agent asks for approval before acting
That’s on purpose: actions on a page or a service ask you first. See Action approval.