Integrations
Netlify
What works today for a site hosted on Netlify, what the Available status in Ulika really means, and what is not supported yet.
Last updated
Netlify is Available, not Connected, in Ulika. That wording matters: there is no Netlify account connection yet, but a site that is hosted on Netlify and built from GitHub can still be connected, edited and published. This page separates what is real today from what is not, so you can plan around it.
The short answer#
You cannot connect a Netlify account, token or API to Ulika. The Connect button for Netlify in project settings does not connect anything.
You can connect a site that Netlify builds from your GitHub repository. Ulika works with Netlify through your repository and through Netlify's GitHub App.
What works today#
| Capability | Status | How it works |
|---|---|---|
| Detecting that a site is on Netlify | Supported | The site check recognizes Netlify from response headers (x-nf-request-id, a server header that names Netlify) and from *.netlify.app and *.netlify.com addresses. It shows Netlify under Hosting in the check details. |
| Connecting the site and installing the connector | Supported | The connector's build step is started through netlify.toml. See below. |
| Publishing | Supported for connectors using Git delivery | Publishing commits a content file to your default branch. Netlify rebuilds on that push like it does for any commit. No deploy hook is needed. |
| Seeing Netlify's build results | Supported, with a GitHub permission | Netlify's GitHub App is on Ulika's list of recognized hosts, so Ulika can read the build results Netlify reports on GitHub. This needs Ulika's read-only permissions for commit statuses, checks and deployments. |
| Reading a Netlify preview address | Supported with limits | A preview address on netlify.app that Netlify reported through GitHub is accepted. Ulika never sends a Vercel bypass secret to it. |
Ulika never talks to your Netlify account, so none of this is confirmed against Netlify directly. It is worked out from your repository and from what Netlify reports to GitHub.
How the build step starts on Netlify#
Ulika needs your Netlify build to run its build step. It does that by editing the build command in netlify.toml:
If your repository has a
netlify.toml(and novercel.json), thecommandline under[build]becomesnode .ulika/build.mjs. Every other line stays as it was. Your original command is kept in.ulika/connector.jsonand runs unchanged inside the Ulika build.If the repository has no
netlify.toml, Ulika instead wraps thebuildscript inpackage.json: your original script moves tobuild:site, andbuildruns the Ulika step. This only works if Netlify runsnpm run build.If
netlify.tomlhas a build command Ulika cannot read safely (for example a multi-line value), Ulika stops and reports a configuration conflict instead of guessing.If your
[build]table innetlify.tomlsets abasefolder, Ulika uses it as the site's root and checks it against the folder your code lives in. A mismatch stops the connection with The hosting project builds from a different folder.
What is not supported today#
| Item | Status |
|---|---|
| A Netlify account, token or OAuth connection | Not available. Nothing like the Vercel connection exists for Netlify. |
| Ulika creating environment variables or build hooks on Netlify | Not available. Ulika does not call the Netlify API. |
| Reading password-protected Netlify previews | Not possible. A Netlify password page counts as a private preview. See Private previews. |
| Seeing a failed Netlify production build | Not observed. Netlify reports production builds as commit statuses, which do not say which environment they were for. Ulika's automatic undo of a failed live build therefore does not trigger from a Netlify failure. See Approving a connection. |
| A Netlify environment on the project | Not created. In the current version, nothing records Netlify as a project's deploy provider, so the Environments tab shows the provider as No deploy target. |
Older connectors and the Next.js App Router connector read a build token (ULIKA_BUILD_TOKEN) while the site builds. Ulika does not set that variable on Netlify. Without it, those connectors build from the content committed in your repository, so your published edits are not applied. New Vite and React connectors do not use a token.
How Netlify appears in the product#
Open Settings for a project and then the Integrations tab. Under Deployment you see:
Netlify, with the description "Alternative deploy target for projects hosted outside Vercel."
A Connect button instead of a Connected badge.
Clicking Connect shows the notice Netlify is not connectable yet, with the text "Available in the next release." Nothing is connected or changed.
The Environments tab can show a Netlify badge in principle, but its empty-state text ("Connect Vercel or Netlify so publishing has somewhere to land.") describes a connection that does not exist for Netlify yet.
Recommended setup for a Netlify site#
Make sure Netlify builds the site from your GitHub repository on every push to the default branch.
Make sure the build runs through
npm run build, or declare the command innetlify.toml.Connect the site from the dashboard.
When the banner Approve Ulika's updated GitHub permissions appears, approve it so Ulika can read Netlify's build results. See The GitHub App.
Leave Merge automatically once the build passes unchecked (the default) and activate yourself, because Ulika cannot catch a Netlify production failure for you.
Learn more#
Requirements: all supported hosts.
Integrations: Vercel for the best supported host.
Was this page helpful?