Data Converter icon

Data Converter

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

Actions49

Overview

The node provides a versatile "Data Converter" tool that supports multiple data format transformations, including Base64 encoding and decoding. Specifically, the Base64 to Text operation decodes a Base64-encoded string back into its original text form.

This operation is useful in scenarios where data has been encoded in Base64 for safe transmission or storage (e.g., embedding images or files in text-based formats, or transferring binary data over protocols that only support text) and needs to be converted back to readable text for further processing or display.

Practical examples:

  • Decoding Base64-encoded email content or attachments.
  • Converting Base64 strings received from APIs or webhooks back into human-readable text.
  • Processing Base64-encoded configuration or JSON data embedded in text fields.

Properties

Name Meaning
Input Data The Base64-encoded string to decode back into text.
Binary Property Name (Optional) When outputting binary data instead of text, this defines the name of the binary property holding the decoded data.

Output

The output JSON contains a field named result which holds the decoded text string obtained from the Base64 input.

If the user opts to output binary data instead of text (via an additional option), the node outputs the decoded data as binary under the specified binary property name. This binary data represents the raw decoded bytes corresponding to the Base64 input.

Example JSON output when decoding Base64 to text:

{
  "result": "Decoded plain text string"
}

If outputting binary, the output will have an empty JSON object and a binary property with the decoded data buffer.

Dependencies

  • No external services or API keys are required.
  • The node uses internal utility functions for Base64 operations.
  • No special environment variables or n8n configurations are necessary.

Troubleshooting

  • Invalid Base64 input: If the input string is not valid Base64, the node may throw an error indicating decoding failure. Ensure the input is properly Base64-encoded.
  • Empty input: Providing an empty string as input will result in an empty output string.
  • Binary output issues: If choosing to output binary data, ensure the binary property name is correctly set and downstream nodes can handle binary data.
  • Character encoding: The decoded text assumes UTF-8 encoding. If the original data used a different encoding, the output text might appear garbled.

Links and References

Discussion