Use Conditional Logic in Bit Flows for complex Automation

This document explains how to use Conditional Logic in Bit Flows to create advanced and dynamic workflows. It guides users on setting up conditions within a workflow to perform different actions based on specific criteria. After reading this document, users will understand how to configure workflows with conditional steps that adapt to different scenarios, making automation smarter and more efficient. By implementing conditional logic, the workflow will execute actions based on the data or trigger event, such as sending emails only to specific users, updating records in a database based on conditions, or performing different tasks for different user roles. This results in a highly customised and automated process.

What is Conditional Logic in Bit Flows?

Conditional Logic in Bit Flows enables you to design workflows that act based on specific conditions. You can define multiple conditions, and if a condition is met, the data is routed to a particular action. If none of the conditions are satisfied, you can specify an alternative action or choose to take no action, similar to an “else” condition in programming.

Add Conditional Logic to a Workflow

Open or Create a Workflow

To add a condition to your flow, you can either open an existing flow or create a new one by setting up your trigger and actions. Refer to this documentation to learn how to create a workflow.

Here, we already have a flow named “BitFormToGoogleSheet.” We will now add a condition to this flow.

Add Conditional to Your Flow

To add conditional logic to your flow, first go to the “Tools” section located next to “Apps.” In the Tools menu, you will find various options. From there, drag the “Conditional” tool and drop it into your flow.

Congratulations! You have successfully added a condition to your flow.

Link with the Condition

Now, to connect the condition with the trigger (which in this case is Bit Form), follow these steps:

1. Unlink the existing connection between Bit Form and Google Sheets.
2. Then, link Bit Form with the condition.

This means, when a form is successfully submitted in Bit Form, the condition will check if the set condition is met.

Configure the Condition

After linking with the condition, you can assign a name to the condition for easier identification.

After assigning a name, click on the plus (+) icon to add condition. This will create a new condition.

If you hover over the newly created condition, you’ll see an edit icon and a delete icon. Click on the edit icon to configure the logic for the condition. This will open a popup where you can set up the logic.

You can also assign a name to the logic. Click on the edit icon next to “Untitled Condition1” in the popup. There, you can input a name for your logic.

Now, set up your logic. Click on the left field where your trigger data is displayed. Select the data you want to evaluate and define the condition. For example, if you want to check whether the Name field value exists when a user submits your Bit Form, select the Name field from the Bit Form in the left field while configuring the logic. Then, in the middle field, choose “Exists” as the condition.

Congratulations! You have successfully configured a logic condition in your workflow.

You can also add multiple logics to a condition. These logics can be either AND or OR logic.

• AND Logic: All the conditions must be true for the action to proceed.
• OR Logic: Only one of the conditions needs to be true for the action to proceed.

To add a new logic, click on the plus (+) icon. This will add a new logic condition, and you can set it up just like before. You’ll also need to select whether the logic is AND-based or OR-based.

For example, when you click on the plus (+) icon, a new logic will be added. After that, you can choose AND-based logic. Then, select the Bit Form Email Field and set the condition to check if the Email field value exists. This means the workflow will check if the email field has a value before proceeding.

So, two logics have been set. When the trigger runs (i.e., when the Bit Form is submitted), this condition will check if both the Name field and Email field values exist. If both fields have values, the data will be sent to the specified action. If either of the fields is empty, the data will not be sent.

After setting up the logic, let’s test it. For this demonstration, I’ve set up a condition with two logics. The condition checks whether both the Name and Email fields from the Bit Form submission have values. If both fields have values, the submitted data will be sent to the specified action (in this case, Google Sheets).

I have linked this condition with Google Sheets, and I want to send the data to a specific sheet called “New Contacts.”

Now, let’s add another condition. In this condition, we’ll set up a rule where if either the Name field value or the Email field value exists, the data will be sent to another sheet.

1. First, click on the plus icon. This will add another condition.
2. Edit the condition, and you can give it a name for better identification.
3. Now, set the logic: If the Name field value exists, click on the plus icon again to add another logic.
4. Choose OR-based logic, and then set the second logic: If the Email field value exists.

After setting the logic, configure the action to send the data to the specified Google Sheets. Now, the data will be sent to a different sheet if either the Name or Email field has a value.

Now, let’s set up an action for when none of the conditions are met. Yes, you do have the option to perform an action if none of the conditions are satisfied.

For this example, we want to send our data to a “Spam” sheet if neither of the two conditions we set earlier is met.

1. To do this, simply add a Google Sheets action to your flow.
2. Link this action with the “Spam” sheet, and ensure it’s connected to No Condition Matched.

Now, try submitting a form and check the result. If neither the Name nor the Email field has a value, the data will be sent to the “Spam” sheet.