Skip to main content

ConvertFromJSON

Convert From JSON Node

The Convert From JSON node transforms JSON data into individual data fields that can be used by other nodes in your workflow. This node is essential when you receive structured data from APIs, databases, or other sources and need to extract specific information for further processing.

What This Node Does​

The Convert From JSON node takes complex JSON data and breaks it down into separate, usable pieces of information. Instead of working with one large data structure, you can access individual values like customer names, order numbers, or product details as separate data points in your workflow.

Business Value: Eliminates manual data extraction tasks and enables automated processing of structured information from various sources, saving hours of manual work and reducing data handling errors.

Configuration Parameters​

Convert Only Object Properties​

Field Name: useCustomPropsOnly Type: Toggle switch (On/Off) Default Value: Off Simple Description: Controls whether to convert all JSON data or only specific properties you choose When to Change This:

  • Turn On when you only need specific pieces of information from large JSON files
  • Turn Off when you want to convert all available data Business Impact:
  • On: Processes only the data you specify, making workflows faster and more focused
  • Off: Converts all available data, giving you access to everything but potentially slowing processing

Property Names to Convert​

Field Name: customPropsOnly Type: Smart text field with data suggestions Default Value: Empty Simple Description: Specify which JSON properties to convert by listing their names separated by commas When to Change This: Only appears when "Convert Only Object Properties" is enabled. Enter the exact names of the data fields you want to extract Business Impact: Focusing on specific properties reduces processing time and makes your workflow results cleaner and more organized

Expected Format: Comma-separated property names Examples:

  • customerName, orderNumber, totalAmount
  • firstName, lastName, email, phoneNumber
  • productId, price, inventory

Real-World Use Cases​

E-commerce Order Processing​

Business Situation: Your online store receives order data from your shopping cart system in JSON format, but you need individual fields like customer name, shipping address, and order total for different automation tasks.

What You'll Configure:

  • Toggle "Convert Only Object Properties" to On
  • Enter customerName, shippingAddress, orderTotal, orderDate in the property names field
  • Connect the output to separate nodes for email notifications, shipping labels, and accounting

What Happens: The node extracts only the customer information you need, making it available as separate data points for your email system, shipping processor, and accounting software.

Business Value: Reduces order processing time from 15 minutes to 2 minutes per order and eliminates data entry errors.

Customer Support Ticket Routing​

Business Situation: Support tickets arrive as JSON data containing customer details, issue categories, and priority levels. You need to route tickets to the right departments based on specific information.

What You'll Configure:

  • Enable "Convert Only Object Properties"
  • Specify customerTier, issueCategory, priorityLevel, customerEmail as the properties to extract
  • Connect outputs to conditional routing nodes for different support teams

What Happens: Each ticket's key information becomes available as individual data points, allowing automatic routing to technical support, billing, or account management teams.

Business Value: Improves response times by 60% and ensures tickets reach the right specialist immediately.

Marketing Campaign Data Processing​

Business Situation: Your marketing platform exports campaign results as JSON files containing engagement metrics, customer segments, and conversion data that need to be processed for reporting.

What You'll Configure:

  • Turn off "Convert Only Object Properties" to capture all campaign metrics
  • Connect to data analysis and reporting nodes
  • Set up automated report generation based on the extracted metrics

What Happens: All campaign data becomes accessible as individual metrics for automated analysis, report generation, and performance tracking.

Business Value: Eliminates 8 hours of weekly manual report preparation and provides real-time campaign insights.

Step-by-Step Configuration​

Adding the Node​

  1. Drag the "Convert From JSON" node from the Data Processing section onto your workflow canvas
  2. Connect it to a node that provides JSON data (like an API call or file reader)
  3. Click on the Convert From JSON node to open its configuration panel

Basic Setup (Convert All Data)​

  1. Leave the "Convert Only Object Properties" toggle in the Off position
  2. The node will automatically convert all properties in your JSON data
  3. Click "Save Configuration" to apply your settings

Advanced Setup (Convert Specific Properties)​

  1. Click the "Convert Only Object Properties" toggle to turn it On
  2. In the "Property Names to Convert" field, type the exact names of the JSON properties you want to extract
  3. Separate multiple property names with commas (example: name, email, phone)
  4. Use the smart suggestions that appear as you type to ensure correct property names
  5. Click "Save Configuration" to save your settings

Testing Your Configuration​

  1. Use the "Test Configuration" button to verify your setup
  2. Provide sample JSON data in the test panel
  3. Review the extracted properties in the output preview
  4. Adjust your property list if needed and test again

Common Business Scenarios​

Financial Data Processing​

Challenge: Bank transaction data arrives in JSON format but needs individual fields for amount, date, merchant, and category for expense tracking.

Solution: Configure the node to extract transactionAmount, transactionDate, merchantName, expenseCategory and connect to budgeting and reporting workflows.

Result: Automated expense categorization and real-time budget tracking without manual data entry.

Inventory Management​

Challenge: Product information from suppliers comes as JSON but needs separate fields for SKU, quantity, price, and description for inventory updates.

Solution: Set up property extraction for productSKU, availableQuantity, unitPrice, productDescription and connect to inventory management systems.

Result: Real-time inventory updates and automated reorder notifications based on stock levels.

Customer Onboarding​

Challenge: New customer registration data needs to be split into separate fields for account creation, welcome emails, and CRM updates.

Solution: Extract customerName, emailAddress, companyName, subscriptionTier and route to different onboarding processes.

Result: Streamlined customer onboarding with personalized communications and proper account setup.

Best Practices​

Property Name Accuracy​

  • Use exact property names as they appear in your JSON data
  • Property names are case-sensitive (customerName ≠ customername)
  • Test with sample data to verify correct property extraction

Performance Optimization​

  • Only extract properties you actually need in your workflow
  • Use specific property selection for large JSON files to improve processing speed
  • Consider the downstream nodes when deciding which properties to extract

Data Validation​

  • Always test your configuration with real sample data
  • Verify that extracted properties contain the expected information
  • Set up error handling for cases where expected properties might be missing

Workflow Integration​

  • Plan how extracted properties will be used by subsequent nodes
  • Name your properties clearly for easy identification in later workflow steps
  • Document which properties are extracted for team collaboration

The Convert From JSON node is essential for any workflow that processes structured data, enabling you to transform complex information into actionable, individual data points that drive your business automation forward.