Skip to main content
String nodes handle post text, author values, addresses, names, tickers, and other text. Most are pure data operations and work well inside pure functions.

​
Find And Validate Text

Use Extract Solana Pubkeys instead of a length-only or character-only check when the requirement is a valid Solana address. Its Pubkeys output preserves valid addresses in text order, and Matched? reports whether at least one was found. Pair Pubkeys with Get At Index at index 0 when the first valid address should win, then handle the optional selected value before connecting it to a required input. The extractor excludes surrounding punctuation and rejects characters outside the Base58 alphabet, including 0, O, I, and l. Cover those boundaries with tests instead of cleaning an address-like string and assuming it is valid.
State address-selection behavior explicitly in tests. A post containing an invalid candidate followed by a valid public key should prove whether the graph skips the invalid text and selects the first valid key.
Regex nodes use Rust-compatible patterns. Lookbehind and backreferences are not supported. Invalid patterns do not produce successful matches.

​
Format And Measure Text

String Slice uses zero-based positions and excludes the end position. To use the first four characters of an address, set Start to 0 and End to 4.

​
Replace And Combine Text

​
Detect Or Translate Chinese Text

Detect Chinese reports whether text contains Chinese and whether it is mixed with alphanumeric non-Chinese text. Translate to Chinese is an impure, execution-driven node because it uses a translation service. A translation failure terminates that execution path; the node does not provide a failure branch. Avoid calling it for content that does not need translation, and do not place required follow-up work after it unless stopping on failure is acceptable.