Automated mParticle Connection Health Alerts
Every morning, WebRun opens mParticle, checks the status of every input and output connection, books a short fix-it slot on the data team's Google Calendar for any connection that is failing, and posts the full status list to Microsoft Teams.
How do I catch broken mParticle connections before reports break?
WebRun checks every mParticle input and output connection each morning and flags any that are failing. When one is down, it books a short fix-it slot on the data team's Google Calendar and posts the full connection status to Microsoft Teams, so a broken feed gets scheduled attention before downstream reports go stale.
- Broken connections get caught the same morning, not when a report looks wrong
- Fix-it time is already on the calendar before anyone asks
- The whole team sees connection status in one Teams post
Built for data engineering teams · marketing analytics teams · CDP administrators
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.mparticle.comin a real browser with your saved login - no setup, no API keys. -
1
mParticle - check connection status
mparticle.com
WebRun opens mParticle to check connection status. - Open mParticle and go to the connections dashboard
- Check the delivery status of every input and output connection
- Note which ones are active, warning, or failing
Done when Every connection has a checked status for today.
-
2
Google Calendar - book a fix-it slot
calendar.google.com
WebRun opens Google Calendar to book a fix-it slot. - If any connection is failing, open the data team's Google Calendar
- Find the next open slot in working hours
- Book a 15 minute fix-it hold titled with the broken connection's name
Done when A failing connection has a fix-it slot on the calendar.
-
3
Microsoft Teams - post the status list
microsoft.com
WebRun opens Microsoft Teams to post the status list. - Open the data team channel in Microsoft Teams
- Post the full connection status list, failing ones first
- Include the fix-it slot time for anything broken
Done when The team has today's connection status in Teams.
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 WebRun fix the broken connection itself?
No. It only reads connection status in mParticle and flags what's failing. Reconnecting or reconfiguring a connection stays a manual, deliberate action.
Will it double book the calendar?
No. It checks for the next genuinely open slot before booking, so the fix-it hold never overlaps an existing meeting.
What counts as a failing connection?
Any input or output that mParticle itself reports as warning or failing status. Healthy connections are just listed, not flagged.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.