PerfCopilot
Get started
HomeDocs
Documentation

Everything you need to write a fair review.

From your first connection to a sealed, delivered review. Set up PerfCopilot, connect your tools, and generate your first cited draft.

Connect Gmail

⚠️ Gmail OAuth is currently disabled. Google's Restricted-scope verification (CASA assessment) hasn't been completed yet, so the OAuth integration path is turned off. Please connect Gmail via IMAP instead — see /docs/integrations/imap/setup. Same signal output (email volume, response time, cross-team comm patterns); different transport. For Gmail accounts with 2-step verification enabled (most), you'll generate an app password and paste that into PerfCopilot's IMAP form. Existing Gmail OAuth connections continue to function until disconnected.

Email count signals — sent / received per employee. No message content.

Prerequisites

  • This is a per-employee integration: each employee connects their own Gmail account
  • A Google account that the employee can sign in to (no Google Workspace admin role required)
  • Managers can send a one-click invite link from Employees; recipients land on a magic-link page that triggers the OAuth flow

1. Generate credentials in Gmail

Gmail uses OAuth, so there are no API tokens to copy. The employee completes the consent themselves.

  1. Sign in to https://app.perfcopilot.com as the employee whose Gmail you're connecting.
  2. Open Account → Integrations, find the Gmail card, and click Connect.

[Screenshot: Google OAuth consent screen showing gmail.metadata scope — pending]

  1. Google's consent screen opens in a popup. Sign in with the Google account you want to connect.
  2. Approve the gmail.metadata scope. PerfCopilot does not request message-body access — only sender / recipient / timestamp headers are read.

Copy these values; you'll paste them in the next step:

  • No fields — OAuth handles credentials.

2. Paste into PerfCopilot

  1. Open Account → Integrations on your PerfCopilot account.

  2. Find the Gmail card and click Connect (or Manage if already configured).

  3. Paste each value into the matching field:

    | Field in PerfCopilot | Value from step 1 | |---|---| | (none) | No fields — OAuth handles credentials. |

  4. Click Save.

[Screenshot: Gmail drawer with credentials filled — pending]

3. Verify

Click Test in the drawer. Expected:

✅ Authenticated as your.name@gmail.com

If you see a red error, jump to Common errors.

Common errors

| Message | What it usually means | Fix | |---|---|---| | Token revoked | The employee revoked PerfCopilot's access from their Google account security settings. | Ask the employee to re-run the Connect flow from their PerfCopilot account. | | HTTP 401: invalid_grant | The refresh token is no longer valid (often a password reset or 6-month idle window). | Re-run the Connect flow to mint a fresh token. | | Scope changed since consent | Google requires fresh consent whenever PerfCopilot's requested scope set changes. | Click Connect again; the new consent screen will list the updated scopes. |

What signals we pull

  • email — emails_sent and emails_received counts per employee per cycle. We never read message bodies, attachments, or subject lines.

Need a feature you don't see? Tell us →.

PreviousGitHubNext Gong