The problem: your code can notice, but it cannot wake you
Builders already have scripts that know when something is wrong. A health check sees the API return 500s. A bot sees its order filled. A nightly job sees the backup failed. What they usually do with that knowledge is send an email, a Slack message or a push notification, and all of those wait politely until morning.
Full on-call tools solve this for companies with rotations and escalation policies. A solo founder, a two-person team or someone running a side project usually needs something smaller: one link that makes one or two phones ring when the script says so.
Three builders, three alarms
The site that goes down at 3am. Maya runs a small shop on her own. She already uses a site monitor that can call a webhook when the site stops answering. She makes an anything alarm called "Shop down" with a 30 minute cooldown, shares it with her co-founder, and pastes the link into the monitor's alert settings. The first outage at 03:10 rings both phones. She fixes the expired certificate; he goes back to sleep once she posts in their chat.
The bot that needs a human. Ben runs his own trading script. It places orders on its own, but when a large order fills he wants to look at the position himself before the next session. He adds one line to the script's fill handler that POSTs to his alarm's link. LFG Alarm does not trade and sees nothing the script sends; it just rings, and Ben opens his own dashboard to check.
The deploy that should not fail quietly. A three-person team adds a final step to their CI pipeline: if the production deploy fails, call the alarm link. The alarm is shared with all three. A 10 minute cooldown means a pipeline that retries five times rings once.
The integration is one request
curl -X POST https://example.com/lfg-webhook-link
Replace the placeholder with your own link from the app. In a script, the same idea is a single POST when your condition is true, for example the last line of a health check that has just failed. That is the whole integration.
How the link works
- Send an HTTP POST request and it rings. Opening the link in a browser does nothing.
- Nothing you send is shown. Whatever is in the request appears nowhere. It just rings, so name the alarm for what it means ("Shop down", "Big fill").
- A cooldown stops loops. Pick 1, 5, 10, 30 or 60 minutes (10 is the default). Calls during the cooldown after a ring are ignored, so a bot stuck in a loop cannot ring you all night.
- Guard it like a password. If the link leaks, tap New URL and the old one stops working.
- Never public. An anything alarm is private, or shared with friends you choose. Only you know what sets it off.
- Clear answers. A deleted alarm's link answers "not found"; a switched-off alarm answers that it is switched off.
How it rings
On Android an anything alarm rings full screen, even on Do Not Disturb. On iPhone it arrives as a time-sensitive alert with the alarm's own sound; it can come through Focus but respects the silent switch, so keep the ringer on if you depend on it overnight. With an lfg.gm tab open on an awake laptop, it rings there too, for up to ten minutes. See alarms on your laptop.
Make it in the app
- On Alarms, tap 🔮 Anything.
- Under Cooldown, pick 1m, 5m, 10m, 30m or 1h.
- Choose who it is for, private or friends, and tap Arm it.
- On the link card, tap Copy, then Test fire to ring only your own phone and check it works.
- Paste the link into your monitor, script, Zap or shortcut.
Your AI agent can make one too: ask for an anything alarm, private or for friends, and it hands you the link to paste into your monitor, script or Zap.
Set one up with no code
Under the link, What's a webhook? explains it for people who have never used one, with three everyday ideas: ring when an app you use says so (Zapier, Make or IFTTT), a one-tap button on your phone for the crew ("we're outside", "the game's on"), and ring when your site goes down or a big sale lands. It also has a prompt to copy into ChatGPT, Claude, Grok or any AI. The prompt explains how the link works with a placeholder in place of your real link, then asks the AI to suggest ideas and walk you through a free, no-code tool step by step. You paste your real link into the tool yourself.
Common mistakes
- Testing by opening the link in a browser. That sends a GET request and does nothing. Use Test fire, or a POST.
- A cooldown that is too short for a flapping service. If your site goes up and down every minute, a 1 minute cooldown rings every minute. Use 30 minutes.
- Pasting the link into a public repository. Keep it in a secret or environment setting, and tap New URL if it ever leaks.
