Get alerted when a Jitsi meeting runs long
Every 10 minutes, WebRun checks active Jitsi meeting rooms against the schedule, and if a room is still active past its booked end time, pings the host on Telegram and drafts a short heads up text through Twilio for the next scheduled participant, left unsent for a human to approve.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted when a Jitsi meeting runs over time?
WebRun checks active Jitsi meeting rooms every 10 minutes against their scheduled end time, pings the host on Telegram if a room is running long, and drafts a heads up text through Twilio for the next scheduled participant for a human to approve, so back to back meetings do not quietly collide.
- Overruns are caught within 10 minutes of the scheduled end
- The next participant gets a reviewed heads up, not silence
- Every heads up text is approved by a human before sending
Built for remote teams · coworking spaces · consultants · meeting room admins
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
meet.jit.siin a real browser with your saved login - no setup, no API keys. -
1
Jitsi - check for meetings running long
jitsi.org
WebRun opens Jitsi to check for meetings running long. - Check active Jitsi rooms against their scheduled end time
- Flag any room still active 10 minutes past that time
- Note who the next scheduled participant is
Done when Every meeting running past its scheduled time is flagged.
-
2
Telegram - alert the host
telegram.org How to Automate Telegram
WebRun opens Telegram to alert the host. - Send the host a Telegram ping noting the meeting is running long
- Include how many minutes past schedule it is
- Note the next scheduled participant waiting
Done when The host has been alerted internally that the meeting is overrunning.
-
3
Twilio - draft a heads up text
twilio.com How to Automate Twilio
WebRun opens Twilio to draft a heads up text. - Draft a short heads up text to the next scheduled participant
- Leave the draft unsent for a human to review and approve
- Note the delay and a revised expected start time
Done when A heads up text draft exists for the next participant, unsent.
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 the heads up text send automatically?
No. WebRun only drafts it through Twilio. A human has to review and send it before the next participant is contacted.
How is a meeting confirmed to be running long?
By comparing the room's actual active status against the end time booked for it, so a room still in use 10 minutes past that time is flagged.
What if there is no next participant scheduled back to back?
Then only the host is alerted on Telegram, no text is drafted since there is no one waiting to notify.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.