Skip to main content

ConvertBase64ToFile

Convert Base64 to File Node

The Convert Base64 to File node transforms Base64-encoded data into actual files within your workflow. This node is essential for processing encoded images, documents, or other file types that come from APIs, databases, or user uploads, converting them into usable files that can be saved, processed, or passed to other workflow steps.

What This Node Does​

This node takes Base64-encoded text data and converts it back into its original file format (images, PDFs, documents, etc.). You can choose to save the converted files to your system or simply pass the file data to the next node in your workflow. This is particularly useful when working with APIs that return files as Base64 strings or when processing uploaded content that needs to be converted back to its original format.

Configuration Parameters​

Data Source Section​

Base64 Value Expression

  • Field Name: base64GetterTemplate
  • Type: Smart text field with dynamic data support
  • Default Value: Empty
  • Simple Description: Specifies where to find the Base64-encoded data in your workflow
  • When to Change This: Always configure this to point to the data field containing your Base64 string
  • Business Impact: Incorrect configuration here means no files will be converted

File Extension - Property Path

  • Field Name: fileExtGetterTemplate
  • Type: Smart text field with dynamic data support
  • Default Value: Empty
  • Simple Description: Tells the node what file extension to use for the converted file (jpg, pdf, png, etc.)
  • When to Change This: Set this to match the original file type of your Base64 data
  • Business Impact: Wrong extension can make files unopenable or cause compatibility issues

Processing Section​

Save File

  • Field Name: saveFile
  • Type: Toggle switch (On/Off)
  • Default Value: Off
  • Simple Description: Controls whether converted files are saved to your system storage
  • When to Change This:
    • On: When you need to permanently store the converted files for later use
    • Off: When you only need to pass the file data to the next workflow step
  • Business Impact: Enabling saves storage space for file archives; disabling saves system storage

Folder Path (appears when Save File is enabled)

  • Field Name: folderPath
  • Type: Smart text field with location support
  • Default Value: "base64_decoder"
  • Simple Description: Specifies the folder where converted files will be saved
  • When to Change This: Customize the storage location for different file types or organizational needs
  • Business Impact: Proper folder organization makes files easier to find and manage

Output Section​

Option

  • Field Name: outTransformId
  • Type: Dropdown menu with options:
    • Original with appended result column: Keeps all original data and adds the converted file information as a new column
    • Return result column only: Returns only the file conversion results, removing original data
  • Default Value: "Original with appended result column"
  • Simple Description: Determines what data gets passed to the next workflow step
  • When to Change This: Choose "Return result column only" when you only need the file data for subsequent steps
  • Business Impact: Affects data structure and what information is available in later workflow steps

Result Property Name

  • Field Name: outColumnName
  • Type: Text field
  • Default Value: "file_result"
  • Simple Description: Names the column that will contain the converted file information
  • When to Change This: Use descriptive names like "converted_image" or "processed_document" for clarity
  • Business Impact: Clear naming makes data easier to reference in subsequent workflow steps

Real-World Use Cases​

Document Processing System​

Business Situation: A legal firm receives client documents through an API that returns files as Base64 strings, and they need to convert these into actual PDF files for their document management system.

What You'll Configure:

  • Set "Base64 Value Expression" to point to the API response field containing the encoded document
  • Enter "pdf" in the "File Extension" field
  • Enable "Save File" toggle
  • Set "Folder Path" to "client_documents/incoming"
  • Choose "Original with appended result column" to keep client metadata
  • Name the result column "processed_document"

What Happens: Each Base64 document string gets converted to a PDF file, saved in the specified folder, and the file path is added to your data for tracking.

Business Value: Eliminates manual file conversion, ensures proper document storage, and maintains audit trails for client files.

E-commerce Image Processing​

Business Situation: An online store receives product images from suppliers as Base64 data and needs to convert them to image files for their website catalog.

What You'll Configure:

  • Point "Base64 Value Expression" to the supplier data field with encoded images
  • Set "File Extension" to dynamically read from supplier data (jpg, png, etc.)
  • Enable "Save File" for permanent storage
  • Set "Folder Path" to "product_images/{{supplier_name}}"
  • Use "Return result column only" if you only need file paths for the next step
  • Name result column "product_image_path"

What Happens: Supplier images are automatically converted and organized by supplier in your file system, ready for website upload.

Business Value: Streamlines product catalog updates, reduces manual image processing time by 85%, and ensures consistent file organization.

Customer Avatar Processing​

Business Situation: A social platform allows users to upload profile pictures through a mobile app that sends images as Base64 data, requiring conversion to standard image files.

What You'll Configure:

  • Set "Base64 Value Expression" to the user upload field
  • Configure "File Extension" to "jpg" for consistency
  • Enable "Save File" to store user avatars
  • Set "Folder Path" to "user_avatars/{{user_id}}"
  • Keep "Original with appended result column" to maintain user data
  • Name result column "avatar_file_path"

What Happens: User profile pictures are automatically converted and saved with proper file paths stored in user records.

Business Value: Enables seamless user experience, maintains organized file storage, and provides file references for profile display.

Step-by-Step Configuration​

Adding the Node​

  1. Drag the "Convert Base64 to File" node from the left panel onto your workflow canvas
  2. Connect it to the previous node that provides your Base64 data using the arrow connector

Configuring Data Source​

  1. Click on the Convert Base64 to File node to open the settings panel
  2. In the "Data Source" section, click on the "Base64 Value Expression" field
  3. Select the data field from your previous node that contains the Base64 string
  4. In the "File Extension" field, either:
    • Type a fixed extension like "pdf" or "jpg"
    • Select a data field that contains the file extension information

Setting Up Processing Options​

  1. In the "Processing" section, toggle "Save File" on if you want to store the converted files
  2. If saving files, enter your desired folder path in the "Folder Path" field
  3. You can use dynamic folder names with data from previous nodes

Configuring Output​

  1. In the "Output" section, choose your preferred option from the dropdown:
    • Select "Original with appended result column" to keep all existing data
    • Select "Return result column only" if you only need the file conversion results
  2. Enter a descriptive name in "Result Property Name" for easy reference in later steps

Testing Your Setup​

  1. Click the "Test Configuration" button
  2. Provide sample Base64 data in the test panel
  3. Verify that files are converted correctly and saved in the expected location
  4. Check that the output data structure matches your needs
  5. Save your configuration when satisfied

Industry Applications​

Healthcare Organizations​

Common Challenge: Medical imaging systems export scans as Base64 data that needs conversion to standard image formats for patient records and specialist consultations.

How This Node Helps: Automatically converts medical imaging data to viewable formats while maintaining proper file organization and patient data associations.

Configuration Recommendations:

  • Use patient ID in folder path for HIPAA compliance
  • Set consistent file extensions based on imaging type
  • Enable file saving for permanent medical records
  • Use descriptive result column names like "patient_scan_file"

Results: Reduces imaging processing time by 70% and ensures compliant file storage for medical records.

Financial Services​

Common Challenge: Banks receive document scans and signatures as Base64 data from mobile apps and need to convert them to standard formats for compliance and record-keeping.

How This Node Helps: Processes encoded financial documents into proper file formats while maintaining audit trails and secure storage.

Configuration Recommendations:

  • Organize files by account number and document type
  • Use secure folder paths with appropriate access controls
  • Maintain original data for compliance tracking
  • Implement consistent naming conventions

Results: Improves document processing efficiency by 60% and ensures regulatory compliance for digital banking operations.

Marketing Agencies​

Common Challenge: Creative teams receive client assets and campaign materials as Base64 data from various sources and need them converted to working files.

How This Node Helps: Streamlines asset conversion and organization for creative workflows while maintaining project structure.

Configuration Recommendations:

  • Organize files by client and campaign
  • Support multiple file formats (images, videos, documents)
  • Use descriptive folder structures for easy asset location
  • Maintain metadata for asset tracking

Results: Reduces asset preparation time by 50% and improves creative team productivity through automated file organization.

Best Practices​

File Organization​

  • Use descriptive folder paths that include relevant identifiers
  • Implement consistent naming conventions across your organization
  • Consider date-based folder structures for time-sensitive content
  • Plan for file cleanup and archival processes

Data Management​

  • Always test with sample data before processing large batches
  • Monitor storage usage when saving files permanently
  • Consider file size limits and processing capacity
  • Implement error handling for corrupted Base64 data

Security Considerations​

  • Ensure proper access controls on saved file locations
  • Consider encryption for sensitive file content
  • Implement audit trails for file conversion activities
  • Follow data retention policies for converted files

Performance Optimization​

  • Process files in appropriate batch sizes
  • Monitor conversion times for large files
  • Consider storage location performance impact
  • Plan for peak usage scenarios

This node is essential for any workflow that handles encoded file data, providing the bridge between Base64 strings and usable files while maintaining proper organization and data flow throughout your automation process.