Connect Google Workspace (Gmail, Calendar, Docs, Sheets)

• You need access to the Google Cloud Console. Any Google account can create a free Cloud project; no billing is required for these APIs.
• Have a project selected inside Insynia — the connection is stored per project.

1. Open the project creation page.
2. Give the project a recognizable name (e.g. insynia-workspace) and click Create.
3. Once created, make sure it is selected in the project picker at the top of the console.

Insynia needs the following APIs enabled in the same project that will own your OAuth client. Open each link (with your new project selected) and click Enable.

• Gmail API — Reading and searching email.
• Google Calendar API — Reading events and schedules.
• Google Docs API — Reading and updating documents.
• Google Sheets API — Reading and writing spreadsheets.
• Google Drive API — Locating Docs and Sheets files.

You can also browse the full API Library and search for each API by name.

1. Open the OAuth consent / branding screen.
2. Choose External as the user type (works for both @gmail.com and Workspace accounts for personal use).
3. Fill in the required fields: App name (e.g. Insynia Workspace), User support email, and Developer contact email.
4. Save and continue. You do not need to add scopes here — Insynia requests them during authorization.
5. Under Audience / Test users, add the Google account you intend to connect as a test user.

1. Open the Credentials / Clients page.
2. Click Create client (or Create credentials → OAuth client ID).
3. For Application type, select Desktop app. This is important — Insynia's headless flow relies on a Desktop client.
4. Name it (e.g. Insynia Desktop) and click Create.
5. In the confirmation dialog, click Download JSON. This file is your client_secret_*.json.

1. In Insynia, go to Tools.
2. Select the project you want to connect (the connection is stored per project).
3. Find any Google Workspace tile — Gmail, Google Calendar, Google Docs, or Google Sheets — and click Connect Google. Connecting one enables all four.
4. In the dialog, enter your Google account email and paste the entire contents of the client_secret_*.json file into OAuth client JSON.
5. Click Get authorize link.

After clicking Get authorize link, Insynia opens a Google authorization page in a new tab.

1. Choose the Google account you want to connect.
2. You may see an "unverified app" warning (expected for personal OAuth apps). Click Advanced → Go to <your app name> (unsafe) to continue.
3. Review the requested permissions and click Allow.
4. Google redirects you to a URL (often a http://localhost… page that may not load). Copy the full URL from your browser's address bar — it contains a code=… value.
5. Back in Insynia, paste that URL into Redirect URL (or authorization code) and click Finish connecting.

Open Brain for the connected project and ask something that uses your data, for example:

• "Summarize my unread emails from the last 7 days."
• "What's on my calendar today?"
• "Read the contents of this Google Doc: <docId>."
• "Get the values in Sheet1!A1:D20 from spreadsheet <spreadsheetId>."

Brain works with your connected account on your behalf.

• Click Manage on any Google Workspace tile to see the connected account or to Disconnect.
• Disconnecting removes the stored credentials for that project. To reconnect, start again from Step 5 — your Google Cloud setup from Steps 1–4 can be reused.

• "client_secret_json must be a Google OAuth client file" — You pasted the wrong file or partial text. Paste the full contents of the downloaded client_secret_*.json (it contains an "installed" key for Desktop clients).
• Nothing happens on finish / "redirect_url is required" — Make sure you copied the entire redirect URL (it contains code=).
• accessNotConfigured errors in Brain — One of the required APIs (Step 2) is not enabled in the same project. Enable it and retry.
• Connection stops working after ~7 days — Your OAuth app is still in Testing. Publish the consent screen (Step 3) for long-lived tokens, then reconnect.
• The account isn't allowed on the authorization page — Add it under Test users on the consent screen (Step 3), or publish the app.