Skip to main content

InputData

InputData Node Documentation

Overview​

The InputData node is the starting point for your TheoBuilder workflows. It receives and processes data that enters your automation, whether from external systems, user inputs, or file uploads. Think of it as the "front door" where information first arrives in your workflow.

This node is essential for workflows that need to handle incoming data, process files, or accept user inputs before passing them to other automation steps.

When to Use This Node​

  • Data Entry Points: When your workflow needs to receive data from external sources
  • File Processing: When users upload files that need to be converted or processed
  • API Integrations: When external systems send data to your workflow
  • User Input Forms: When collecting information from users before processing
  • Data Validation: When you need to structure incoming data before further processing

Configuration Parameters​

Input Format Settings​

Input is JSON

  • Field Name: inputIsJson
  • Type: Toggle switch (On/Off)
  • Default Value: On (enabled)
  • Simple Description: Tells the node whether incoming data is in JSON format or plain text
  • When to Change This:
    • Turn On when receiving structured data from APIs, databases, or web forms
    • Turn Off when receiving simple text, numbers, or unstructured data
  • Business Impact: Proper format selection ensures your data is processed correctly and prevents errors in downstream nodes

File Processing Options​

Contains File

  • Field Name: containsFile
  • Type: Toggle switch (On/Off)
  • Default Value: Off (disabled)
  • Simple Description: Enables file processing capabilities when your input data includes uploaded files
  • When to Change This: Enable when your workflow receives file uploads (documents, images, spreadsheets, etc.)
  • Business Impact: Allows your workflow to automatically process uploaded files without manual intervention

Base 64 Value Expression

  • Field Name: base64ValueGetter
  • Type: Smart text field with dynamic data support
  • Default Value: "base64file"
  • Simple Description: Specifies where to find the file data within your input
  • When to Change This: Modify when your file data is stored under a different property name in the incoming data
  • Business Impact: Ensures files are correctly extracted and processed from complex data structures

Result Property Name

  • Field Name: outColumnName
  • Type: Text field
  • Default Value: "file_result"
  • Simple Description: The name given to processed file data when passed to the next node
  • When to Change This: Use descriptive names like "customer_document" or "invoice_file" for clarity
  • Business Impact: Clear naming helps track data flow and makes workflow maintenance easier

File Storage Options​

Save File

  • Field Name: saveFile
  • Type: Toggle switch (On/Off)
  • Default Value: Off (disabled)
  • Simple Description: Saves processed files to your system's storage for future access
  • When to Change This: Enable when you need to keep copies of uploaded files for compliance, backup, or later processing
  • Business Impact: Provides audit trails and backup copies of important documents

Folder Path

  • Field Name: folderPath
  • Type: Smart text field with location support
  • Default Value: Empty
  • Simple Description: Specifies where to save files in your system
  • When to Change This: Set specific folders for different document types (e.g., "/invoices/2024" or "/customer-uploads")
  • Business Impact: Organized file storage improves document management and retrieval

Step-by-Step Configuration​

Setting Up Basic Data Input​

  1. Add the Node:

    • Drag the InputData node from the left panel onto your workflow canvas
    • Position it as the first node in your workflow

  2. Configure Input Format:

    • Click on the InputData node to open the settings panel
    • Leave "Input is JSON" toggle On if receiving structured data from forms, APIs, or databases
    • Turn "Input is JSON" toggle Off if receiving simple text or numbers

  3. Test Your Setup:

    • Use the workflow test feature to send sample data
    • Verify the node correctly receives and processes your input format

Setting Up File Processing​

  1. Enable File Handling:

    • Ensure "Input is JSON" is turned On
    • Turn On the "Contains File" toggle
    • The file processing options will appear

  2. Configure File Extraction:

    • In "Base 64 Value Expression," enter the property name where file data is located
    • Common values: "file", "attachment", "document", or "upload"
    • Use the smart text features to reference dynamic data if needed

  3. Set Result Naming:

    • In "Result Property Name," enter a descriptive name for the processed file
    • Examples: "processed_invoice", "customer_photo", "signed_contract"

  4. Configure File Storage (Optional):

    • Turn On "Save File" if you need to keep copies
    • In "Folder Path," specify where to store files
    • Use forward slashes for folder structure: "/documents/contracts/2024"

Real-World Use Cases​

Customer Support Ticket System​

Business Situation: A help desk receives support tickets with attached screenshots and documents that need automated processing.

Configuration Setup:

  • Keep "Input is JSON" On (tickets come from web forms)
  • Enable "Contains File" for attachment processing
  • Set "Base 64 Value Expression" to "attachment"
  • Set "Result Property Name" to "support_document"
  • Enable "Save File" for record keeping
  • Set "Folder Path" to "/support-tickets/{{ticketDate}}"

Business Outcome: Support tickets are automatically processed, attachments are saved in organized folders, and the workflow can immediately begin analyzing document content.

Invoice Processing Automation​

Business Situation: An accounting department receives invoices via email that need to be processed and stored in the company's document management system.

Configuration Setup:

  • "Input is JSON" On (email system sends structured data)
  • "Contains File" On (invoices are PDF attachments)
  • "Base 64 Value Expression" set to "invoice_pdf"
  • "Result Property Name" set to "invoice_document"
  • "Save File" On for compliance
  • "Folder Path" set to "/invoices/{{currentYear}}/{{vendorName}}"

Business Outcome: Invoices are automatically extracted, saved in vendor-specific folders, and ready for data extraction and approval workflows.

Employee Onboarding Forms​

Business Situation: HR department collects new employee information through online forms, including profile photos and signed documents.

Configuration Setup:

  • "Input is JSON" On (web form data)
  • "Contains File" On (profile photos and documents)
  • "Base 64 Value Expression" set to "employee_documents"
  • "Result Property Name" set to "onboarding_files"
  • "Save File" On for HR records
  • "Folder Path" set to "/hr/employees/{{employeeId}}/onboarding"

Business Outcome: New employee data and documents are automatically organized, stored securely, and ready for further processing steps like badge creation and system account setup.

Industry Applications​

Healthcare Organizations​

Common Challenge: Patient intake forms with insurance cards and medical history documents need secure processing and storage.

How This Node Helps: Automatically receives patient data and documents from intake systems, processes files securely, and organizes them for clinical workflows.

Configuration Recommendations:

  • Enable "Contains File" for insurance cards and medical documents
  • Use "Save File" with HIPAA-compliant folder structures
  • Set descriptive result names like "insurance_card" and "medical_history"

Results: Reduces intake processing time by 60% and ensures all patient documents are properly organized and accessible.

Financial Services​

Common Challenge: Loan applications include multiple document types (pay stubs, bank statements, tax returns) that require immediate processing.

How This Node Helps: Processes loan application data and automatically extracts and organizes supporting documents for underwriting review.

Configuration Recommendations:

  • Structure folder paths by application ID and document type
  • Use clear result property names for different document categories
  • Enable file saving for regulatory compliance

Results: Accelerates loan processing by 45% and maintains complete audit trails for regulatory requirements.

E-commerce Platforms​

Common Challenge: Product listings with multiple images and specification documents need automated processing and organization.

How This Node Helps: Receives product data from various sources and automatically processes images and documents for catalog management.

Configuration Recommendations:

  • Set up folder structures by product category and SKU
  • Use descriptive naming for different image types (main, thumbnail, detail)
  • Enable file saving for inventory management integration

Results: Reduces product listing time by 70% and ensures consistent image and document organization across the catalog.

Best Practices​

Data Organization​

  • Use descriptive names for result properties that clearly indicate content type
  • Structure folder paths logically with dates, categories, or identifiers
  • Test with sample data to ensure proper file extraction and naming

Performance Optimization​

  • Only enable file processing when actually needed to improve workflow speed
  • Use specific folder paths rather than saving everything to root directories
  • Consider file size limits when processing large documents or images

Security Considerations​

  • Ensure folder paths comply with your organization's data governance policies
  • Use appropriate access controls for saved files
  • Consider data retention policies when enabling file saving

Troubleshooting Common Issues​

  • Files not processing: Verify the "Base 64 Value Expression" matches your data structure
  • Storage errors: Check folder path permissions and naming conventions
  • Data format issues: Confirm the "Input is JSON" setting matches your actual data format

The InputData node is your workflow's foundation - proper configuration ensures smooth data flow and reliable automation throughout your entire process.