Hello UptimeRobot Team,
I hope you are doing well.
I would like to submit a feature request concerning the Integrations framework, specifically the Microsoft Teams Webhook integration, but this also applies to other integrations that use webhooks.
Current Situation
When using the MS Teams integration, every status change (up/down/warning) triggers a post to the Teams channel. This works, but it produces notifications even in short, irrelevant downtime events (for example, outages of only a few seconds). For operational teams, this creates noise and makes it harder to focus on actionable alerts.
Requested Change
We would like UptimeRobot to support conditional delivery rules inside an Integration, so the webhook only fires when specific criteria are met.
Examples of desired conditions
Only send a notification if a monitor has been down for more than X seconds/minutes.
e.g. “Send Teams message only if downtime ≥ 120 seconds.”
Optional:
Notifications only for certain monitor types
Notifications only after Y failed checks
Suppress “flapping” alerts
Include additional metadata in webhook payload (timestamp, duration, previous state)
Reason / Value
Helps reduce alert fatigue for operational teams
Prevents Teams channels from filling up with false positives or micro-outages
Makes Teams integration equally flexible as custom Webhooks
Supports workflows where different applications have different SLAs or tolerance levels for short outages
Use Case Example
We use UptimeRobot connected to a Microsoft Teams incident channel.
A service is considered “down” in our SLA only if unavailability lasts longer than 2 minutes.
Today the Teams webhook posts instantly on state changes, even if the downtime is only 5–30 seconds.
A built-in conditional rule within the Integration would solve this cleanly, without additional automation layers.
Suggested Implementation Approaches
Any of the following would be very helpful:
Configuration fields inside the Integration UI, e.g.:
“Notify only if DOWN duration ≥ [X] seconds”
Advanced rule builder, similar to Slack/Pushover filters
Webhook payload extension, allowing downstream systems to filter based on provided “downtime_duration_seconds”
Closing
If possible, please let us know whether this feature is on your roadmap.
We are happy to provide additional details, examples, or test scenarios.
Thank you for considering this improvement and for the great service.
Kind regards,
Emiel