# Pagerless for Google Cloud Run

> Woken only when it matters, and one tap undoes a bad deploy: Pagerless sends traffic to the previous revision.

URL: https://pagerless.dev/integrations/google-cloud-run
Updated: 2026-10-22

## Set up

Node, Go or Python SDK. `K_SERVICE` and `K_REVISION` are read automatically.

Store the key with `gcloud run services update SERVICE --update-env-vars PAGERLESS_KEY=pl_live_...`. Or run `npx pagerless connect` and it finds your services and places the key for you.

## Fixes on Google Cloud Run

| Fix | On Google Cloud Run |
| --- | --- |
| Undo the update | Sends traffic to the previous revision |
| Restart | Creates a new revision |
| Add capacity | Changes max instances |
| Deploy events | Yes: errors right after a deploy are tied to it |
| Access it needs | Google OAuth or an IAM service account |

## Questions

### Can Pagerless roll back Google Cloud Run 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 sends traffic to the previous revision.

### Does Pagerless need admin access to Google Cloud Run?

It needs Google OAuth or an IAM service account. It is stored encrypted and used only for the fixes listed above. You can skip it: alerts work without it.