Condition Check

The Condition Check component runs a conditional script and starts different events based on its outcome. It checks the script and sends an onTrue event if the result is true, an onFalse event if the result is false, and an onError event if an error occurs. The execute method compiles and runs the script. It determines the correct event to start based on the script's result.

Skill Level

You need intermediate JavaScript knowledge.

How to use:

Overview

The Condition Check component runs JavaScript code and starts different event paths based on the result. This component allows branching logic in agent workflows, enabling you to create decision points based on any condition you need to check. The component checks JavaScript expressions and directs the workflow based on whether the result is true or false, making it an important building block for creating agent behaviors. You write a simple or intermediate JavaScript condition script that returns true or false to control the workflow path.

---

Input

---

Methods

---

Events

---

Typical Chaining of Components

Source Components

Target Components

---

Implementation Example

1. Drag the Condition Check component:
   Place the Condition Check component next to the component where you want to perform the validation[1].

2. Write the script:
   Add the following script to check that all uploaded files end with .pdf (case-insensitive):

   // Retrieve the uploaded files array from the agent's data// Default to an empty array if no files are uploadedlet uploadedFiles = this.agent.data.uploadedFiles || [];

    

   // Check if every file URL ends with '.pdf' (case-insensitive)if (uploadedFiles.every(fileUrl => fileUrl.trim().toLowerCase().endsWith('.pdf'))) {

   returntrue;

   } else {

   returnfalse;

   }

3. Connect Event Handlers:
   Connect the Condition Check component to the rest of the flow with these events:

   • On True: Runs when all uploaded files are PDFs.

   • On False: Runs when at least one file is not a PDF.

   • On Error: Runs if there is an error during validation.
     

     

---

Best Practices

• Keep conditions focused and simple: Write short conditions that check one logical concept. Complex conditions should be broken down into multiple Check Condition components when possible.

• Always handle errors: Connect the onError event to correct components to ensure errors are handled well.

• Use multiple condition components: For complex decision trees, break logic into multiple Check Condition components for easier maintenance.

• Validate input data: Always check for null or undefined values before you use variables to avoid runtime errors.

• Avoid side effects: Condition checks should check the state but not change it. Keep the script focused on determining the condition outcome.

• Test edge cases: Check both true and false paths work as expected, including boundary conditions and unexpected inputs.

• Use consistent formatting: Use the same coding style for better readability and easier maintenance.

---

Common Use Cases