Looply Academy
  • Getting Started
    • What is Looply?
    • Deployment Models
  • System Requirements
  • SAP Integration: ABAP Add-on & Access
  • Security & Identity - What IT Teams Need to Know
  • Authenticating Teams User Actions to Enterprise Systems
  • Signing Up & Onboarding Your Team
  • Looply Implementation Plan
  • Looply Integration Demos
  • Integrations
    • Microsoft Integration
    • SAP Integration
      • Installing the ABAP Looply Add-On
        • Gateway Service Setup - Single System
        • Gateway Service Setup - Hub scenario
      • Triggering or Resuming a Looply Workflow from SAP
      • Triggering SAP code from Looply
      • SAP Workflow Integration
      • Varo/Stelo Integration
      • SSL & IP address
      • SSO Authentication
  • App Management
    • Building Apps
    • Deploying apps to Teams App catalog
      • Looply Dashboard
      • Manual Installation
    • Installing Looply Apps
    • Uninstall/Update Looply Apps
    • Teams Admin center
  • Adaptive Cards
    • Building Adaptive Cards
      • Container Elements
      • Content Elements
      • Input Elements
      • Actions
    • Data Binding
    • Conditional Rendering
    • AI Assistant
    • Inline Functions
  • Workflows
    • Building Workflows
    • Triggering Workflows
    • Environment Variables & Profiles
    • Versioning Workflows
    • Using HTTP Requests
    • Using Functions
    • Using Conditionals
    • Using Branch Conditionals
    • Using Advanced Conditionals
    • Using Integrations
      • Adaptive Card Actions
      • SAP Requests
    • Using Redirects
    • Using Override Payload
    • Terminating Workflows
  • Data Vault
    • Variable Datastores
  • Monitoring & Logs
    • Monitoring Workflows
    • Error Notifications
  • API REFERENCE
    • Developer API Overview
    • Workflow API
    • Adaptive Card API
  • Team Management
    • Managing Organisations
    • Team Roles and Permissions
  • Resources
    • JavaScript Libraries
  • Tutorials
    • Creating MS Teams Apps
    • Designing Workflows
    • Building Adaptive Cards
    • Adaptive Cards with AI
    • Examining Workflow Executions
  • Support
    • Changelog
    • Contacting Support
Powered by GitBook
On this page
  • Define Conditional Logic
  • Adding Rules
  • Handling Outcomes
  1. Workflows

Using Conditionals

Using conditional logic in Looply workflows

PreviousUsing FunctionsNextUsing Branch Conditionals

Last updated 1 year ago

Dictate the flow of your processes with precision using Looply's conditional steps.

Conditionals operate in an if-else fashion, allowing users to define a series of conditions to evaluate and then seamlessly branch workflows into two distinct paths based on true or false outcomes.

Whether crafting your own static conditions or evaluating data returned from a prior workflow step, these conditional steps offer unparalleled control and flexibility in shaping the logic of your workflows.

Define Conditional Logic

You can get started adding your conditional logic by clicking on a + button in your workflow and selecting the Conditional step from the Workflow's toolbox.

This will add the conditional step to your workflow and branch out into 2 separate flows for Yes and No outcomes. Each new branch will contain a placeholder until you are ready to determine your next steps.

Adding Rules

You can use the Rules section of the Conditional editor to define the specific conditions to evaluate as true for your condition to pass.

Each rule contains a variable name, a condition, and a value.

Conditions we support are:

  • Boolean Equals

  • Is Boolean

  • Is Null

  • Is Numeric

  • Is Present

  • Is String

  • Is Timestamp

  • Not

  • Numeric Equals

  • Numeric Greater Than

  • Numeric Greater Than Equals

  • Numeric Less Than

  • Numeric Less Than Equals

  • String Equals

  • String Greater Than

  • String Greater Than Equals

  • String Less Than

  • String Less Than Equals

  • String Matches

  • Timestamp Equals

  • Timestamp Greater Than

  • Timestamp Greater Than Equals

  • Timestamp Less Than

  • Timestamp Less Than Equals

Create your rule by manually entering or selecting the variable that should be evaluated, followed by the conditional operator, and finally manually entering or selecting the expected value.

You can add more than one rule by clicking the + Add rule button and repeating this process.

Additionally, you can access the dropdown menu in the Variable and Value fields to select data from previous steps in your workflow for use in your rule.

Note: Remember when adding rules, all of your rules must be true for your conditional logic to pass and follow down the Yes branch of your workflow.

Handling Outcomes

Once you have added all of your conditional logic, the final step is to handle what your workflow should do next depending on the outcome of your condition.

Conditional steps are designed to branch out into two flows for Yes (true) and No (false) outcomes of your logic. Each branch is initialized with a placeholder step.

You can determine the next steps for your workflow by clicking on the placeholder step, and then selecting the new step you want to insert in its place for each outcome.

Note: Deleting conditional steps within your workflow will result in both outcome branches and all subsequent steps also being deleted.