What is a webhook?
A webhook is a private URL another tool can call when something happens. Page Me turns that request into a push notification on your iPhone.
Page Me turns that doorbell into a private iPhone page for agents, scripts, automations, and workflows that need your attention.
The short version before you wire Page Me into agents, deploys, cron jobs, or personal scripts.
A webhook is a private URL another tool can call when something happens. Page Me turns that request into a push notification on your iPhone.
A pager is an alert path you reserve for events that deserve attention. It is quieter than chat and more intentional than a general notification feed.
An agent pager lets Codex, MCP tools, deploy checks, scripts, and automations reach you when work finishes, fails, or needs a decision.
Channels give each tool its own webhook URL, defaults, and rotation path. If one URL leaks or gets noisy, you can fix that channel without breaking the rest.
Treat every webhook URL like a password. Put it in a secret manager, local config file, CI secret, or automation setting, and rotate it if it appears in logs or screenshots.
Page when a build, export, crawl, or long-running agent task is ready for review.
Needs inputUse time-sensitive priority when an agent is blocked on a real decision from you.
Failure onlySend alerts for failed deploys, broken scheduled jobs, or scripts that need a human recovery step.
One channel per sourceKeep Codex, GitHub, Vercel, cron, and personal scripts separate so history and rotation stay clean.
A Page Me webhook URL is intentionally simple to use, which means it should be handled like a secret.
A webhook URL can send pages until you rotate or disable that channel.
Use names like PAGE_ME_WEBHOOK in terminals, CI, and agent config instead of hard-coding the URL.
If a URL appears in a repo, transcript, screenshot, or tool you no longer trust, rotate that channel in the app.