Automated WP Engine Launch Checks
Every morning, WebRun opens WP Engine, finds the environments still heading to production, checks the SSL certificate, PHP version, backup points, and redirect rules on each, writes a pass or fail per item into Airtable, and opens a Trello card for every launch blocker it finds.
How do I check every new site against a launch checklist before go-live?
WebRun opens WP Engine every morning and runs your pre-launch checklist on every environment heading to production: SSL certificate, PHP version, recent backup point, and redirect rules. It records a pass or fail per item in Airtable and opens a Trello card, assigned to the site owner, for every blocker.
- No site goes live with a missing certificate or an old PHP version
- Every blocker lands as an owned Trello card with a due date
- The same checklist runs on every launch, not just the ones someone remembered
Built for web agencies · WordPress developers · hosting ops teams · technical project managers
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
my.wpengine.comin a real browser with your saved login - no setup, no API keys. -
1
WP Engine - check each site against the launch list
wpengine.com
WebRun opens WP Engine to check each site against the launch list. - Open WP Engine and list the environments tagged as heading to production
- For each site, check the SSL certificate is installed and not close to expiry
- Check the PHP version against the version your team standardises on
- Confirm a recent successful backup point exists and that redirect rules are in place
Done when Every pre-launch site has a result recorded for each checklist item.
-
2
Airtable - record pass or fail per item
airtable.com
WebRun opens Airtable to record pass or fail per item. - Open the launch base and add or update a row per site
- Write pass or fail against each item: certificate, PHP version, backup point, redirects
- Record the value found, such as the PHP version or the certificate expiry date
- Set the site's overall status to ready or blocked
Done when Airtable shows a per-site launch scorecard with the failing items named.
-
3
Trello - raise a card for every blocker
trello.com
WebRun opens Trello to raise a card for every blocker. - Open the launch board and create a card for each failing item, titled with the site and the check
- Put the value found and the expected value in the card description
- Assign the card to the site's owner and set the due date to the planned launch date
- Move any card whose item now passes into the done list
Done when Every launch blocker has an owned Trello card and the fixed ones are cleared.
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 it change anything on the site?
No. WebRun only reads the environment settings in WP Engine and reports what it finds. It never installs a certificate, changes a PHP version, or edits redirects. Fixes stay with your team.
Can I choose the checklist items?
Yes. Tell WebRun which checks matter and the values you expect, such as your standard PHP version or a maximum backup age, and it reports pass or fail against your own list.
Does it publish a site or point a domain?
Never. Going live stays a human decision. WebRun produces the readiness report and the Trello blockers, and your team makes the launch call.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.