Automated Codemagic Certificate Expiry Reminders
Every Monday, WebRun opens Codemagic, reviews iOS and Android signing certificates and provisioning profiles, adds a Google Calendar reminder for anything expiring within 30 days, and posts a heads-up in Microsoft Teams so a mobile release never gets blocked by an expired certificate.
How do I avoid a Codemagic signing certificate expiring unnoticed?
WebRun reviews Codemagic's code signing identities and provisioning profiles every Monday, flags anything expiring within 30 days, and adds a Google Calendar reminder a week ahead of the expiry date. It also posts a heads-up in Microsoft Teams, so a mobile release never gets blocked at the last minute by a certificate nobody noticed was expiring.
- An expiring certificate gets flagged 30 days out instead of on release day
- A calendar reminder makes sure the renewal actually gets scheduled
- Mobile releases stop getting blocked by expired signing credentials
Built for Mobile engineering teams · release managers · iOS and Android developers · mobile DevOps 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
codemagic.io/signinin a real browser with your saved login - no setup, no API keys. -
1
Codemagic - check signing credentials
- Open Codemagic and review code signing identities and provisioning profiles across apps
- Check the expiry date on each certificate and profile
- Flag anything expiring within the next 30 days
Done when Every signing credential expiring within 30 days is identified with its app and expiry date.
-
2
Google Calendar - schedule the expiry reminder
calendar.google.com
WebRun opens Google Calendar to schedule the expiry reminder. - Open the mobile release team's Google Calendar
- Add a reminder one week before each credential's expiry date
- Title it with the app name and credential type
Done when A calendar reminder is scheduled ahead of every expiring signing credential.
-
3
Microsoft Teams - post the heads-up
microsoft.com
WebRun opens Microsoft Teams to post the heads-up. - Post a heads-up to the mobile team's Microsoft Teams channel
- List each expiring certificate or profile with its app and expiry date
- Link to the credential in Codemagic
Done when The mobile team has this week's signing credential heads-up in Teams.
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 WebRun renew the certificate itself?
No. Renewing a signing certificate happens in the Apple or Google developer portal and requires your account credentials, so WebRun only reminds you. It never renews anything on its own.
How far ahead does it warn?
It flags anything expiring within 30 days and schedules a calendar reminder a week before the expiry date, giving enough runway to renew without rushing.
Does it cover both iOS and Android credentials?
Yes. It checks every signing identity and provisioning profile configured in Codemagic across both platforms.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.