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 data conversion capabilities focused on the "Base64 to Binary" operation within the broader "Base64" resource. Specifically, it decodes Base64-encoded strings into binary data. This is useful when you receive data encoded in Base64 (commonly used for transmitting binary files or images as text) and need to convert it back into its original binary form for further processing or storage.

Practical scenarios include:

  • Decoding Base64-encoded file contents received from APIs or webhooks to save or manipulate the original file.
  • Converting Base64 image data into binary format for uploading to file storage or sending to other systems expecting binary input.
  • Processing encoded attachments or media data within automation workflows.

Properties

Name Meaning
Output Binary Whether the output should be provided as binary data instead of a Base64 string.
Binary Property Name The name of the binary property to use for the output binary data if "Output Binary" is enabled.

Output

  • If Output Binary is set to false (default), the output JSON contains a Base64 string representation of the decoded binary data under the result field.
  • If Output Binary is set to true, the output contains no JSON data but includes a binary property named as specified by Binary Property Name (default "data"). This binary property holds the raw decoded binary data with MIME type "application/octet-stream" and filename "file".

Dependencies

  • No external services or API keys are required.
  • The node relies on internal utility functions for Base64 decoding and binary data handling.
  • No special environment variables or n8n credentials are needed.

Troubleshooting

  • Common issues:

    • Input Base64 string is invalid or malformed, causing decoding errors.
    • Forgetting to enable "Output Binary" when downstream nodes expect binary data.
    • Incorrect binary property name leading to missing or inaccessible binary data.

  • Error messages:

    • Errors related to invalid Base64 input will typically indicate decoding failure.
    • If binary data is requested but the specified binary property does not exist or is misspelled, subsequent nodes may fail to find the data.

  • Resolutions:

    • Ensure the Base64 input string is correctly formatted and complete.
    • Enable "Output Binary" if the next steps require binary data.
    • Double-check the binary property name matches what downstream nodes expect.

Links and References

Discussion