Automated CodePen Embed Health Checks
Every Monday, WebRun opens CodePen, works through the list of pens your own pages embed, checks that each one still exists and is still publicly visible, records the state of every pen in Airtable next to the page it sits on, and posts the broken embeds to Slack.
How do I check that the code embeds on my site still load?
Every Monday WebRun opens CodePen and works through the pens your own pages embed, confirming each one still exists and is still public. It records the result per embed in Airtable next to the page it sits on and posts the failures to Slack, so a broken embed is fixed before a reader reports a blank box.
- Broken embeds are found on Monday rather than reported by a reader
- Every failure names the exact page it affects
- The channel stays silent in weeks when every embed passes
Built for web teams · front-end developers · technical writers · design system maintainers
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
codepen.io/loginin a real browser with your saved login - no setup, no API keys. -
1
CodePen - check each embedded pen
codepen.io
WebRun opens CodePen to check each embedded pen. - Open CodePen and sign in to the account or team that owns the pens
- Work through the list of pens your pages embed and confirm each one still opens
- Note whether the pen is still public, whether its title or URL changed, and whether it now sits under a different owner
Done when Every embedded pen has been opened and its visibility confirmed.
-
2
Airtable - record the state of each pen
airtable.com
WebRun opens Airtable to record the state of each pen. - Keep one row per embed with the pen, the page it sits on and the result of this week's check
- Mark rows as fine, private, renamed, or missing, and stamp the date checked
- Leave a row in a failing state until a later run finds it working again
Done when Every embed row carries this week's result and a date.
-
3
Slack - post the broken embeds
slack.com
WebRun opens Slack to post the broken embeds. - Post only the embeds that failed, with the page each one appears on
- Say what changed for each: deleted, made private, or renamed
- Stay quiet when every embed passes, so the channel only sounds when there is work
Done when The web team knows which pages have a broken embed.
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 change pen settings or visibility?
No. WebRun opens each pen to read its state. Changing visibility, renaming, and republishing all stay with the person who owns the pen.
Does it edit the pages that hold the embeds?
No. It reports which page each broken embed sits on. Editing your site is left to you, because a live page change cannot be undone by a script.
What if a pen belongs to someone outside the team?
It is still checked and reported, and the row notes that the owner is external, so you can decide whether to keep depending on it or fork a copy.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.