Connect your first integration
PerfCopilot doesn't generate reviews from thin air — it grounds them in evidence pulled from the tools your team uses. The fastest first integration is GitHub for engineering teams, but the same flow applies to Slack, Jira, Email, CRM, and Phone.
Why GitHub first?
For most engineering managers, GitHub is the highest-density signal source: PRs opened, PRs reviewed, comments left, commits authored. It also installs in under two minutes via OAuth — no API keys to copy, no admin permissions from your IT team. Good place to start before the heavier integrations.
Two ways to connect GitHub
There are two flavors:
- Org-wide GitHub App (recommended) — installed once on your GitHub organization, sees every repo your team works in. Best for teams that work in a small number of org-owned repos.
- Per-employee personal access (OAuth) — each engineer connects their own GitHub account. Best for teams that work across many personal repos or open-source.
You can use both — they don't conflict.
Org-wide install
- Go to
/admin?tab=integrations. - Find the GitHub card under "Org-wide" and click Install.
- GitHub will ask you to choose which organization and which repos to grant access to. You can pick "All repos" or a specific allowlist; PerfCopilot only reads, never writes.
- Once installed, click Sync now on the card. The first sync pulls the last 90 days of activity for every employee whose
emailorgithub_loginmatches an account on those repos.
Per-employee OAuth
- Each engineer signs in to PerfCopilot at app.perfcopilot.com.
- From their dashboard, they click their avatar → Account → Integrations.
- They click Connect next to GitHub. A popup opens, they authorize, and the popup closes.
- Their GitHub data flows into the next Sync All on their cycle.
Managers can also send an invite link to an employee to do this in one click — see the Invite to connect action on the team list.
What we pull from GitHub
For each employee in a cycle's window:
- Pull requests opened — count, repos, merged status, time-to-merge
- Pull requests reviewed — count, comments left, approve/request-changes ratio
- Commits authored — count, lines changed, repos touched
- Issues opened / closed — count, repos
These flow into the AI review prompt as a [GITHUB DATA] block with the raw counts, plus a comparative baseline (the median for the employee's team / department / org cohort).
Verify it's working
After your first sync:
- Go to your dashboard → pick an employee → look at the Signals strip.
- You should see GitHub activity grouped by week within the cycle window. Click any signal to see the underlying details (which repo, which PR, who merged it).
- If counts look wrong — too low, too high, or zero where you expected activity — see Integrations → GitHub troubleshooting (coming soon).
Other integrations (overview)
The same /admin?tab=integrations page has cards for everything else PerfCopilot pulls from. Roughly grouped:
- Code & tickets — GitHub, Jira, Linear (coming)
- Communication — Slack, Microsoft Teams, Gmail, Outlook (via MS Graph)
- CRM & sales — Salesforce, HubSpot
- Phone & calls — Aircall (with optional call-quality analysis)
- HRIS & goals — BambooHR, 15Five, Lattice, Asana, Perdoo, Weekdone, Culture Amp
Each card has its own Connect flow; some are OAuth (one-click), some need an API key. The integrations page keeps it organized and tells you the per-employee status.