Before you start
- Get the LFG Alarm app on your phone from Google Play or the App Store, and sign in. Make sets it off; the app is what rings.
- A Make account and a scenario with a trigger module you care about, such as a calendar, a payment app or a form.
Make the alarm
- In LFG Alarm, on Alarms, tap 🔮 Anything.
- Name it for what it means, for example "Big order" or "Board call". Nothing Make sends is shown on the ring screen, so the name is the message.
- Pick a Cooldown, the alarm's quiet time after a ring: 1 minute to 1 hour. Calls inside it do not ring again, so a scenario that processes ten bundles at once rings once.
- Keep it private, or share it with the people who should hear it (an anything alarm is private or friends, never public), and tap Arm it.
- On the link card, tap Copy. Tap Test fire once to hear it on your own phone.
Add the HTTP module
- In the scenario editor, add a module after your trigger and choose the HTTP app, then Make a request.
- URL: paste the alarm's link. It looks like
https://api.lfg.gm/horn/followed by 32 letters and digits. - Method: POST.
- Leave Authentication type, Headers and Query parameters empty, and send no body. LFG Alarm ignores the body, so there is no reason to pass your customer or calendar data along.
- Click Run once and fire the trigger. Your phone should ring, and the module's output should include
"fired":true.
Add a filter so only what matters rings
An alarm that rings for everything stops being an alarm. Make lets you put a filter on the line between two modules: click the line between the trigger and the HTTP module, give the filter a name, and set a condition from an operand, an operator and a value. Only bundles that pass the condition reach the HTTP module and ring you.
Three scenarios that earn a ring
The board call at 6am. Jun is a founder in Singapore with investors in New York, so the important calls land at odd hours. His scenario watches his calendar for events starting soon, and the filter only passes events whose title contains "Board". The "Board call" alarm is shared with his COO. Both phones ring before the call, and nobody has to set a manual alarm the night before.
The order worth waking up for. Sam sells handmade furniture online. Most orders can wait until morning, but a custom order over $2,000 needs a reply the same day before the customer shops elsewhere. The scenario watches new payments, the filter checks the amount is greater than 2000, and only those orders ring Sam and his partner.
The form from the client who pays the bills. Maya runs a small video studio for YouTubers. Her intake form feeds a scenario that files every enquiry in a sheet. A second route, with a filter on the email field matching her two biggest channels, goes to the HTTP module, so those enquiries ring her phone while the rest wait in the sheet.
How it rings
On Android an anything alarm rings full screen, like an alarm. On iPhone it arrives as a time-sensitive alert with the alarm's sound, 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. See alarms on your laptop.
If it does not work
- The module returns 429. The alarm is inside its quiet time, so it already rang recently. If Return error if HTTP request fails is on in the module's advanced settings, Make shows this as an error even though nothing is wrong.
- The module returns 409. The alarm is switched off. Switch it on in the app.
- The module returns 404. The link is wrong, the alarm was deleted, or someone tapped New URL. Copy the link again.
- The module succeeds but nothing rings. Check Method is POST; a GET does nothing.
- The scenario rang late. A scheduled scenario only runs when its schedule says so, and the alarm rings when the HTTP module runs. Check the scenario's schedule if timing matters.
Learn more
- How to make any app, script or feed ring your phone
- Anything alarms and Friends and groups
- The same idea in Zapier, IFTTT, n8n and Home Assistant
Sources and further reading
LFG Alarm is not affiliated with Make.
