Integrations
Vercel integration
What the Vercel integration does in Ulika, where its status appears, and links to the detailed connection and private preview guides.
Last updated
Vercel is the best supported host for Ulika. The Vercel integration lets Ulika find the Vercel project behind your site, confirm that a preview of the connector built, and prepare what older connectors need to read published content. This page is the overview. The detailed guides are linked below.
What the integration does#
Matches your site to its Vercel project and checks that the project deploys the repository and branch you selected.
Verifies previews. Ulika checks the preview of its pull request before anything is merged, including previews behind Vercel's login wall (see Private previews).
Prepares the build for older connectors: a build token variable and a deploy hook. New Vite and React connectors need neither.
Reports build failures. Ulika uses Vercel's own deployment status to know when a build failed.
Cleans up. Disconnecting removes only what Ulika created.
Your live site is not changed by connecting Vercel. See Connect Vercel for each step in detail.
Do you need it?#
For a Vite or React site connected today, no: Ulika can verify your host's build through GitHub and publish through Git alone. A Next.js site needs Vercel, and so does a Vite or React site with an older connector. The table in Connect Vercel shows which.
How it appears in the product#
Connect screen. While you connect a site, a card shows the Vercel state. It is titled Connect Vercel to verify private previews when optional, and Connect Vercel when required. After connecting it reads Vercel is connected and names the Vercel project and the site it serves.
Project settings. Under Settings, the Integrations tab lists Vercel in the Deployment group with the description "Deploys published content changes to your production and preview environments." It shows Connected when one of the project's environments is hosted on Vercel. The Environments tab shows where published content is served, with a Vercel badge for the provider.
Two ways to connect#
Integration. Click Connect Vercel and install the Ulika integration on Vercel.
Access token. Open Use an access token instead (advanced), create a token scoped to the one team that owns the project, and paste it into Vercel access token.
Both are explained in Connect Vercel.
What Ulika creates on your Vercel project#
| Item | When |
|---|---|
ULIKA_BUILD_TOKEN (or ULIKA_CONNECTOR_TOKEN) environment variable | Older connectors and the Next.js App Router connector |
| A deploy hook named Ulika followed by the project id | Older connectors |
| A webhook that reports deployments to Ulika | When connected with an access token |
| A Protection Bypass for Automation secret with the note Ulika preview verification | When Vercel allows it, for private previews |
Anything you created yourself is never touched, even with the same name.
Supported project setup#
The Vercel project must be linked to your GitHub repository and deploy the production branch you selected. Otherwise the card says This Vercel project is not linked to GitHub or This Vercel project deploys a different repository.
Learn more#
Connect Vercel: setup, environment variables, statuses, disconnecting.
Private previews: how Ulika verifies previews behind Vercel Authentication.
Troubleshooting Vercel: fixes for common Vercel problems.
Requirements: other hosts Ulika supports.
Was this page helpful?