Automated IFTTT Applet Health Alerts
Every morning, WebRun opens IFTTT, checks the run history for every active applet, posts a short health digest to Slack naming which applets ran successfully, and sends a Telegram alert for any applet that has gone quiet or logged an error, so a broken connection between two services does not go unnoticed for days.
How do I know if one of my IFTTT applets stopped working?
Every morning, WebRun checks your IFTTT applet run history and posts a short health digest to Slack naming which applets ran cleanly. If an applet has gone quiet or logged an error, it also sends a Telegram alert naming it, so a broken connection between two services gets caught quickly instead of silently failing for days.
- A broken applet gets caught within a day, not weeks later
- Routine days get a quick, quiet digest instead of noise
- A silently stalled automation stops going unnoticed
Built for home automation enthusiasts · small business owners · solo automation builders · productivity power users
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
ifttt.comin a real browser with your saved login - no setup, no API keys. -
1
IFTTT - check applet run history
WebRun opens IFTTT to check applet run history. - Open IFTTT and review the activity log for active applets
- Note which applets ran successfully in the past day
- Flag any applet that logged an error or has not run when expected
Done when Every active applet's status for the past day is captured.
-
2
Slack - post the daily health digest
WebRun opens Slack to post the daily health digest. - Post today's applet health digest to the team channel
- List applets that ran successfully as a short summary
- Keep the post easy to skim in a few seconds
Done when The team channel has today's applet health digest.
-
3
Telegram - alert on a broken applet
WebRun opens Telegram to alert on a broken applet. - Check whether any applet logged an error or missed an expected run
- Send a Telegram alert naming the applet if one did
- Stay quiet on days every applet ran cleanly
Done when A Telegram alert has gone out only on days an applet needs attention.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it re-enable or fix a broken applet?
No. WebRun only reads the run history and reports it. Reconnecting a service or fixing an applet stays a decision you make yourself in IFTTT.
How does it know an applet has gone quiet?
It compares an applet's run history against how often it is expected to fire and flags it when a run is missing or logged as an error.
Will I get a Telegram alert every day?
No. It only fires on a day an applet actually needs attention. A clean day only gets the routine Slack digest.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.