Automated Webflow Publish Monitoring
Every morning, WebRun signs in to Webflow, opens each site in your workspace, checks the last publish result and whether staged changes are still waiting to go live, posts a status board to Microsoft Teams, and sends you a Twilio text when a publish has failed or a site has sat unpublished too long.
How do I get alerted when a Webflow site fails to publish?
WebRun signs in to Webflow each morning and checks every site in your workspace for a failed publish or staged changes that never went live. It posts a status board to Microsoft Teams and sends a Twilio text to the on-call owner when a site needs attention, so a broken deploy never hides for a week.
- A failed publish is spotted the next morning instead of by a customer
- Staged changes never sit unpublished for weeks unnoticed
- One board covers every site in the workspace, however many brands you run
Built for web agencies · marketing teams · freelance Webflow designers · site owners
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
webflow.comin a real browser with your saved login - no setup, no API keys. -
1
Webflow - check publish state on every site
WebRun opens Webflow to check publish state on every site. - Sign in to Webflow and open your workspace site list
- Open each site and read the last publish date and result
- Note whether the site has staged changes that are not yet published
- Check which domains each site last published to
- Flag any site whose last publish failed or is older than the window you set
Done when Every site in the workspace has a publish status and a staleness flag.
-
2
Microsoft Teams - post the site status board
WebRun opens Microsoft Teams to post the site status board. - Post a status board to your web team channel
- List each site with its last publish date, its result, and whether changes are staged
- Put failed publishes and stale sites at the top
- Note what changed since yesterday's board
Done when The team channel has today's Webflow status board.
-
3
Twilio - text you about a failed publish
WebRun opens Twilio to text you about a failed publish. - Open Twilio and prepare a short alert text for the on-call owner
- Include the site name, the problem, and the last successful publish date
- Send only when a publish failed or a site breached your staleness window
- Leave any customer-facing or bulk message as a draft for a human to approve
Done when The on-call owner is texted whenever a site needs attention, and quiet days stay quiet.
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 publish my site for me?
No. WebRun only reads publish state and reports it. Publishing stays a human decision, so an unfinished design never goes live because an automation pushed it.
Will it text me every single morning?
No. The Twilio text fires only when a publish has failed or a site has sat unpublished past the window you set. Healthy mornings get the Teams board and nothing else.
Can it watch more than one site?
Yes. It walks every site in your Webflow workspace on each run, so agencies and multi-brand teams get one board covering all of them.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.