# Pagerless for Netlify

> Woken only when it matters, and one tap undoes a bad deploy: Pagerless restores the previous deploy.

URL: https://pagerless.dev/integrations/netlify
Updated: 2026-10-22

## Set up

Netlify Functions run Node: `import "pagerless/auto"`. Static sites: [pagerless/browser](https://pagerless.dev/integrations/browser).

Store the key with `netlify env:set PAGERLESS_KEY pl_live_...`. Or run `npx pagerless connect` and it finds your services and places the key for you.

## Fixes on Netlify

| Fix | On Netlify |
| --- | --- |
| Undo the update | Restores the previous deploy |
| Restart | Rebuilds |
| Add capacity | Not available |
| Deploy events | Yes: errors right after a deploy are tied to it |
| Access it needs | a Netlify personal access token |

## Questions

### Can Pagerless roll back Netlify automatically?

Yes, if your rules set undo to alone. By default it asks first, and approving an undo needs your passkey (Face ID or Touch ID). It then restores the previous deploy.

### Does Pagerless need admin access to Netlify?

It needs a Netlify personal access token. It is stored encrypted and used only for the fixes listed above. You can skip it: alerts work without it.