Catch an automated flow that quietly stopped sending
Every morning, WebRun opens Klaviyo, walks your live flows, checks each message is live rather than sitting in draft, reads yesterday's recipients and revenue per recipient against the recent average, records the readings in Notion, and posts anything that stopped sending or dropped sharply to Slack.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I know when a Klaviyo flow stops sending?
WebRun checks your Klaviyo flows every morning for messages left in draft and for sends that fell against the recent average. It records each flow's recipients and revenue per recipient in Notion, then posts a Slack alert naming the flow and the message whenever one quietly stops sending.
- A broken flow is caught in a day instead of at month end
- Every alert names the exact flow and message at fault
- Quiet days stay quiet: Slack only hears when something is wrong
Built for ecommerce marketers · email marketing managers · DTC brands · agencies · retention teams
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
www.klaviyo.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Klaviyo - check flows and messages
klaviyo.com How to Automate Klaviyo
WebRun opens Klaviyo to check flows and messages. - Open Klaviyo and list every flow you rely on, with its trigger and its live or draft status
- Open each flow and check whether any message inside it is still in draft rather than live
- Read yesterday's recipients and revenue per recipient for each flow message
- Compare against the trailing average and flag anything that sent far less than usual or nothing at all
Done when Every watched flow has a live-or-draft status per message and yesterday's send figures.
-
2
Notion - record the daily readings
notion.so How to Automate Notion
WebRun opens Notion to record the daily readings. - Write one Notion row per flow per day with recipients, revenue per recipient and message status
- Keep the trailing average alongside so the comparison is visible in the table
- Mark any day where a flow sent zero, and note whether the trigger or a draft message explains it
- Retain history so a slow decline is as visible as a sudden stop
Done when Notion holds today's reading for every flow next to its recent average.
-
3
Slack - post what stopped sending
slack.com How to Automate Slack
WebRun opens Slack to post what stopped sending. - Post to your marketing channel in Slack only when something looks wrong
- Name the flow, the specific message and what changed: draft status, zero sends, or a drop against the average
- Put the flow with the largest revenue at risk first
- Stay silent on days where every flow is sending normally
Done when The team has been told which flow stopped sending, or nothing was posted because all are healthy.
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 turn a draft message live for me?
No. WebRun reads flow and message status and reports what is not sending. Setting a message live stays a human decision inside Klaviyo.
Does it send any marketing email?
No. It never sends, schedules or edits a campaign or flow message. It only reads the numbers and posts an internal Slack alert.
How does it decide a drop is real?
It compares yesterday's recipients against the trailing average stored in Notion, so normal weekday variation is ignored and only a genuine fall is flagged.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.