Automated Fastly TLS Certificate Expiry Alerts
Every Monday, WebRun signs into Fastly, reads every TLS certificate and the domains it covers, checks the status and expiration date on each, logs them all in Airtable with the days remaining, and writes a dated renewal plan into Notion for whoever owns the platform.
Fastly
read certificate expiry dates
How do I track when my Fastly TLS certificates expire?
Every Monday, WebRun signs into Fastly, reads the TLS certificates attached to your services, and lists the ones expiring in the next 60 days with the domains each covers. It logs every certificate in Airtable with its days remaining and writes the renewal plan into Notion for the platform team.
- Renewals happen on a calendar rather than after a browser warning
- Every domain on every certificate is accounted for, wildcards included
- Certificates inside 14 days are marked urgent so DNS lead time is planned
Built for platform engineers · DevOps teams · site reliability engineers · IT operations
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
manage.fastly.comin a real browser with your saved login - no setup, no API keys. -
1
Fastly - read certificate expiry dates
WebRun opens Fastly to read certificate expiry dates. - Sign in to Fastly and open the TLS management area
- Capture every certificate with its status, its expiration date, and the domains listed on it
- Match each certificate to the services that serve those domains
- Work out the days remaining on each and sort so the soonest expiry is first
- Flag any certificate that is already past its date or shows a status other than active
- Read only. WebRun never issues, renews, or removes a certificate
Done when Every TLS certificate is listed with its status, expiry date, domains, and days remaining.
-
2
Airtable - log every certificate and domain
airtable.com
WebRun opens Airtable to log every certificate and domain. - Open the certificate register base and update a row per certificate
- Fill in the domains covered, the service, the status, the expiry date, and the days remaining
- Mark anything inside 60 days as due and anything inside 14 days as urgent
- Close off rows for certificates that were replaced since the last run
Done when The register holds a current row for every certificate, with due and urgent flags set.
-
3
Notion - write the renewal plan
notion.so
WebRun opens Notion to write the renewal plan. - Add this week's entry to your platform operations page
- List the certificates due inside 60 days in date order, each with its domains and owning service
- Note which renewals need a DNS change so the lead time is planned for
- Link back to the Airtable register for the full list
- Keep it internal. Nothing is emailed to a certificate authority or a customer
Done when The operations page carries this week's dated renewal plan.
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.
Fastly
Sign in once
Every action is checked against this policy before it runs.
Questions, answered
Will it renew or replace a certificate itself?
No. WebRun reads the TLS view in Fastly and reports what it finds. Issuing, renewing, and removing certificates stay with your platform engineers, and no configuration is changed on a run.
Does it cover every domain on a certificate?
Yes. It records each domain listed on a certificate, so a wildcard or multi-domain certificate shows every site that would start warning visitors if it lapsed.
How far ahead does it warn?
60 days by default, with anything inside 14 days marked urgent. Both windows are yours to change if your renewal process needs more lead time for DNS work.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.