ReAct: Reason + Act Prompting
The ReAct framework explained
ReAct stands for Reason + Act. It's a prompting pattern where the AI alternates between two modes:
Thought — The model reasons about what it knows and what it needs next.
Action — The model takes a step (searches for information, writes code, calls a tool).
Observation — The model reads the result of its action and updates its understanding.
This cycle repeats until the task is complete. ReAct is the foundation of modern AI agents — every tool-calling AI (like Claude with computer use, or ChatGPT with browsing) operates on this principle.
Even without actual tools, you can simulate ReAct manually to make the model reason more carefully about multi-step problems.
Manual ReAct: simulating the pattern in a conversation
You don't need API access or tool-calling to use ReAct thinking. You can simulate it in a normal chat:
```
You are solving a complex research task. Use this cycle:
Thought: [reason about what you know and what you need]
Action: [describe what you would look up or do]
Observation: [what you would expect to find]
Thought: [update your understanding]
... repeat until you can answer.
Task: Help me understand why my SaaS churn rate jumped from 4% to 11% last month. What are the most likely causes and how should I investigate?
```
The model will simulate the research process, naming what data it would gather and how it would interpret each finding. This surfaces better hypotheses than a direct answer.
ReAct in real AI agents
When you build an AI agent (using Claude API, OpenAI, or n8n), ReAct is the architecture that makes it work. The agent:
1. Reads your instruction
2. Thinks about what it needs (Thought)
3. Calls a tool — search, database, API (Action)
4. Reads the result (Observation)
5. Decides: done, or needs another action?
Practical example — an AI customer support agent:
- Thought: Customer is asking about their order status. I need to look it up.
- Action: Query orders database with order ID from the message.
- Observation: Order #4421 shipped 2 days ago, expected delivery tomorrow.
- Thought: I can now answer with the specific delivery information.
- Final response: 'Your order #4421 shipped on Tuesday and is expected to arrive tomorrow by 6pm.'
This is why ReAct agents give accurate, grounded answers instead of hallucinating.
Designing ReAct prompts for n8n and Make workflows
If you're building automations with n8n or Make, you can embed ReAct-style prompts in your AI nodes to make them smarter:
Without ReAct (fragile):
Summarize this email and categorize it as Sales, Support, or Spam.
With ReAct (robust):
```
Analyze this email using the following steps:
Thought 1: Who sent this email and what do they want?
Thought 2: Does this match Sales (buying intent), Support (existing customer problem), or Spam (unsolicited)?
Thought 3: What is the urgency level: High (reply within 1 hour), Normal (reply today), or Low (reply this week)?
Output as JSON:
{"category": "...", "urgency": "...", "one_line_summary": "...", "recommended_action": "..."}
```
The explicit reasoning steps dramatically reduce miscategorization, and the structured output slots directly into your workflow's next node.
Key Takeaways
- ReAct alternates between Thought (reasoning), Action (doing), and Observation (reading results).
- You can simulate ReAct in plain chat to get more careful multi-step reasoning.
- Every modern AI agent uses ReAct under the hood — understanding it makes you a better agent designer.
- Embedding ReAct-style reasoning in n8n/Make AI nodes dramatically improves accuracy and reduces hallucination.
Build a ReAct prompt for a research task
Pick a research question relevant to your work or project. Write a ReAct-style prompt with explicit Thought→Action→Observation cycles. Run it in Claude and observe how the structured reasoning leads to a more thorough answer than a simple direct question.