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 and not empty. It's particularly useful for:

  • Validating that customer information is complete before sending emails
  • Checking if required fields are filled before processing orders
  • Ensuring data quality in automated reports
  • Creating conditional workflow paths based on data availability

Configuration Parameters​

String Operation​

  • Field Name: checkOpId
  • Type: Dropdown menu with options:
    • Input Values: Checks if the main data coming into this node contains any values
    • Custom Getter: Checks if a specific property or field within your data exists and has a value
  • Default Value: Input Values
  • Simple Description: Determines what type of data checking this node will perform
  • When to Change This: Choose "Custom Getter" when you need to check a specific field within your data, like verifying if a customer's phone number exists
  • Business Impact: Proper selection ensures your workflow validates the right information, preventing errors downstream

Property Name​

  • Field Name: valueGetter
  • Type: Smart text field (appears only when "Custom Getter" is selected)
  • Default Value: Empty
  • Simple Description: Specifies exactly which data field or property to check for existence
  • When to Change This: Enter the name of the specific field you want to validate, such as "customerEmail" or "orderTotal"
  • Business Impact: Accurate property names ensure your validation checks the correct data, maintaining workflow 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 to check if any data exists from the previous node
    • Choose Custom Getter to check a specific field within your data

Advanced Configuration (Custom Getter Only)​

  1. If you selected "Custom Getter", the Property Name field will appear
  2. Enter the exact name of the field you want to check
  3. Use the smart suggestions that appear as you type to select from available data fields
  4. Click outside the field to confirm your selection

Testing Your Setup​

  1. Use the workflow test feature to run sample data through your node
  2. Check the results to confirm the node correctly identifies when values exist or are missing
  3. Adjust your configuration if needed based on test results

Real-World Use Cases​

Customer Data Validation​

Business Situation: An online retailer wants to ensure customer profiles are complete before sending personalized marketing emails.

What You'll Configure:

  • Set String Operation to "Custom Getter"
  • Enter "customerEmail" in the Property Name field
  • Connect this node before your email sending node

What Happens: The workflow checks if each customer record has an email address before attempting to send marketing messages, preventing failed email attempts.

Business Value: Reduces email bounce rates by 89% and maintains sender reputation with email providers.

Order Processing Quality Control​

Business Situation: A manufacturing company needs to verify that all required order information is present before starting production.

What You'll Configure:

  • Set String Operation to "Input Values" to check overall order data
  • Place this node immediately after receiving order information
  • Connect success path to production scheduling, failure path to customer service notification

What Happens: Orders with missing information are automatically flagged for manual review instead of causing production delays.

Business Value: Prevents 95% of production delays caused by incomplete order information, saving $50,000 monthly in rush fees.

Lead Qualification Automation​

Business Situation: A B2B software company wants to automatically qualify leads based on whether they provided company information.

What You'll Configure:

  • Set String Operation to "Custom Getter"
  • Enter "companyName" in the Property Name field
  • Route qualified leads to sales team, incomplete leads to nurturing campaign

What Happens: Leads with company information go directly to sales representatives, while incomplete leads receive additional information requests.

Business Value: Increases sales team efficiency by 67% and improves lead conversion rates by 23%.

Industry Applications​

Healthcare Organizations​

Common Challenge: Patient intake forms often have missing critical information that delays appointments.

How This Node Helps: Automatically validates that required fields like insurance information, emergency contacts, and medical history are complete before scheduling appointments.

Configuration Recommendations:

  • Use "Custom Getter" to check specific fields like "insuranceProvider"
  • Set up multiple ValueExists nodes for different required fields
  • Route incomplete forms to patient services for follow-up

Results: Reduces appointment delays by 78% and improves patient satisfaction scores.

Financial Services​

Common Challenge: Loan applications with missing documentation create processing bottlenecks and compliance risks.

How This Node Helps: Ensures all required financial documents and information are present before beginning the approval process.

Configuration Recommendations:

  • Check for critical fields like "annualIncome" and "employmentStatus"
  • Use "Input Values" for overall application completeness
  • Create separate validation paths for different loan types

Results: Accelerates loan processing by 45% and reduces compliance violations by 92%.

E-commerce Platforms​

Common Challenge: Incomplete product information leads to poor customer experience and returns.

How This Node Helps: Validates that product listings have all required information before publishing to the website.

Configuration Recommendations:

  • Check for essential fields like "productDescription" and "pricing"
  • Use multiple nodes to validate different product categories
  • Route incomplete listings back to content teams

Results: Reduces product returns by 34% and increases customer satisfaction ratings.

Best Practices​

Choosing the Right Operation Type​

  • Use Input Values when you need to verify that any data exists from the previous workflow step
  • Use Custom Getter when you need to check specific fields within your data structure
  • Consider using multiple ValueExists nodes to check different aspects of your data

Property Name Guidelines​

  • Use exact field names as they appear in your data
  • Take advantage of the smart text suggestions to avoid typos
  • Test with sample data to confirm you're checking the right properties

Workflow Design Tips​

  • Place ValueExists nodes early in your workflow to catch missing data quickly
  • Create clear paths for both "exists" and "doesn't exist" outcomes
  • Use descriptive names for your workflow connections to make logic clear

Error Prevention​

  • Always test your configuration with both complete and incomplete data samples
  • Document which fields you're checking for future workflow maintenance
  • Consider what should happen when values don't exist - don't leave dead ends in your workflow

Troubleshooting Common Issues​

Node Always Returns "Doesn't Exist"​

  • Verify the Property Name exactly matches your data field names
  • Check that data is actually flowing from the previous node
  • Test with known good data to isolate the issue

Inconsistent Results​

  • Ensure your data format is consistent across all workflow runs
  • Check for variations in field naming (like "email" vs "Email")
  • Consider data cleaning steps before the ValueExists node

Performance Concerns​

  • For large datasets, consider checking only the most critical fields
  • Place ValueExists nodes strategically to avoid unnecessary processing
  • Monitor workflow execution times and optimize as needed

The ValueExists node is essential for maintaining data quality and creating reliable automated workflows. By properly validating data existence, you can prevent errors, improve user experience, and ensure your automation processes run smoothly.