How to use Router Tool in Bit Flows for Multi-Path Flows

The Router Tool in Bit Flows helps you create workflows with multiple paths, allowing data to be processed differently. In this guide, we explain how to use the Router in a workflow. We’ll use Bit Form as the trigger and show how to send form data to Google Sheets and, at the same time, make an API request to add a subscriber in MailerLite. After reading this, users will understand how to set up and configure the Router Tool and create branches for different actions. The result will be a workflow where form submissions are sent to Google Sheets and new subscribers are automatically added to MailerLite.

Add Router to a Workflow

Open or Create a Workflow

To add a Router to your flow, you can either open an existing workflow 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 “BitForm_to_Sheets&MailerLite.” We will add a Router to this flow to manage multiple paths effectively.

Add Router to Your Flow

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

Link with the Router

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

1. Unlink any existing connection, if any.
2. Connect Bit Form to the Router.

This setup ensures that when an event is triggered in Bit Form, the Router will split the data into multiple paths, enabling different actions to be executed simultaneously based on your workflow.

Add Multiple Paths with Router

To add a path in Bit Flows, simply click on the Router. A new path will be created automatically. If you want to create multiple paths, simply click on the Router multiple times. Each path will represent a different workflow route, and you can direct the flow based on your needs.

In this way, you can easily split the workflow into multiple paths and perform different actions for each.

In this example, I need two paths: one to send data to Google Sheets and another to make an API request to MailerLite to create a subscriber.

Testing the Flow: Verifying Data Submission to Google Sheets and MailerLite

Now, let’s run the trigger, which in this case is the Bit Form Submit Success event, and verify if the submitted data is being sent to Google Sheets and the API Request to create a new subscriber in MailerLite.

I have already configured Google Sheets and API Request (Create Subscriber in MailerLite) as actions. Now, let’s verify if the Router is working correctly. To do this, click on “Test Flow Once” and trigger the event. Afterward, check the logs and verify if the data is correctly updated in Google Sheets and the MailerLite subscriber list.