# Pagerless for Cloudflare Workers

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

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

## Set up

Wrap the default export with `withPagerless`; cron triggers become job check-ins.

```js
import { withPagerless } from "pagerless";

export default withPagerless({
  async fetch(request, env, ctx) {
    return new Response("ok");
  },
  async scheduled(event, env, ctx) {
    await nightly(env);
  },
});
```

Store the key with `npx wrangler secret put PAGERLESS_KEY`. Or run `npx pagerless connect` and it finds your services and places the key for you.

## Fixes on Cloudflare Workers

| Fix | On Cloudflare Workers |
| --- | --- |
| Undo the update | Deploys the previous Worker version |
| Restart | Not available |
| Add capacity | Not available |
| Deploy events | From the SDK's deploy marker |
| Access it needs | a Cloudflare API token with Workers Scripts edit (connect opens the token page prefilled) |

## Questions

### Can Pagerless roll back Cloudflare Workers 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 deploys the previous Worker version.

### Does Pagerless need admin access to Cloudflare Workers?

It needs a Cloudflare API token with Workers Scripts edit (connect opens the token page prefilled). It is stored encrypted and used only for the fixes listed above. You can skip it: alerts work without it.