Google Connect (Setup)
Introduction
This guide walks you through the full process of setting up Google Cloud, creating projects, and obtaining your Project ID, Client ID, and Client secret. It establishes the core setup shared across all Google Agent team. Because you own and manage your Google Cloud projects, your team’s data remains fully under your control—no third parties have access to your Google Workspace information.
Time: ~9 minutes
What You'll Need
A Google account (either your company Google Workspace Gmail or a personal Gmail account)
If you are setting up Google Connect for Google Ads, you must use the same email as your Google Ads Manager Account
Google Chrome
1. Project ID from Google Cloud Platform (~2 mins)
The goal of this step is to obtain your Project ID by ensuring you have a Google Cloud Platform (GCP) account set up and a Google Cloud Project ready to use.
Google Cloud - Create a New Project
Go to Google Cloud Console and sign in with your email, accept the terms of Google Cloud if any.
Tap on "Select a project", then inside the pop up
Tap on "New Project"
Note: If you prefer to use an existing project, simply select it and use its Project ID. In that case, you can skip ahead directly to steps 5 and 6
Enter any name you like, then tap on "Create"
After a while, you'll see a notification at top right corner. Tap on "select project"
Congratulations—you’ve successfully created your first Google Cloud Platform project! You should now see a Project ID similar to the example below. Copy and save this Project ID, as you’ll need it later on the Chat page along with your Client ID and Client Secret (from Step 2).
2. Client ID and Client Secret (~5 mins)
In this step, you’ll create a small OAuth app that grants permission to access your Google data. The objective is to obtain a Client ID and Client Secret.
2.1 Set up the consent screen
Go to Google Cloud Console, Click the top menu button
Click “API & Services” in the side menu
Click on "OAuth consent screen", If the “Configure consent screen” option appears, click the “Configure consent screen” button, or proceed to the next step.
Within this page, tap on "Get started".
Fill in App information
App Information
App name — type anything you like, e.g.
My AI ToolUser support email — select your email from the dropdown
Audience:
if your email is within your Google Workspace and your audience is only available to users within your organization, select "Internal", you will not need to submit your app for verification. (Recommended)
Otherwise, select External (for personal email) and add a test user if needed (see below).
Contact Information: enter your email
Finally, agree to terms and tap on "Create", you are done.
(Optional) Add Test users
If you chose "External" audience type earlier, you must follow this setup, or you can skip.
After saving, click Audience in the left sidebar
Scroll down to Test users → click Add users
Enter your Gmail address → click Save
2.2 Create your Client ID and Client Secret
If you already have an OAuth client (Desktop app) in this project, you can reuse it if you have the client ID and client secret, but we recommend creating a new credential for each agent team.
On the same Google Cloud, click Clients (or credentials) on the left sidebar:
Click + Create client
Create OAuth Client ID
Application type: choose Desktop app
Name: anything is fine, like google-skillpack-tool
Tap on "Create"
Copy Client ID and Client Secret
A popup shows your Client ID and Client Secret
Copy both values and paste it to Frevana Chat. This page only shows up once!
Recommend: Tap on "Download JSON" and save the OAuth client credentials somewhere safe.
3. Paste Your Project ID, Client ID and Client Secret back to Chat (~1 min)
Go back to the chat and paste your Project ID, Client ID and Client Secret. Frevana will save them securely on your computer.
After that, the AI will open a browser page for the permission authorizations.
Sign in to Google with the email address you used
Tap on Continue or Allow button, the page might look different from yours depending on which Google services you are using
You can close the page and go back to the Chat after it is done. See screenshot below.
(Optional) For personal emails
If you are using your personal email, you will see something like this. Don't worry, just tap on continue.
⚠️ If you are using your personal email but seeing something like this, it means the email you are using is not within the Test User list. Please follow the part "Add test users" above.
4. Done! 🎉
The AI confirms the connection is working. The Google Cloud project and OAuth app are now set up.
The setup enables common Google APIs in your project. This doesn't grant any access by itself — actual permissions are controlled by the scopes you approve during login.
What to expect next
Depending on which Google Product you're using, the AI may open a browser window to request access to specific Google services. This is normal — it's how Google grants permissions. You'll see a screen asking you to allow access to things like Gmail, Drive, Calendar, etc.
Just click Allow and close the page. The AI will confirm when it's ready.
Service-specific setup
Some Google services need a few extra steps beyond this initial setup:
Google Workspace (Gmail, Drive, Calendar, Sheets, Docs)
Read access are granted. The AI will ask you to enable the Write permissions if you need to create contents
Google Ads
Yes — Google Ads Setup (Developer Token + Customer ID)
Google Search Console
The AI will ask you to enable the Search Console API in a web page
Google Analytics
The AI will ask you to enable the Analytics APIs in a web page
FAQs
Install Google Cloud CLI SDK on Windows
For Windows users, your Google agent team will automatically download the official Google Cloud CLI installer and launch it for you.
If the installer did not pop up, please follow the installation flow as Google’s official guide: https://docs.cloud.google.com/sdk/docs/install-sdk
When the installer opens, keep the default installation options.
At the end of the installation, uncheck all optional actions, including Run gcloud init. （This option automatically greys out after the third option is unselected).
Go back to the agent team and it will complete the Google Cloud setup for you after the installer finishes.
Switching Accounts
Want to use a different Google account? Just tell the AI:
It will walk you through connecting a new account. The old connection is replaced automatically.
Multiple Agent Teams
Each Agent team stores its own credentials in its data/google-connect/ directory. This means:
Google Workspace and Google Ads Agent teams can connect to different Google accounts
Reinstalling or updating one Agent team does not affect another
Credentials are never shared between Agent teams
If you need to use the same Google account across multiple Agent teams, you'll need to complete the authorization step for each one (the GCP project and OAuth client can be reused).
About Permissions
During initial setup, we request read-only access to keep permissions minimal. You can immediately view emails, calendar events, files, and more.
When you ask the AI to do something that requires write access — like sending an email or creating a calendar event — it will ask your permission first. A browser page opens for you to approve the expanded access. This only happens once per service, and you're always in control.
Troubleshooting
"Access blocked" when signing in (after Step 4)
This happens to personal Gmail users who didn't add themselves as a Test User:
Click Audience in the sidebar
Under Test users, click Add users
Enter your Gmail address → Save
Go back to the chat and try again
"Token invalid" or "OAuth client was deleted"
Your credentials expired or were removed. Just tell the AI — it will detect the issue and guide you through reconnecting.
Browser doesn't open automatically
The authorization link is displayed directly in the terminal output. Copy and open it manually in your browser.
"Invalid OAuth JSON" or wrong file type
Make sure you created a Desktop app (not "Web application") when creating the OAuth client in Step 3b.
Setup interrupted (closed browser, timed out):
Ask AI to re-run the same command. The AI will detect that the OAuth client already exists and skip project creation — it will go straight to the authorization step.
Privacy & Security
Credentials stored only locally, inside each Agent team's
data/google-connect/directoryEach Agent team has its own isolated credentials — different SkillPacks can connect to different Google accounts without interfering with each other
The AI never stores your personal data (emails, files, analytics, etc.)
You can revoke access anytime at myaccount.google.com/permissions
The OAuth app you created is yours — no third party has access
All credential files use restricted permissions (only you can read them)
Last updated