Gmail Integrations in WordPress – Send Gmail Automatically with Bit Flows

Gmail Integrations: With the Gmail action in Bit Flows, you can automatically send emails as part of workflows on your WordPress website. By connecting Gmail integration to enable automated email sending using a form submission trigger. With this workflow automation tool, you can send personalized emails without manual effort.

Bit Flows is a WordPress automation plugin that allows you to connect different tools and automate tasks without any coding. It helps businesses build powerful workflow automation by connecting apps and moving data between them automatically. It supports integrations with more than 346+ popular apps, including Gmail, Mail, Elastic Mail, MailerLite, MailPoet, and many others.

In this guide, you’ll learn how to integrate Bit Form with Gmail through Bit Flows, where Bit Form acts as the trigger, and Gmail serves as the action. 

Once the automation is complete, an automated email will be sent through Gmail whenever someone submits your form.

Step 1: Open Bit Flows and create a new flow

First, open your Bit Flows Dashboard, then either create a new flow or open an existing one. In the Flow Builder, first click the plus (+) icon to add a trigger as you wish. In this setup, Bit Form is the trigger, and Gmail is used as the action.

Step 2: Set Bit Form as the Trigger and Capture the Form Data

From the trigger app list, search for Bit Form and select it. After selecting Bit Form, choose the correct form and trigger event. Then go to the form on your website, fill it out, and submit it.

This step is important because Bit Flows needs real sample data from the form before you can map fields properly inside Gmail. Once the data has been fetched successfully, move to the action step.

Step 3: Add Gmail as the action app

Now click the action area in your flow, search for Gmail, and select it. From the available Gmail events, choose Send an Email.

After selecting Gmail as the action, the next step is to choose an event. In the available events, we selected “Send an Email.”

Here, you can either select an existing connection if you’ve already created one or create a new one by simply clicking the “Add connection” button.

 Step 4: Create a Gmail connection

When you click the Add Connection button, you’ll be prompted to enter a “Connection Name” for your connection. After that, 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.

Step 5: Google Cloud Console Setup

To get the Client ID and Client Secret, open Google Cloud Console and sign in with your Google account. Then either create a new project or select an existing one. If this is your first time doing this, creating a fresh project is usually the easiest option because it keeps everything organized for the Gmail connection.

Step 6: Enable Google APIs & Configure the OAuth

Inside your Google Cloud project, go to APIs & Services. Search for and enable both Gmail API and Google Drive API. 

Next, go to Configure Consent Screen. Click “Get Started” under the OAuth overview and complete the app details, such as app information, audience, and contact information.

• In the App Information section, enter your app name and add your Gmail address.
• In the Audience section, select External.
• In the Contact Information section, provide your email address.
• Accept the Google terms and policies.
• Finally, click Create to complete the setup.

After finishing that part, create the consent screen setup. Then open the Audience section from the left menu and publish the app. This makes the connection usable when Bit Flows tries to authorize the Gmail account.

Step 7: Create the OAuth Client

Now go to the Clients section and click Create Client. Select Web Application as the application type, then give it a name. After that, add the Authorized JavaScript Origins and Authorized Redirect URIs exactly as shown on the Bit Flows connection pop-up.

In the JavaScript Origins field, enter your website’s domain name. In the Authorized Redirect URL field, paste the webhook URL you copied from Bit Flows. Then enable data access and add the required scopes.

Here are the scopes:

• Drive
• drive.file
• drive.metadata
• spreadsheets
• userinfo.profile
• userinfo.email

Save everything once done. If Google shows any warning about restricted scopes, the integration may still work, but if authorization fails later, you may need to complete Google’s app verification process.

Learn more: Google Cloud App Verification

Step 8: Get Client ID and Client Secret

After creating the OAuth client, go to the Credentials section in Google Cloud Console. Open the client details or use the download option, then copy the Client ID and Client Secret. Return to Bit Flows and paste both values into the Gmail connection pop-up.

 Enter your connection name if you have not done that already, then complete the connection. Once it is successful, the new Gmail connection will appear automatically in the Select Connection field.

Once Bit Flows is successfully connected to your Google app, the newly created connection will automatically be selected under “Select Connection.” After that, you will need to add Field Mapping.

Step 9: Map Bit Form Fields to Gmail Fields

Here, you’ll see a “Map Fields” section where you need to map your form fields to the matching fields in Gmail. The From Email, From Name, To, Subject and Body fields are required by Gmail, so make sure to map your form’s From Email, From Name, To, Subject and Body fields to it.

Learn more about Field Mapping

Once you’ve finished these settings, you can either click the “Test Run” button to check if the integration is working correctly or simply close the pop-up to complete the setup.

Congratulations! You have successfully set up Gmail as your action with Bit Flows.

Step 10: Test the Full Flow with a Form Submission

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 Bit Form Submit.

Step 11: Integration Log

After testing the flow, open the Logs section by clicking the logs icon in the top right corner of the flow screen. Here, you can verify whether the trigger and action were successful.

If everything is set up correctly, you should see a SUCCESS status in the log.