If you're a BotSailor reseller or admin looking to connect Google services like Google Sheets, Cloud Translation, or Maps, this tutorial will walk you through setting up your Google API integration properly.
🔍 What is Google API Integration in BotSailor?
Google API integration in BotSailor allows you to:
Store chatbot form responses in Google Sheets
Use Google Maps for dynamic location features
Enable Cloud Translation for multilingual bot responses
Offer Google login for your end-users
This guide walks you through the process of creating a Google Cloud App, enabling required APIs, setting up credentials, and submitting your app for verification.
This is essential for Google Sheet in integration for your customers to BotSailor. All your customers will use your admin google app to connect their google sheet and integrate with BotSailor.
Go to BotSailor Settings
Login to your BotSailor reseller dashboard and navigate to:
Control Panel→ Settings & Integration → Google
You will see fields for:
Google API Key
Client ID
Client Secret
OAuth Redirect URIs
Toggle for enabling social login
Go to "APIs & Services → Library"
Search for Google Drive API:
Click on Google Drive API and then click Enable.
Search for Google Sheets API:
Click on Google Sheets API and then click Enable.
Search for Maps JavaScript API:
Click on Maps JavaScript API and then click Enable.
Search for Cloud Translation API:
Click on Cloud Translation API and then click Enable.
The OAuth consent screen is a crucial component of Google's identity and access management system. It acts as an intermediary between a user and an application requesting access to their data. When a user tries to use an application that integrates with Google services, this screen will pop up, displaying key information about the application and the specific permissions it's requesting.
To set up your OAuth concent screen:
Go to "APIs & Services → Credentials"
A prompt will appear to set up the OAuth consent screen. Click on Configure consent screen.
1. Click Configure concent screen.
2. Provide the following details:
- App Information & Support Email: Choose an appropriate name for your app and give your support email for the app.
- Audience: There are two main user types for an OAuth consent screen:
Internal: This is for applications that are only used by people within your Google Workspace organization.
External: This is for applications that will be available to any user with a Google account.
Choose User Type as External to make your app available for users outside your organization.
- Contact Information: Enter your Email addresses to let users communicate with you, as you are developing the app.
- Confirmation: Agree to Google API services user data policy and click continue.
- Finish: Click Create to finish Concent Screen.
The publishing status of your consent screen can be either Testing or In production. While in testing, the app can only be used by a limited number of test users that you define. To make your app available to the public, you need to publish it to production, which may require a verification process by Google, especially if you are requesting access to sensitive user data, which will be discussed in the verification part.
Return to the Credentials page and click Create Credentials > OAuth Client ID.
Add the following Authorized Redirect URIs (as shown in your BotSailor panel):
âś… Copy your:
Client ID
Client Secret
This guide will walk you through adding two types of restrictions to your API key:
Application restrictions: To ensure your key can only be used on specific websites or from specific IP addresses.
API restrictions: To limit the key to calling only the specific APIs you've authorized.
First, you need to find the API key you want to secure within your Google Cloud project.
Go to the Google Cloud Console.
From the main navigation menu on the left, select "APIs & Services" and then click on "Credentials".
On the "Credentials" page, you will see a list of your API Keys. Find the key you want to restrict (e.g., "API key 1").
Click the three-dot menu icon under the "Actions" column for that key, and select "Edit API key".
This step will lock your API key so it only works on websites you specify.
On the "Edit API key" page, scroll down to the "Application restrictions" section.
Select the "Websites" radio button. This will reveal the "Website restrictions" section below it.
Click the "Add" button.
A field will appear. Enter the specific URL of the website where you will use the key. You can use wildcards (*) to include all subdomains. For example:
To allow a specific domain and all its subdomains, use *.yourdomain.com/*
To allow only a specific page, you could use yourdomain.com/page
In your example, *.bloodtek.studio/* is used to allow all pages on all subdomains of bloodtek.studio.
This is the most important step for limiting which services the key can access.
Scroll further down to the "API restrictions" section.
Select the "Restrict key" radio button.
A dropdown menu will appear. Click on it and select the specific APIs that this key is allowed to call. You can select multiple APIs.
In your example, the key is being restricted to only call:
Google Drive API
Google Sheets API
Maps JavaScript API
Cloud Translation API
Once you have configured both the application and API restrictions, click the "Save" button at the bottom of the page.
Note: Google mentions that it may take up to 5 minutes for the new settings to take effect.
By following these steps, you have successfully secured your API key, significantly reducing the risk of unauthorized use. It's a best practice to apply the most restrictive policies possible for all your API keys.
What it is: A simple code that identifies your application.
When to use: For accessing public data or services where no user is logged in.
Examples: Google Maps API, YouTube API (for public videos), Cloud Translation API.
What it is: A secure way to get a user's permission to act on their behalf.
When to use: For accessing a user's private data.
Examples: Reading a user's Gmail, accessing their private Google Drive files, or viewing their Google Calendar events.
In short: If your app needs to access a specific user's private account data, use OAuth. For everything else, use an API Key.
https://www.googleapis.com/auth/userinfo.emailThis scope grants your application access to the user's primary email address. It's commonly used for identifying and communicating with the user.
-https://www.googleapis.com/auth/userinfo.profileThis scope allows your application to see a user's basic, public profile information. This includes their name, profile photo, gender, and other details they have chosen to make public. It's often used to personalize the user experience within your app.
-https://www.googleapis.com/auth/drive.fileThis is a specific, per-file access scope for Google Drive. It allows your application to:
Create new files and folders in the user's Google Drive.
Access and modify only the specific files and folders that your application has created.
Crucially, this scope does not grant permission to see, access, or modify other files in the user's Drive that were created by the user or other applications. It's a more secure, limited scope for apps that only need to work with their own files.
-https://www.googleapis.com/auth/spreadsheets
2. Under How will the scopes be used?, describe how your app will use each requested Google API.
3. Create a demo video showing how the scopes will be used. Upload the video to YouTube and provide the link.
Here is a demo video https://youtu.be/sMjlt0LlqCQ , You must need to screencast your own video with your own app, then provide it for Google review.
Click Save when done.
Go to the OAuth Consent Screen and select Audience section.
Click on Publish App to publish your app.
You will get a confirmation popup of "Push to production?"
Click Confirm. Your App will be published.
Go back to Branding Section and edit the app according to your details and app domains. Make sure to provide app logo, app domain fields, authorized domains and developer contact information.
Before verification process, you will be asked to enter Homepage Link, Privacy Policy and Terms of Service URL.
Ensure you have valid URLs for your app's Privacy Policy.
Enter these URLs in the corresponding fields and click Save and Continue.
Google will now review your app to ensure it complies with their policies. The review process may take several days to a week. You will receive email notifications if additional information is needed or when your app is approved.
Once your app is verified, you can start using it with the Google Drive and Google Sheets APIs for data synchronization or other functionalities.
Return to your BotSailor settings:
Paste the Google API Key
Paste the Client ID
Paste the Client Secret
“Force User To Use Own API Key” toggle is optional if you're setting up a custom environment for end users
Enable Social Login toggle (optional, for user login via Google)
Click the Save button to complete your integration.
đź’ˇ Tips & Best Practices
Always restrict your API Key usage under Google Cloud to only required domains for better security.
Regularly monitor your Google Cloud dashboard to track API usage.
If you're offering login with Google, ensure your OAuth Consent Screen is properly configured with your logo, support email, and scopes.
đź“Ś Why Set Up Google API?
Connecting your Google API enables smooth automation and integrations like:
Auto-logging data into Google Sheets
Showing dynamic locations via Google Maps
Multi-language chatbot support with real-time translation
Allowing users to log in using their Google accounts
🧩 Conclusion
With just a few steps, your BotSailor reseller platform can be fully connected with Google’s powerful services. Whether you're managing leads, storing customer data, or offering a seamless login experience — Google API integration can significantly boost your automation game.
FAQs
What is the purpose of Google API integration in BotSailor?
Google API integration allows BotSailor resellers to connect services like Google Sheets, Maps, Cloud Translation, and Google Login to enhance chatbot functionality and user experience.
Which Google services can I integrate with BotSailor?
You can integrate:
Google Sheets to log form responses.
Google Maps for dynamic location-based features.
Cloud Translation API for multilingual chatbot responses.
Google OAuth Login for allowing users to sign in with their Google accounts.
Where do I find the Google integration settings in BotSailor?
Log in to your reseller dashboard and go to:
Settings → Google Integration
You’ll find fields to input API Key, Client ID, Client Secret, and OAuth redirect URIs.
Do I need a Google Cloud account for this integration?
Yes, you must create a project in the Google Cloud Console to generate the necessary API credentials.
Which APIs should I enable in my Google Cloud project?
Enable the following from APIs & Services → Library:
Google Sheets API
Google Maps JavaScript API
Cloud Translation API
OAuth 2.0 Client ID (for login)
What redirect URIs do I need to configure for OAuth?
Add these to your OAuth Client ID:
https://yourdomain.com/google/import/account/callback
https://yourdomain.com/login/google/callback
(Check your BotSailor panel for exact values.)
Where do I paste the API credentials in BotSailor?
Paste your:
API Key
Client ID
Client Secret
in the Google Integration section under BotSailor settings.
Can I enable Google Login for users?
Yes, enable the Social Login toggle in your BotSailor settings after setting up OAuth credentials.
Is it mandatory to enable all Google APIs?
No. You only need to enable the APIs required for the features you want (e.g., enable only Google Sheets if you just need form logging).
How do I secure my Google API Key?
Restrict API key usage in your Google Cloud Console by:
Limiting it to specific domains
Enabling only required APIs
This protects your quota from abuse.