Data Converter icon

Data Converter

Convert between various data formats - Base64, Binary, JSON, XML, YAML, CSV, HTML, and more
Join our community

Actions49

Overview

This node applies multiple string transformation operations sequentially on input text data. It is useful when you need to perform a series of text manipulations in one step, such as cleaning filenames, changing case styles (camelCase, snake_case, kebab-case), removing special characters, padding text, truncating, or parsing email addresses.

Practical examples include:

  • Preparing user input for URLs by slugifying and lowercasing.
  • Cleaning and formatting filenames before saving files.
  • Extracting parts of an email address from raw strings.
  • Formatting text content for display or further processing by applying multiple transformations like trimming whitespace, capitalizing, and truncating.

Properties

Name Meaning
Operations A collection of string operations to apply in sequence. Each operation has:
- Operation: The type of string transformation to apply. Options include:
Camel Case, Capitalize First, Clean Filename, Kebab Case, Lower Case, Normalize Whitespace, Pad Text, Parse Email Address, Remove Code Block Markers, Remove Special Characters, Reverse Text, Slugify, Snake Case, Title Case, Truncate, Upper Case.
- Options: Additional parameters specific to the selected operation, such as:
  • Keep File Extension (boolean)
  • Keep Filename Characters (boolean)
  • Keep Numbers (boolean)
  • Keep Spaces (boolean)
  • Length (number, for Truncate)
  • Pad Character (string, for Pad Text)
  • Pad Length (number, for Pad Text)
  • Pad Side (left, right, both, for Pad Text)
  • Suffix (string, for Truncate)
Input Data The input text string to transform. This is required.
Binary Property Name (Optional) Name for the output binary property if the node outputs binary data.

Output

The node outputs JSON with a result field containing the transformed string after all specified operations have been applied in order.

If an operation returns an object (e.g., parsing an email address), its properties are merged into the output JSON alongside the result string.

Example output JSON structure:

{
  "result": "transformed string",
  "name": "extracted name",        // example if parseEmailAddress was used
  "email": "extracted email",
  "domain": "extracted domain"
}

No binary output is produced by this operation itself.

Dependencies

  • No external services or API keys are required.
  • Uses internal utility functions for string manipulation bundled within the node's codebase.
  • No special environment variables or n8n configurations needed.

Troubleshooting

  • Empty or unchanged output: Ensure that the input data is provided and that the operations list is not empty.
  • Invalid options for operations: Some operations require specific options (e.g., length for truncate). Missing or invalid options may cause unexpected results.
  • Error messages: If an error occurs during processing, it will be reported with the item index and error message. Common causes include invalid input types or malformed option values.
  • To resolve errors, verify input data correctness and review each operation's options for validity.

Links and References

Discussion