Vercel Integration
One OAuth click to auto-configure Vercel preview deployments
Table of Contents
What is the Vercel integration?
The QA Note Vercel integration uses Vercel's Connectable Account Integration (OAuth 2.0) to authenticate your team, then performs every Vercel setup step needed to receive deploy events — automatically. Those deploy events are correlated with fix commits recorded via commit keys to mark issues "ready to verify."
The manual steps that used to be required (paste project ID → confirm preview deployments are enabled) collapse into a single project selection, eliminating silent failure modes such as previewDeploymentsDisabled: true.
Webhook delivery is handled by the single Integration Console channel that is configured automatically when you install the QA Note integration from the Vercel Marketplace. There is no per-project webhook URL to register and no signing secret to copy by hand.
Installation
1. Click "Connect Vercel"
Open the project Settings → Integrations tab and click Connect Vercel. QA Note redirects you to Vercel's OAuth approval screen.
2. Select team and install
Choose the team QA Note should access and click Install. When you return to QA Note, that team's Vercel projects appear in a dropdown.
3. Pick a project (triggers automation)
Selecting a Vercel project runs the following in parallel:
| Action | API | Effect |
|---|---|---|
| Permission check | GET /v9/projects | Confirms actual team access |
| Enable previews | PATCH /v9/projects/{id} | previewDeploymentsDisabled=false |
| Persist project link | (internal) | projects.vercel_project_id is saved so deployment events from the shared Integration Console webhook can be routed back to the correct project |
On success you see a "Vercel preview linked" toast and the status badge flips to Connected.
Disconnecting
Unlink in QA Note
Click Disconnect on the linked project tile. QA Note clears vercelProjectId for that project. The shared Integration Console webhook stays in place because other projects in the organization may still need it — remove the whole integration from Vercel if you want to tear the channel down.
Remove from Vercel
From Vercel account → Integrations → QA Note → Remove. QA Note receives the integration-configuration.removed webhook and cleans up its installation row automatically.
Scopes
The installation token is limited to:
- Projects Read/Write — list projects, enable preview deployments
- Deployments Read — receive deployment status
- Integration Configuration / Resource Read/Write — manage installation metadata
QA Note never requests environment variables, domains, or billing scopes because none of them are needed for the automation.
Reinstalling
If Vercel releases new scopes or the integration was revoked, open the Vercel Integrations Console, remove the QA Note entry, and reinstall it. The Integration Console webhook is re-provisioned on install, so you do not need to touch per-project webhook settings manually.
Troubleshooting
- Deploy events not arriving — Preview deployments are likely off on the Vercel project. Re-run Connect Vercel in QA Note (auto path) or enable them manually in Project Settings → Git.
- Secret leak response — In Vercel Integrations Console, regenerate the Client Secret, replace
VERCEL_INTEGRATION_CLIENT_SECRET, and re-run the OAuth round-trip. Per-installationaccess_tokens are unaffected.