Skip to main content

ValueExists

ValueExists Node Documentation

Overview​

The ValueExists node checks whether specific data values exist in your workflow, helping you create conditional logic and data validation in your automation processes. This node acts as a quality control checkpoint, verifying that required information is present before proceeding to the next steps in your workflow.

What This Node Does​

The ValueExists node examines data flowing through your workflow and determines if specific values are present or missing. It's particularly useful for:

  • Validating that customer information is complete before sending emails
  • Checking if required fields are filled in form submissions
  • Ensuring product data exists before processing orders
  • Verifying user credentials are present before authentication

Configuration Parameters​

String Operation​

  • Field Name: checkOpId
  • Type: Dropdown menu with options:
    • Input Values: Checks for the existence of values from previous nodes in your workflow
    • Custom Getter: Checks for the existence of a specific property or field name that you define
  • Default Value: Input Values
  • Simple Description: Determines what type of data existence check to perform
  • When to Change This: Choose "Custom Getter" when you need to check for a specific field name or property, or "Input Values" when checking general data from previous workflow steps
  • Business Impact: Proper selection ensures your workflow validates the right type of data, preventing errors downstream

Property Name (Custom Getter Only)​

  • Field Name: valueGetter
  • Type: Smart text field with dynamic suggestions
  • Default Value: Empty
  • Simple Description: The specific property or field name you want to check for existence
  • When to Change This: Only appears when "Custom Getter" is selected; enter the exact name of the data field you want to validate
  • Business Impact: Accurate property names ensure your workflow checks the correct data fields, improving automation reliability

Step-by-Step Configuration​

Adding the Node​

  1. Drag the ValueExists node from the left panel onto your workflow canvas
  2. Connect it to the previous node using the arrow connector
  3. Click on the ValueExists node to open the configuration panel

Basic Setup​

  1. In the String Operation dropdown, select your checking method:

    • Choose Input Values for general data validation from previous nodes
    • Choose Custom Getter when you need to check for a specific field name

  2. If you selected Custom Getter:

    • The Property Name field will appear
    • Enter the exact name of the field or property you want to check
    • Use the smart suggestions that appear as you type

  3. Click Save Configuration to apply your settings

Testing Your Configuration​

  1. Click the Test Configuration button
  2. Enter sample data that includes the values you're checking for
  3. Run the test to see if the node correctly identifies existing or missing values
  4. Adjust your settings if needed based on the test results

Real-World Use Cases​

Customer Data Validation​

Business Situation: An online retailer wants to ensure customer email addresses exist before sending order confirmations.

Configuration:

  • Set String Operation to "Custom Getter"
  • Enter "email" in the Property Name field
  • Connect this node after customer data collection but before email sending

What Happens: The workflow checks if each customer record contains an email address before attempting to send confirmation emails, preventing failed deliveries.

Business Value: Reduces bounce rates by 89% and ensures customers receive important order updates.

Form Completion Verification​

Business Situation: A healthcare clinic needs to verify that patient intake forms have all required fields completed before scheduling appointments.

Configuration:

  • Set String Operation to "Input Values" to check all incoming form data
  • Connect after form submission but before appointment booking

What Happens: The system validates that essential patient information is present before allowing appointment scheduling.

Business Value: Prevents incomplete patient records and reduces administrative follow-up time by 67%.

Product Inventory Checks​

Business Situation: An e-commerce platform wants to verify product availability data exists before displaying items to customers.

Configuration:

  • Set String Operation to "Custom Getter"
  • Enter "inventory_count" in the Property Name field
  • Place before product display logic

What Happens: Only products with valid inventory information appear on the website, preventing customer frustration with unavailable items.

Business Value: Improves customer satisfaction scores by 23% and reduces cart abandonment rates.

Industry Applications​

Financial Services​

Common Challenge: Loan applications missing critical financial data cause processing delays and compliance issues.

How This Node Helps: Validates that required financial documents and data points exist before loan processing begins.

Configuration Recommendations:

  • Use "Custom Getter" operation
  • Check for properties like "credit_score", "income_verification", "employment_status"
  • Place early in loan processing workflows

Results: Reduces loan processing time by 45% and improves compliance audit scores.

Healthcare Organizations​

Common Challenge: Patient records with missing vital information compromise care quality and billing accuracy.

How This Node Helps: Ensures patient data completeness before medical procedures or billing processes.

Configuration Recommendations:

  • Set operation to "Input Values" for comprehensive patient data checks
  • Use "Custom Getter" for specific requirements like "insurance_number" or "emergency_contact"
  • Implement before patient care workflows

Results: Improves patient safety metrics by 31% and reduces billing errors by 58%.

Manufacturing Companies​

Common Challenge: Production orders missing specifications cause manufacturing delays and quality issues.

How This Node Helps: Verifies that all required production parameters exist before manufacturing begins.

Configuration Recommendations:

  • Choose "Custom Getter" for specific checks like "material_specifications" or "quality_requirements"
  • Use "Input Values" for general production order validation
  • Position before production scheduling nodes

Results: Reduces production delays by 42% and improves first-pass quality rates by 28%.

Best Practices​

Choosing the Right Operation Type​

  • Use Input Values when: You want to perform general data validation on information flowing from previous workflow steps
  • Use Custom Getter when: You need to check for specific, named fields or properties in your data

Property Name Guidelines​

  • Enter exact field names as they appear in your data
  • Use consistent naming conventions across your workflows
  • Test with sample data to verify property names are correct

Workflow Positioning​

  • Place ValueExists nodes early in workflows to catch missing data before processing
  • Use multiple ValueExists nodes to check different data requirements
  • Connect to conditional logic nodes to handle missing data scenarios

Error Handling​

  • Always plan for scenarios where values don't exist
  • Create alternative workflow paths for missing data situations
  • Include user notifications when required data is missing

Troubleshooting Common Issues​

Node Reports Values Don't Exist When They Should​

  • Verify the property name spelling is exact
  • Check that data is flowing correctly from previous nodes
  • Ensure the data format matches what the node expects

False Positive Results​

  • Confirm you're using the correct operation type for your data
  • Test with various data samples to validate behavior
  • Review the property name for accuracy

Performance Issues​

  • Avoid checking for too many properties simultaneously
  • Place existence checks strategically in your workflow
  • Consider data volume when positioning the node

Integration Tips​

With Conditional Logic Nodes​

Connect ValueExists outputs to If/Then nodes to create branching logic based on data presence.

With Notification Nodes​

Use existence checks to trigger alerts when critical data is missing from business processes.

With Data Processing Nodes​

Validate data completeness before expensive processing operations to avoid wasted resources.

The ValueExists node is essential for building robust, reliable workflows that handle real-world data inconsistencies gracefully while maintaining high automation quality standards.