Skip to main content

↔️ Conditions

A Condition acts as a decision gate in your workflow. It evaluates specified criteria and, if the condition is met (i.e., evaluates to true), the subsequent action(s) will run. If the condition is not met, the subsequent action(s) in that branch will be skipped.

Adding a Condition​

  1. Select the element on your canvas (e.g., a “Submit” button) you want to attach the action to. Click on it to open left and right bar. In the left bar click Add Action → More actions…
  2. In the canvas, click Add Condition beneath an existing action. A Condition node will appear in the workflow.
  3. Configure the Condition:
    • Choose the variable or parameter to evaluate. Examples might include:
      • Device (iOS, Android, Web)
      • A response variable from a previous HTTP request
      • A local storage value
      • An element input value
    • Choose how to compare the selected variable (e.g., Equals, Not Equals, etc.).
    • Specify the value to compare against. For instance, if the variable is Device, you might select iOS, Android, or Web.
  4. Add Additional Conditions (Optional)
    • Click Add condition to create additional comparisons. Each condition row is evaluated separately. If multiple conditions are present, they must all evaluate to true for the subsequent action(s) to run.
  5. Save & Test
    • Click Save. In Preview, trigger the workflow to see if the condition passes. If the condition is met, the next action(s) will execute; if not, those action(s) will be skipped.

Example Use Cases​

  1. Device-Specific Flows
    • Condition: Device Equals iOS
    • Outcome: Only run certain actions (e.g., display iOS-specific UI or open an iOS app link) if the user is on iOS.
  2. Validating Form Data
    • Condition: Form Input Value Not Equals "" (an empty string)
    • Outcome: Proceed with a data submission or next step only if the user has filled out the form.
  3. API Response Handling
    • Condition: Response Code Equals 200
    • Outcome: Display a success message or run a next step only if the API request returned a 200 OK response.

Best Practices​

  • Combine Conditions: Add multiple conditions to refine logic further. For instance, you might check both device type and a user input field to ensure both are valid.
  • Fallback Paths: If you need alternative behavior when a condition fails, you can create a separate workflow branch or action for that scenario.

Need Assistance?​

If you encounter any challenges or require further guidance while building your app, please refer to the Documentation or, contact our support team at [email protected].