On a schedule
Open Linear issues for expiring SSL certificates
Any domain whose certificate expires within 30 days gets one Linear issue and a Slack alert, well before visitors see a browser warning.
- Runs
- On a schedule
- Apps
- Linear, Slack
- AI
- Not needed
- Access
- Linear write; Slack chat:write
Send this to your assistant
Create a ClickRuntime automation: every morning at 8, check the SSL certificates on my domains. For any that expire within 30 days, open a Linear issue once and post to #ops.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A small product team runs a marketing site, an app, an API and a handful of customer-specific subdomains. Most certificates renew on their own, but one sits on an old load balancer and another was bought by hand years ago. Nobody remembers which. The first sign of trouble is a customer screenshot of a full-page browser warning, and by then sign-ups and API calls have already been failing for hours.
Checking each morning and turning anything close to expiry into a Linear issue puts the renewal into the same queue as the rest of the team's work, with a month of warning instead of none.
What you get out of it
A month of warning, not a morning of panic
Thirty days is enough time to renew a manual certificate, wait for a vendor, or fix a broken auto-renewal. The work gets planned instead of done in a rush while the site is down.
The renewal lands in your normal workflow
A Linear issue can be assigned, estimated and tracked like any other task. It shows up in planning and does not depend on someone remembering a Slack message.
One issue per certificate, not one per day
Each expiring certificate opens a single issue, even though the check runs every morning. Your backlog stays clean and the issue stays the one place for that renewal.
Catches the certificates auto-renewal misses
Certificates that renew themselves can still fail quietly when DNS or a validation step changes. A daily check of the live certificate shows what visitors will actually get, not what the provider dashboard claims.
Covers every domain in one list
Subdomains, client sites and old hosts all sit in one list. Adding a domain is one line, so new ones do not slip through.
How it works
What happens, step by step
Every morning at 8, ClickRuntime checks the security certificate on each domain in your list.
It reads the expiry date and picks out any certificate that runs out within 30 days.
For each one it opens a Linear issue, remembering which ones already have an issue so you never get duplicates.
A short alert with the domain and the days left is posted to your #ops Slack channel.
Before it runs live
- Connect Linear
- Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Run it at a different time, more or less often, or only on weekdays
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Google Sheets
- Combine it with other Linear and Slack steps into one automation
Under the hood
The code that runs this automation
import socket, ssl
from datetime import datetime, timezone
from clickruntime import on_trigger, credentials, http, state, notify
DOMAINS = ["example.com", "app.example.com", "api.example.com"]
TEAM_ID = "your-linear-team-id"
def days_left(host):
with socket.create_connection((host, 443), timeout=10) as sock:
with ssl.create_default_context().wrap_socket(sock, server_hostname=host) as s:
expires = datetime.fromtimestamp(ssl.cert_time_to_seconds(s.getpeercert()["notAfter"]), timezone.utc)
return (expires - datetime.now(timezone.utc)).days
@on_trigger
def run(event):
opened = state.get("opened") or {}
alerts = []
for host in DOMAINS:
days = days_left(host)
if days > 30 or host in opened:
continue
query = "mutation($i: IssueCreateInput!) { issueCreate(input: $i) { issue { identifier } } }"
r = http.post("https://api.linear.app/graphql", headers={"Authorization": credentials.secret("LINEAR_API_KEY")},
json={"query": query, "variables": {"i": {"teamId": TEAM_ID, "title": f"Renew SSL certificate for {host} ({days} days left)"}}}).json()
opened[host] = r["data"]["issueCreate"]["issue"]["identifier"]
alerts.append(f"{host}: {days} days left ({opened[host]})")
if alerts:
notify.slack("SSL certificates expiring soon:\n" + "\n".join(alerts), channel="#ops")
state.set("opened", opened)
return {"checked": len(DOMAINS), "new_issues": len(alerts)}FAQ
Common questions
Does it check the certificate my visitors see?
What happens after I renew the certificate?
Can I use a different warning window than 30 days?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Turn Slack support messages into Linear tickets
Every request posted in #support becomes a Linear issue with a clear title, priority and summary, and the link appears in the Slack thread.
See how it worksSend new Linear bugs to the team that owns them
Each new bug lands with the right team in Linear within seconds, and that team hears about it in Slack.
See how it worksTurn meeting transcripts into Linear issues
Send a meeting transcript and every action item becomes a Linear issue, with a summary and links posted in Slack.
See how it worksKeep exploring
Set up “Open Linear issues for expiring SSL certificates” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.