Skip to main content

Conversion

The Conversion node transforms files from one format to another, enabling seamless data integration between systems that use different file formats. This is essential for processing logistics data that comes in various formats from different carriers, vendors, and systems.

Overview​

The Conversion node is essential when you need to:

  • Format standardization - Convert various input formats to a standard processing format
  • System integration - Bridge systems that use different data formats
  • Data processing - Transform files into formats suitable for analysis or storage
  • Legacy system support - Convert older file formats to modern standards
  • API compatibility - Transform data formats for external API consumption
  • Workflow optimization - Convert files to formats that work best with downstream processes

Supported Conversions​

Currently Available​

  • XML to JSON - Convert XML documents to JSON format for easier processing

Configuration​

Input Settings​

  • Source format - Specify the input file format
  • File source - Upload file or use output from previous workflow nodes
  • Encoding - Character encoding for text-based formats (UTF-8, ASCII, etc.)
  • Validation - Validate input format before conversion

Output Settings​

  • Target format - Choose the desired output format
  • Output filename - Specify name for converted file (optional)

Example Usage & Common Use Cases​

XML to JSON Conversion​

Carrier Data Processing:
  Receive XML tracking update → Convert to JSON → Process with standard workflow

Configuration:
  Source Format: XML
  Target Format: JSON
  Input: carrier_tracking_update.xml
  Preserve Structure: true
  Pretty Print: true

Input XML:
<shipment>
  <tracking_number>ABC123456</tracking_number>
  <status>In Transit</status>
  <location>Chicago, IL</location>
  <timestamp>2024-01-15T10:30:00Z</timestamp>
</shipment>

Output JSON:
{
  "shipment": {
    "tracking_number": "ABC123456",
    "status": "In Transit",
    "location": "Chicago, IL",
    "timestamp": "2024-01-15T10:30:00Z"
  }
}

Conversion Features​

Data Preservation​

  • Structure integrity - Maintain hierarchical relationships in data
  • Data type preservation - Keep appropriate data types (strings, numbers, booleans)
  • Attribute handling - Preserve XML attributes and metadata
  • Namespace support - Handle XML namespaces appropriately

Advanced Features​

Integration Capabilities​

  • Workflow chaining - Use converted files in subsequent workflow steps
  • Dynamic configuration - Adjust conversion settings based on workflow data
  • Conditional conversion - Convert only when certain conditions are met
  • Output routing - Send converted files to different destinations

Best Practices​

Input Validation​

  • Format verification - Confirm input files match expected format
  • Schema validation - Validate against known schemas when available
  • Size limits - Set appropriate limits for file sizes
  • Content scanning - Check for malicious content in input files

Performance Optimization​

  • Streaming processing - Handle large files efficiently
  • Memory management - Optimize memory usage for large conversions
  • Caching - Cache conversion results for repeated operations
  • Batch sizing - Optimize batch sizes for performance

Quality Assurance​

  • Output validation - Verify converted files meet quality standards
  • Data integrity checks - Ensure no data loss during conversion
  • Format compliance - Verify output conforms to target format specifications

Error Management​

  • Graceful degradation - Continue processing when possible despite errors
  • Detailed logging - Capture conversion details for troubleshooting
  • Retry mechanisms - Implement retry logic for transient failures
  • Fallback options - Provide alternative processing paths for failed conversions

Integration Patterns​

With File Processing​

File Upload → Conversion Node → Spreadsheet Node → Data Processing

With API Integration​

Receive Data → Conversion Node → HTTP Request → External System

With Conditional Logic​

File Input → If Node (format check) → Conversion Node (if needed) → Standard Processing

With Loops​

File List → Loop → Conversion Node (per file) → Collect Results → Summary

Troubleshooting​

Common Issues​

  • Format detection failures - Verify input file format and structure
  • Conversion errors - Check for malformed or invalid input data
  • Character encoding problems - Ensure proper encoding configuration

Debugging Tips​

  • Test with simple files - Start with basic, well-formed input files
  • Validate input format - Confirm input files are properly formatted
  • Check conversion settings - Verify configuration matches requirements

The Conversion node provides essential format transformation capabilities for logistics workflows, enabling seamless integration between systems that use different data formats and standards.