Text Replace Node

The Text Replace node belongs to the “Text Processing” category. It replaces every occurrence of a target string with new content inside your workflow text. Typical use cases include template rendering, placeholder cleanup, and post-processing of model outputs.

Node Configuration

Basic Settings

1. Node Name

   • Assign a descriptive name such as “Replace Customer Salutation”
   • The output variable uses this name as its prefix (for example, $Replace Customer Salutation.text)

2. Text Source

   • Select the upstream variable that provides the text to process
   • Supports context references like $input.content or $LLM.output

3. Search For

   • Define the original string you want to locate and replace
   • Accepts literal text only; context variables are not expanded

4. Replace With

   • Provide the replacement string
   • Accepts literal text only; leave it empty to remove the target text entirely

5. Output Variable

   • Defaults to text
   • Refer to the processed result in downstream nodes with $NodeName.text

How It Works

• Only the “Text Source” field expands context variables at runtime. The engine resolves $node.field placeholders within the text, while “Search For” and “Replace With” are treated as literal values.
• When the “Search For” field is empty, the node raises an error and stops execution to prevent accidental data loss.
• Escape the dollar sign with a backslash (for example, \$variable) if you need to keep the literal text.

Usage Example

The following example removes a fixed tag from an LLM response:

1. Suppose the LLM node output contains a signature line such as:

   [Disclaimer] This response is for reference only.

2. Configure the Text Replace node:

   Text: $LLM.output
   Search For: [Disclaimer]
   Replace With: (leave empty)

3. Reference $Text Replace.text in a Content Combiner or Output node to display the cleaned response.

Advanced Use Cases

Clean Up Model Responses

Run a Text Replace node after an LLM to standardize typos, strip unwanted guidance phrases, or mask sensitive data with placeholders.

Pair with Loops or Branches

Combine with loop nodes to process each list item, or branch-specific replacements to deliver tailored messages for different segments.

Template Placeholder Handling

Use the node to swap fixed placeholders with predetermined wording after composing text in a Content Combiner or template node.

Best Practices

• Clear Naming: Use an “action + target” naming style such as “Replace SKU Code” for easier debugging.
• Validate Inputs: Confirm the target text actually appears in the source; a Content Combiner preview helps catch mistakes quickly.
• Step-by-Step Debugging: Split multiple replacements into separate Text Replace nodes so each output stays predictable.
• Keep It Idempotent: Avoid adding repeated suffixes or markers when the workflow may run more than once on the same content.

Common Issues

Caution

• Empty search string: The node throws an error; verify the “Search For” field is filled or referenced correctly.
• Variable expansion unexpected: Remember that “Search For” and “Replace With” do not expand context variables; placeholders remain unchanged.
• Regex requirements: The node handles plain text replacements only. Use a code execution node if you need regular expressions.