Know the day a FormAssembly form stops collecting
Every morning, WebRun opens FormAssembly, reads yesterday's submission count for every live form, compares it to that form's recent daily average, posts anything that has dropped sharply or gone to zero into Microsoft Teams, and sends the same alert to Telegram for whoever is on call.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find out when a web form stops receiving submissions?
WebRun checks your FormAssembly forms every morning and compares yesterday's submission count for each one against its own recent baseline. Any form at zero or sharply below normal is posted to Microsoft Teams with its owner and last edit date, and the same alert reaches the on-call Telegram channel.
- A broken form is caught the next morning, not weeks later
- Each alert names the owner and the last edit that could explain it
- Quiet days stay quiet, so the alert keeps its meaning
Built for marketing operations · web teams · higher education administrators · revenue operations
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
app.formassembly.comin a real browser with your saved login - no setup, no API keys. -
1
FormAssembly - compare yesterday against normal volume
formassembly.com
WebRun opens FormAssembly to compare yesterday against normal volume. - Sign into FormAssembly and open the list of published forms
- Read yesterday's submission count for each form and its average daily count over the recent baseline period
- Flag any form at zero submissions when its baseline is not zero, and any form more than your drop percentage below baseline
- Note the form name, owner, yesterday's count, the baseline, and the date it was last edited
Done when Every live form has yesterday's count against its baseline, and drops are flagged with the owner named.
-
2
Microsoft Teams - raise the forms that went quiet
microsoft.com How to Automate Microsoft Teams
WebRun opens Microsoft Teams to raise the forms that went quiet. - Post the alert to the forms operations channel
- Lead with forms at zero, then forms below the drop threshold
- Show each one with its owner, yesterday's count, the baseline, and when the form was last edited, since a recent edit is the usual cause
- Note which forms recovered since the previous alert so the channel sees resolutions too
Done when The channel has the drop list with owners named, or a short all-clear line.
-
3
Telegram - alert whoever is on call
telegram.org How to Automate Telegram
WebRun opens Telegram to alert whoever is on call. - Send the same alert to the on-call Telegram channel so it reaches a phone
- Keep it to the form name, the drop, and the owner
- Only send when at least one form is flagged, so quiet days stay quiet
Done when The on-call channel has the alert, or nothing was sent because no form was flagged.
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
Will it edit or republish my forms?
No. WebRun only reads submission counts and form settings in FormAssembly. It never edits a form, never changes a connector, never republishes, and never deletes a submission. Fixing a broken form stays a human job.
How does it avoid false alarms on quiet forms?
It compares each form against its own recent baseline, not against a fixed number. A form that normally gets no submissions on a Sunday is not flagged, and a form whose baseline is zero is skipped entirely.
Does it read the submitted data?
No. The alert uses counts only. Field values and respondent details stay inside FormAssembly and are never copied into Teams or Telegram.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.