The Google API Integration page allows you to connect your platform with Google services using OAuth authentication. This enables users to securely link their Google accounts and use features such as Google Sheets, Calendar, and Contacts within the platform.
This integration is essential for automation, data synchronization, and workflow enhancements.
What This Is Used For
Once configured, users can connect their Google accounts to enable:
- Google Sheets → read/write data for automation and syncing
- Google Contacts → import and sync contacts into the platform
- Google Calendar → create and manage events via automation
- User Profile Access → fetch basic user information
These integrations help extend platform capabilities and enable real-time workflows.
Required OAuth Scopes
These are the scopes the platform requests when a user connects Google:
Add these scopes under OAuth consent screen → Data Access. Do not re-list them inside the configuration steps below.
Step 1: Go to Google Cloud Console
Open: https://console.cloud.google.com/
Step 2: Create or Select a Project
- Create a new project OR Select an existing project
Step 3: Enable Required APIs
Go to APIs & Services → Library and enable:
- Google Sheets API
- Google Calendar API
- Google People API (for contacts)
- Google Maps API (for Inbox)
- Google Translate API (for Inbox)
Step 4: Complete OAuth Consent Setup and Verification
After creating your project, you must fully configure the OAuth consent screen in the Google Cloud Console.
Go to APIs & Services → OAuth consent screen
Ensure that all required sections are completed, including:
- Branding (application name, logo, support email)
- Audience (internal or external users)
- Clients (OAuth client configuration) - Refer Step 5
- Data Access (add the scopes from Required OAuth Scopes)
- Settings (general app configuration)
Once all sections are properly configured, proceed to the Verification Center and submit your application for verification if required.
Verification is mandatory when using sensitive scopes such as Google Sheets, Contacts, or Calendar. Until verification is approved, access may be limited to test users only.
Step 5: Create OAuth Credentials
Go to APIs & Services → Credentials
- Click Create Credentials → OAuth Client ID
- Select:
Step 6: Copy Credentials
After creating credentials, copy:
- Client ID
- Client Secret
- API Key (from credentials section)
Go to Google API Integration page and:
- Paste API Key
- Paste Client ID
- Paste Client Secret
- Enable Google OAuth
- Save settings
Testing the Integration
After saving:
- Click Test (if available)
- Try connecting a Google account
- Verify that Sheets, Contacts, and Calendar access works correctly
Review Submission Pack
1) App Use-Case Description (Copy-Paste)
Use this text when Google asks:
“Please provide a detailed description of how your app uses the permission or feature requested, how it adds value for a person using your app, and why it’s necessary for app functionality.”
Overall Description
Our platform is a business communication and automation system used by companies to manage contacts, conversations, workflows, and scheduling from one dashboard. Google OAuth is used so a signed-in user can securely connect their own Google account and authorize only the data access required for enabled features.
We use the requested scopes to support three user-facing capabilities:
- Google Sheets sync for importing/exporting business data and automation records,
- Google Contacts sync for keeping customer/contact records updated,
- Google Calendar integration for creating and updating events from workflow actions.
These permissions are necessary because the features directly read or write user-owned Google resources after explicit user consent. Without these scopes, the connected features cannot function.
2) Scope-by-Scope Justification (Copy-Paste)
We use this scope to read and update Google Sheets selected by the user so they can sync platform data (such as contacts or workflow outputs) with spreadsheets they already use. This is required for sheet-based automation and reporting.
We use this scope to import and sync contact records between the user’s Google Contacts and our platform contact library. This allows users to manage communication records in one place and keep data consistent.
We use this scope to create and update Google Calendar events triggered by user actions and automation flows (for example reminders or booking follow-ups). It is necessary for calendar-based workflow execution.
We use this scope to identify which Google account is being connected and map it to the correct platform user/workspace for secure authorization and account linking.
We use this scope to display basic profile identity during account linking and to reduce user errors when multiple Google accounts are available.
3) Screen Recording Checklist
Google may ask for a video proving that sensitive scopes are used exactly as described.
What to Record
- Show your platform URL and login.
- Open Platform Settings -> Google OAuth.
- Show configured Client ID and redirect URL domain (mask secrets).
- Click Connect Google and complete OAuth consent.
- Show successful account connection in UI.
- Demonstrate one action per requested sensitive scope:
- Sheets: import/export/sync with a Google Sheet.
- Contacts: import/sync a Google contact.
- Calendar: create or update an event from the platform.
- Show the result in both places (platform + Google product) to prove write/read behavior.
Recording Quality Checklist
- Keep video between 3-8 minutes.
- Use a real test account and real UI flow (not slides).
- Add voice-over or captions explaining each step.
- Mask API keys, client secrets, personal data.
- Do not skip from login directly to final state; show the full consent and usage flow.
4) Upload Instructions
- Upload the video as “Anyone with the link can view” (Google Drive or unlisted YouTube).
- Open Google Cloud Console -> OAuth consent screen -> Verification Center.
- Paste the video link in the verification evidence field.
- In “Scope justification”, paste the overall description plus scope-by-scope text above.
- Submit and keep test account credentials ready if Google requests additional review access.
5) Pre-Submission Checklist
- OAuth consent screen fields are complete (branding, audience, scopes, support email).
- Requested scopes exactly match the Required OAuth Scopes list above.
- Redirect URI exactly matches your platform callback URL.
- Video link is publicly viewable to reviewers.
- Test user credentials are ready for reviewer follow-up.
Verification (Important)
If your app is in production and uses sensitive scopes (like Contacts or Sheets), Google may require OAuth verification.
You may need to:
- submit your app for verification
- provide a demo video
- explain how data is used
- verify domain ownership
Until verified, your app may be limited to test users.
Security Notes
- Keep your Client Secret secure
- Never expose credentials in frontend code
- Use HTTPS for all redirect URLs
- Restrict API usage where possible
Last modified on August 7, 2026
