Netlify

Deploy your product to Netlify. Your factory’s deployment engineer handles the release; you approve it.

What it enables: shipping a product to a Netlify site, either by generating the CI workflow in your own repository or by having Sapient deploy directly.

Connect

Settings → Connectors → Netlify.

Field	Where to get it
API token	Netlify → User settings → Applications → Personal access tokens → New access token
Site ID	Netlify → your site → Site configuration → General → Site ID

The token is encrypted before it’s stored; it never appears in a log, an agent prompt, or an audit entry.

GitOps or managed — pick per product

GitOps (recommended). Sapient writes a Netlify deploy workflow into your repository. Netlify deploys from your own CI and the pipeline stays readable and reviewable in the repo.

Managed. Sapient calls the Netlify API directly to create the deployment.

Choose per product in the product’s deployment settings. Prefer GitOps unless you have a reason not to: nothing deploys that isn’t in your repository.

Approvals

Deploying is approval-gated. The factory prepares the release and waits for you — in the control room, the iOS app, or sapient approvals approve <id>.

Troubleshooting

“Site not found.” The site id is wrong, or the token belongs to an account that can’t see that site. Both are in Netlify’s UI at the paths above — the site name is not the site id.

401 from Netlify. The token was revoked or expired. Create a new one and re-paste.

Build fails immediately. Check the build command and publish directory on the Netlify side. The factory reports Netlify’s own build log rather than paraphrasing it.

Removing

Remove the connection under Settings → Connectors. Products configured to deploy here stop being deployable until you connect another target; deployed sites are untouched.