String Operation
String Operation node for Builder — apply text transformations including trim, replace, split, concatenate, upper/lower case, and regex substitution to string fields in a workflow.
🎯 Purpose
Section titled “🎯 Purpose”The String Operation node provides text manipulation capabilities for cleaning, formatting, and restructuring text data. It supports operations like joining arrays, splitting text, replacing content, extracting substrings, trimming whitespace, and changing case. This makes it a versatile utility node for preparing text data in automation workflows.
📥 Inputs
Section titled “📥 Inputs”- Text / Array Input (String or Array, Required): The text or array of text values from a previous node to be transformed.
📤 Outputs
Section titled “📤 Outputs”- Transformed Text: A new property containing the manipulated text according to the selected operation.
- Structured Output: Can either include all original data plus the new property, or only the transformed text, depending on output settings.
⚙️ Parameters
Section titled “⚙️ Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| String Operation | Dropdown | No | Join (array to string) | Operation to perform. Options: Join, Replace, Split, Substring, Trim, Upper case, Lower case. |
| Property Name | String | Yes | (empty) | Property containing the source text or array. |
| Delimiter | String | No | (empty) | Separator used when joining arrays into a single string. |
| Find | String | No | (empty) | The text pattern to find for replacement. |
| Replace By | String | No | (empty) | The text to replace matches with. |
| Split Delimiter | String | No | (empty) | The delimiter used to split strings into arrays. |
| Substring Start | Number | No | 0 | Start index for substring extraction (0-based). |
| Substring End | Number | No | 2 | End index for substring extraction (exclusive). |
| Option | Dropdown | No | Original with appended result column | Controls output: keep original data with result, or return only the result. |
| Result Property Name | String | No | string_result | Name of the property containing the transformed text. |
💡 Example Usage
Section titled “💡 Example Usage”Customer Data Standardization
Section titled “Customer Data Standardization”- Setup: Replace unwanted characters in
phone_numberand name resultclean_phone_number. - Result: Standardized phone numbers (e.g.,
"1234567890").
Product Description Summaries
Section titled “Product Description Summaries”- Setup: Substring
product_descriptionfrom 0–100 →short_description. - Result: Short previews for mobile app listings.
Email List Management
Section titled “Email List Management”- Setup: Split
customer_tagsby","→tag_array. - Result:
"premium,loyal,newsletter"→["premium", "loyal", "newsletter"].
Address Formatting
Section titled “Address Formatting”- Setup: Join address parts array with
", "→formatted_address. - Result:
"123 Main St, Springfield, IL 62701".
📘 Best Practices
Section titled “📘 Best Practices”- Use Trim before other operations to clean unwanted whitespace.
- Chain multiple String Operation nodes for complex transformations.
- Prefer Return result column only if the original data is not needed downstream.
- Always test delimiters and substring indices with sample data.
- Use descriptive output names like
clean_email,formatted_phone,short_title.
🧪 Test Cases
Section titled “🧪 Test Cases”- Given:
["Alice", "Bob", "Charlie"]with Join,Delimiter = ", "→
Expected:"Alice, Bob, Charlie" - Given:
"Hello World"with Replace,find = "World",Replace By = "Threo"→
Expected:"Hello Threo" - Given:
"red,blue,green"with Split,delimiter = ","→
Expected:["red", "blue", "green"] - Given:
"ProductCode12345"with Substring,start = 0,end = 11→
Expected:"ProductCode" - Given:
" spaced text "with Trim →
Expected:"spaced text"