ComfyUI Node: Text String

Text String:

The Text String node is designed to handle and process multiple text strings simultaneously, making it a versatile tool for text manipulation tasks. This node allows you to input up to four different text strings, which it then processes to parse any embedded tokens. The primary benefit of this node is its ability to handle multiple text inputs in a single operation, streamlining workflows that involve complex text manipulations. By parsing tokens within the text, it ensures that any dynamic or placeholder content is appropriately resolved, making it particularly useful for generating dynamic prompts or preparing text for further processing in AI art projects.

Text String Input Parameters:

text

This parameter accepts a single text string as input. It is the primary text that will be processed by the node. The default value is an empty string, and it does not support multiline input. This parameter is essential for the node's operation as it forms the base text that will be parsed for tokens.

text_b

This optional parameter allows you to input a second text string. Like the primary text parameter, it is processed to parse any embedded tokens. The default value is an empty string, and it does not support multiline input. This parameter is useful when you need to handle multiple text strings in a single operation.

text_c

This optional parameter allows you to input a third text string. It functions similarly to the text and text_b parameters, parsing any tokens within the text. The default value is an empty string, and it does not support multiline input. This parameter provides additional flexibility for handling multiple text inputs.

text_d

This optional parameter allows you to input a fourth text string. It is processed in the same way as the other text parameters, with the node parsing any tokens within the text. The default value is an empty string, and it does not support multiline input. This parameter is useful for scenarios where you need to manage and process multiple text strings simultaneously.

Text String Output Parameters:

text

This output parameter returns the processed version of the primary text input, with all tokens parsed and resolved. It is essential for verifying the final text after token parsing.

text_b

This output parameter returns the processed version of the second text input, with all tokens parsed and resolved. It allows you to see the final text after token parsing for the second input.

text_c

This output parameter returns the processed version of the third text input, with all tokens parsed and resolved. It provides the final text after token parsing for the third input.

text_d

This output parameter returns the processed version of the fourth text input, with all tokens parsed and resolved. It shows the final text after token parsing for the fourth input.

Text String Usage Tips:

• Use the Text String node to handle multiple text inputs in a single operation, which can save time and streamline your workflow.
• Ensure that all text inputs are properly formatted and free of unnecessary whitespace to avoid unexpected results during token parsing.
• Utilize the optional text_b, text_c, and text_d parameters when you need to process multiple text strings simultaneously, rather than creating separate nodes for each text input.

Text String Common Errors and Solutions:

"Token parsing failed"

• Explanation: This error occurs when the node encounters an issue while parsing tokens within the text.
• Solution: Check the text inputs for any malformed or unsupported tokens and correct them. Ensure that all tokens are properly formatted and recognized by the node.

"Empty text input"

• Explanation: This error occurs when the primary text input is empty, and no optional text inputs are provided.
• Solution: Provide at least one non-empty text input to ensure the node has content to process. Verify that the text parameter is not left blank.

"Unsupported character in text"

• Explanation: This error occurs when the text input contains characters that are not supported by the node.
• Solution: Remove or replace any unsupported characters in the text input. Ensure that the text only contains valid characters for token parsing.