Get Started with Bit Flows: A Beginner’s Guide

This document provides a step-by-step guide to creating an automated workflow in Bit Flows. It shows how to set up a trigger using WordPress with the event “On Post Status Update” and connect it to actions in Google Sheets. Users will learn how to capture response data, map fields, and set up the required settings for the integration. After setting up this workflow, whenever a WordPress post’s status changes (like from draft to publish), the post details will automatically be added as a new row in Google Sheets. This saves time and reduces manual effort.

Create a New Workflow

To create a new workflow, first click on Flows in your Bit Flows. Then, click on the Create Workflow button. You will then be prompted to enter a name for your workflow. After entering the name, click on Create. This will create a new workflow and redirect you to the Visual Workflow Editor, where you can customize your workflow.

Select your trigger application

The Trigger Step is the starting point of your workflow, where it provides the necessary data or executes tasks at a scheduled time. To choose an application, click on Select an App, then click on the desired app. For this example, we will choose WordPress as our trigger.

Select the application event that will trigger the workflow

Once you select your trigger application (WordPress) for the workflow, you’ll see a list of available events for the next step. Choose the trigger event to proceed. For this example, we will select On Post Status Update as the WordPress trigger event.

Additional Configuration Options

If you choose the On Post Status Update event in the WordPress trigger, like we did, you will also need to configure additional settings. You will be asked to select the Post Type and a specific Post. For this demonstration, we will select Post as the Post Type and choose the Lorem Ipsum demo post for the Post. This means the trigger will run whenever the status of this post is changed.

Capture Response

Now, you need to capture the response, which will be used to map with different data points in the subsequent action steps of the workflow. Click on the Capture Response button and complete the trigger event. For this example, we clicked on Capture Response and changed the demo post Lorem Ipsum status from Draft to Publish. (WordPress is used here for demonstration purposes. You will need to send data from your selected app to the trigger based on its configuration.) For further guidance, please refer to the video below.

Once done, click on the Close button. Congratulations! You have successfully set up your trigger.

Capturing the response is necessary because it allows you to understand and map the data coming from the trigger. When a trigger event occurs, the data associated with that event like user details, form inputs, or post information is sent to the workflow. Capturing this response:

• Identifies the Data: It helps you see what specific data is being sent by the trigger.
• Prepares for Mapping: Enables you to map this data to corresponding fields in the action step (e.g., adding a row in Google Sheets or sending an email).
• Ensures Accuracy: Verifies that the trigger is correctly configured and sending the expected data.

After capturing the response:

1. Review the Data: Look at the captured data fields to understand what information is available.
2. Map the Data: Use the captured data fields to map them to corresponding fields in your action steps. For example:
   • Map “Name” from the trigger response to a “Name” column in Google Sheets.
3. Test the Workflow: Run a test to ensure that the data flows correctly from the trigger to the action steps.
4. Finalize the Workflow: Save and activate the workflow so it will function as intended whenever the trigger event occurs.

Adding Action Steps

Once your trigger is set up, you can proceed to add Action Steps to your workflow. Action Steps define what happens after the trigger is executed. You can choose from a variety of applications and actions to perform tasks such as sending data, updating records, or notifying users.

To add action steps to your workflow:

1. Click the “+” Button
   Locate and click on the + button next to the trigger step in the workflow builder. This will add a new step to your workflow and open the Action App Selection popup.
2. Search for the Required App
   In the popup, search for the app you want to use for this step. Once you find it, click on the app name to select it.
3. Configure the App Settings
   After selecting the app, a settings popup will appear. Here, you need to choose an action event. Then, configure the required options and settings for the app to function correctly within the workflow step.

Repeat these steps for any additional actions you want to include in the workflow.

Send Data To Google Sheets

Add Steps

To add an action, click on the plus (+) icon located next to your trigger. This will add a new step to your workflow.

Select an App

After adding your Action Step, you need to select an app to send your data. To select an app, click on the plus (+) icon in the Action Step. This will open a popup displaying a list of all available apps.

From the app list, you can choose your preferred action. You can also search for the app where you want to send your data. For this example, we will choose Google Sheets as the action.

Select App Action Event

If you select Google Sheets for the action, as we did, you will see the available events that can be performed. For example, when you click on Google Sheets, the available event is “Add Row.” This means that whenever the trigger event runs, a row of your data will be added to Google Sheets.

Add Connection

After choosing the “Add Row” event, you will be prompted to select a connection. Click on the “Add” button to create a new connection. You will be required to enter your Client ID and Client Secret from your Google Console app. Additionally, you can set a connection name to easily identify it for future use. Remember, for the same Google account, you won’t need to connect again. Next time, simply select the connection from the drop-down list.

Get Client ID and Client Secret

To get your Client ID and Client Secret, you need to go to your Google Cloud Console and create an app.

1. Go to Google Cloud Console
   • Open the Google Cloud Console and sign in with your Google account.

2. Create a Project or Select an Existing Project
   • If you don’t already have a project, click on Create Project and follow the prompts to set it up.
   • If you have an existing project, select it from the project list.

3. Enable APIs:
   • Now, go to “APIs & Services.”
   • Search and enable both the Google Drive API and the Google Sheets API.

4. Configure Consent Screen:

• Go to “Configure Consent Screen.”
  • Click on “Get Started” under OAuth Overview.
  • Fill in App Information, Audience, Contact Information, and click Finish.
  • Click Create.
• Publish the App.
  • On the left menu, click Audience and Publish the app.
• Create a Client.
  • On the left menu, go to Clients and click “CREATE CLIENT.”
  • Select Web Application as the application type.
  • Enter a Name.
  • Add your Authorized JavaScript Origins and Authorized Redirect URIs (found on the integration page).
• Enable Data Access.
  • In the scope section, click on “Add or Remove Scopes.” Add these scopes. Then, click on “Update.”
    • https://www.googleapis.com/auth/drive
    • https://www.googleapis.com/auth/drive.file
    • https://www.googleapis.com/auth/drive.metadata
    • https://www.googleapis.com/auth/spreadsheets
    • https://www.googleapis.com/auth/userinfo.profile
    • https://www.googleapis.com/auth/userinfo.email
  • Scroll down and click Save.

5. Generate Client ID and Client Secret:
   • Go to the “Credentials” section.
   • Click on the download icon under the Action column.
   • A popup will appear displaying your Client ID and Client Secret.
   • Copy these credentials.
   • Paste them into the appropriate fields on the integration page.

Once you have successfully entered your Google Sheets Client ID and Client Secret, click “Connect” to proceed. Then follow these steps:

• Select your Google account.
• Click on “Advanced.”
• Click on “Go to“
• Click on “Continue.”
• Grant the necessary permissions (for this example, all permissions are selected).
• Your connection to Google Sheets is now successfully established.

Congratulations! You have successfully connected your Google Console App with Bit Flows.

Once Bit Flows is successfully connected to your Google app, the newly created connection will automatically be selected under “Select Connection.”

After connecting with Google Sheets, you will need to select your spreadsheet. If you have multiple spreadsheets, choose the one you want to use for this action.

After selecting your spreadsheet, you will need to choose a specific sheet within it. Since a spreadsheet can contain multiple sheets, pick the one you want to use for this action. Here, we have two sheets available, and we will select the “arouf.towpSite” sheet.

After choosing your sheet, you need to map the trigger fields with the action fields, which in this case is Google Sheets. To map your fields, click on the Add Row button. You will then see two fields: Column and Value.

• For Column, select the column from your chosen spreadsheet.
• For Value, map it to the corresponding trigger response field, which in this case is WordPress On Post Status Update event. Additionally, you can use options like Flow, Math, String, or System for custom values or calculations.

For more guidance, follow the demo video below.

Congratulations! You have successfully set up Google Sheets as your action.

After setting up the trigger and actions, you can test your flow to verify if the integration is working correctly. To do this, simply click on Test Flow Once. Then, complete the trigger event, which in this case is WordPress On Post Status Update. For demonstration, let’s change the status of a post and observe the results.

Integration Log

You can check your integration logs to monitor the flow’s activity. To view the logs, click on the Logs button located at the top-right corner. All the logs related to this flow will be displayed there.