Text Node
The Text Node is a fundamental utility node that stores and outputs static or dynamic text content. Unlike Display Text which shows content to users, the Text node works behind the scenes to provide text data to other nodes in your workflow. It's essential for supplying prompts, instructions, queries, and other text-based inputs to processing nodes like AI prompts, API calls, and data operations.

Basic Usage
Use the Text Node to store text content that will be passed as input to other nodes, such as AI prompts, web searches, API calls, or any node requiring text input.
Inputs
The Text node does not accept inputs from other nodes. It serves as a source node that provides text output to subsequent nodes.
Outputs
Output (Green Port)
Text Content: Outputs the text content stored in the node.
- Connects to green input ports of other nodes
- Passes the exact text from the Output field
- Can connect to multiple nodes simultaneously
- Text is passed as-is without processing
Configuration
Output Field
Text Content Area: Large text box where you enter the text content to be passed to other nodes.
Features:
- Multi-line text input
- Plain text (no Markdown rendering)
- Supports variable interpolation using labels (e.g.,
{{USERNAME}},{{SCORE}}) - Scrollable for long content
- No character limit
Example Content:
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Praesent rutrum, massa vel feugiat scelerisque, ipsum elit...
Encrypt the Text
Security Option: Checkbox to encrypt the text content stored in the node.
When to Enable:
- Storing sensitive information (API keys, passwords, credentials)
- Personal data that requires protection
- Confidential instructions or prompts
- Data subject to privacy regulations
When Disabled:
- Regular text content
- Public information
- Non-sensitive prompts and instructions
- Content that needs to be easily editable
Example Workflows
AI Prompt with Text Node
Scenario: Provide a system prompt to an AI processing node.

Steps to Create the Flow:
-
Add a Start Node.
-
Add a Text Node:
i. Configure the Output field:
You are a helpful biology tutor. Explain complex concepts
in simple terms that a high school student can understand.
Use examples and analogies to make the content engaging.ii. Leave "Encrypt the text" unchecked (not sensitive content)
-
Add an AI General Prompt node:
- Connect: Text node Output (green) → AI General Prompt "Overwrite System Prompt" (green)
- Configure other AI prompt settings as needed
-
Add Display Text node to show results:
- Connect: AI General Prompt Output → Display Text Input
Preview:
[Start] → [AI General Prompt]
↑ (System Prompt from Text Node)
→ [Display Text: Show AI Response]
Result: The AI uses the custom system prompt from the Text node to generate responses in the specified style.
Related Nodes
- Display Text: Shows text to users (Text node provides backend text)
- Create Text Label: Creates variables that Text node can reference
- Text Join: Combines multiple Text node outputs
- AI General Prompt: Receives prompts and instructions from Text node
- Web Search: Receives search queries from Text node
- API Call: Receives endpoints, headers, and payloads from Text node
- Multi-Turn Conversation: Receives instructions from Text node
- Local LLM Connector: Receives prompts from Text node
Text Node vs Display Text Node
| Feature | Text Node | Display Text Node |
|---|---|---|
| Purpose | Backend data supply | User-facing display |
| Visibility | Not shown to users | Shown to users |
| Output | Text data only | Text display + data |
| Formatting | Plain text | Markdown support |
| Use Case | Prompts, queries, data | Messages, instructions |
| Connection | Green port only | Green + Red ports |
| Encryption | Optional | Not available |
When to use Text Node:
- Supplying prompts to AI nodes
- Providing queries to search nodes
- Storing API parameters
- Backend configuration
- Data that shouldn't be displayed
When to use Display Text:
- Showing messages to users
- Displaying instructions
- Presenting results
- User-facing content
- Formatted text with Markdown
Security Considerations
Encrypting Sensitive Content
Always encrypt:
- API keys and tokens
- Database credentials
- Authentication information
- Personal identifiable information (PII)
- Proprietary algorithms or methods
Example:
Text Node: "API_KEY=sk-1234567890abcdef..."
✓ Enable "Encrypt the text"
Best Practices
- Principle of Least Exposure: Only store sensitive data when absolutely necessary
- Separate Credentials: Use dedicated Text nodes for sensitive data
- Regular Audits: Review which Text nodes contain sensitive content
- Access Control: Restrict who can edit flows with encrypted Text nodes
- Rotation: Update encrypted credentials regularly
Summary
The Text Node is a versatile utility for supplying text data throughout your workflows:
✓ Simple: Easy to configure and use
✓ Secure: Optional encryption for sensitive data
✓ Flexible: Supports variables and multi-line content
✓ Efficient: Instant processing, no overhead
✓ Reusable: One node can supply multiple targets
Master the Text node to create maintainable, organized workflows with clear separation between data supply and user display.