Text

1. Overview

The Text tool is a built-in GoInsight utility designed for performing common text processing and manipulation tasks directly within your workflows. It provides a suite of powerful operations to parse, format, and transform string data without needing external services.

With the GoInsight Text node, you can seamlessly integrate text manipulation into your automation processes. Key capabilities include:

• Searching and Replacing: Find specific text or patterns within a larger string and replace them.
• Parsing and Splitting: Break down a single string into a list of substrings based on a specified delimiter.
• Formatting: Convert text into a URL-friendly "slug" format.
• Content Conversion: Extract clean, readable text from raw HTML content.

2. Prerequisites

As a built-in GoInsight utility, the Text tool does not require any external accounts or special permissions. It is available for use in all workflows by default.

3. Credentials

The Text tool is a core GoInsight feature and does not require any credentials for its use.

4. Supported Operations

Summary

This node provides a range of operations for text manipulation, formatting, and conversion. The table below summarizes the available actions.

Operation Details

Find Text

Finds occurrences of a search value in the input text.

Input Parameters:

• Text: Input text to process.
• SearchValue: A plain text string or regex pattern to search for.

Output:

• Found (bool): Indicates whether any matches were found.
• TotalMatches (number): The total number of matches found.
• Matches (string-array): List of matched text segments.
• FirstMatchText (string): The first matched text segment, or empty string if no match.

HTML to Text

Cleans HTML content and extracts text, converting only headings into Markdown to preserve hierarchy.

Input Parameters:

• HtmlContent: The raw HTML string to be cleaned, must be a non-empty HTML document or fragment.

Output:

• Content (string): The resulting text in Markdown format, preserving heading hierarchy; contains the cleaned content with tags removed except headings.

Replace

Replaces occurrences of a search value in the input text with a specified replace value.

Input Parameters:

• Text: Input text to process.
• SearchValue: A plain text string or regex pattern to search for.

Options:

• ReplaceValue: The string to replace matches with, which can be plain text or a regex expression.
• ReplaceOnlyFirstMatch: Whether to replace only the first match (true) or all matches (false).

Output:

• Text (string): The resulting text after replacement, original text if an error occurs.
• Success (bool): Indicates whether the replacement was successful.
• ErrorMessage (string): Error message if replacement fails, empty if successful.

Slugify String

Converts a given text into a URL-friendly slug format.

Input Parameters:

• Text: The input string to be converted into a slug.

Output:

• Slug (string): The generated slug string.

Split Text

Splits the input text by the specified delimiter and returns a list of substrings. Supports optional trimming of each element and filtering out empty strings.

Input Parameters:

• Text: The input text to split.
• Delimiter: The delimiter string to split by. Must be non-empty.

Options:

• TrimEach: Indicating whether to remove leading and trailing whitespace from each split element
• FilterEmpty: Indicating whether to exclude empty strings from the split results.

Output:

• splitResult (string-array): A list of substrings resulting from the split.

5. Example Usage

This section will guide you through creating a simple workflow to parse a comma-separated string of tags into an array of individual tags using the Split Text operation.

The workflow will consist of three nodes: Start -> Split Text -> Answer.

1. Add the Text Node
   • In the workflow canvas, click the + icon to add a new node.
   • Select the "Tools" tab in the pop-up panel.
   • Find and select "Text" from the list of tools.
   • From the list of supported operations for Text, click on Split Text to add the node to your canvas.
2. Configure the Node
   • Click on the newly added Split Text node to open its configuration panel on the right.
   • Credentials: This tool is built-in, so no credentials are required.
   • Parameter Configuration: Fill in the input parameters as follows:
   • Text: Enter the string you want to split. You can use a static value like "goinsight, automation, workflow" or a variable from a previous node, such as {{start.tags}}.
   • Delimiter: Enter the character you want to split by. For our example, this would be a comma: ,.
   • TrimEach: Leave this as the default true to automatically remove any leading or trailing whitespace from each tag (e.g., " automation " becomes "automation").
3. Run and Validate
   • Once the parameters are configured, any error indicators on the canvas should disappear.
   • Click the "Run" button in the top-right corner of the canvas to execute the workflow.
   • After a successful run, click the "Logs" icon to view the detailed input and output of the Split Text node. You should see an output named splitResult containing a JSON array: ["goinsight", "automation", "workflow"].

After completing these steps, your workflow is ready. When executed, it will successfully take a single string of tags and convert it into a structured array, which can then be used in subsequent nodes for looping or other processing tasks.

6. FAQs

Q: Why isn't my Find Text or Replace operation working with special characters like . or +?

A: The SearchValue field in these operations supports regular expressions (regex). In regex, characters like ., +, *, ?, (, ) have special meanings. If you want to match these characters literally, you need to "escape" them with a backslash.

• To find a literal period (.), use \. as your SearchValue.
• To find a literal plus sign (+), use \+ as your SearchValue.

Q: The Split Text node is returning an empty list or fewer items than I expected. What could be wrong?

A: Please check the following:

• Delimiter Mismatch: Ensure the Delimiter you specified actually exists in the input Text. For example, splitting a tab-separated string with a comma will not produce the desired result.
• FilterEmpty Option: The FilterEmpty option is enabled by default. If your input text contains consecutive delimiters (e.g., "apple,,banana") or starts/ends with a delimiter, the resulting empty strings will be removed from the output. If you need to keep these empty entries, set FilterEmpty to false.

Q: How do I handle multi-line text in the input fields?

A: The input fields for the Text node fully support multi-line strings. You can paste or pass multi-line text directly into parameters like Text or HtmlContent. The operations will process the entire text block as a single string, including newline characters (\n).

7. Official Documentation

For more information on built-in utilities and advanced workflow patterns, please refer to the official GoInsight documentation: GoInsight Built-in Tools Guide.