Daily
Check a list of domains from a sheet and open Jira tickets for problems
Each day every domain in your sheet is checked, the status columns are updated, and each new problem opens one Jira ticket.
- Runs
- Daily
- Apps
- Google Sheets, Jira
- AI
- Not needed
- Access
- Sheets read+write; Jira create issues
Send this to your assistant
Create a ClickRuntime automation: every morning, check each domain in my Domains sheet responds and its SSL certificate has more than 21 days left, update the status column, open a ticket in OPS for each new problem, and post to #ops.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
An agency manages dozens of client websites and keeps the list in a Google Sheet. Certificates expire and sites quietly break, and the team finds out from clients. Checking each site by hand is nobody's job.
Checking every row in the sheet daily, writing the result next to it and opening a ticket for each new problem turns the list into a live dashboard. Problems get an owner in Jira before clients notice.
What you get out of it
The sheet becomes a dashboard
Status and expiry dates are written next to each domain. Anyone can see the health of every site.
Adding a site is one row
New clients are monitored as soon as their domain is added. No other setup needed.
One ticket per problem
A problem is ticketed once and remembered until fixed. The ops backlog stays clean.
The team hears in Slack
New problems are posted to the ops channel. Someone picks them up the same morning.
How it works
What happens, step by step
Every morning, ClickRuntime reads the list of domains from your sheet.
It checks each site responds and how long its certificate has left.
The results are written into the status columns next to each domain.
For each new problem, it opens a Jira ticket and posts a note to your #ops Slack channel.
Before it runs live
- Connect your Google Sheets account and pick the spreadsheets it may use
- Connect Jira
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 Slack
- Combine it with other Google Sheets and Jira steps into one automation
Under the hood
The code that runs this automation
from datetime import date, datetime, timezone
from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
from clickruntime import on_trigger, credentials, http, notify, state
JIRA, SITE = "https://api.atlassian.com/ex/jira/your-cloud-id", "https://acme.atlassian.net/browse/"
adf = lambda text: {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": text}]}]}
def jira(method, path, **kw):
resp = http.request(method, JIRA + path, headers={"Authorization": f"Bearer {credentials.connection('jira', 'work')}", "Accept": "application/json"}, **kw)
return resp.raise_for_status() or (resp.json() if resp.content else None)
SHEET_ID = "your-spreadsheet-id"
def check(domain):
resp = http.get(f"https://{domain}", stream=True, timeout=10)
exp = datetime.strptime(resp.raw.connection.sock.getpeercert()["notAfter"], "%b %d %H:%M:%S %Y %Z").replace(tzinfo=timezone.utc)
resp.close()
return resp.status_code < 500, (exp - datetime.now(timezone.utc)).days
@on_trigger
def run(event):
values = build("sheets", "v4", credentials=Credentials(credentials.connection("google", "work")), cache_discovery=False).spreadsheets().values()
domains = [r[0] for r in values.get(spreadsheetId=SHEET_ID, range="Domains!A2:A").execute().get("values", []) if r]
known, results, new = state.get("known") or {}, [], []
for d in domains:
try:
up, days = check(d)
problem = None if up and days >= 21 else ("site error" if not up else f"certificate expires in {days} days")
except Exception:
days, problem = "", "not reachable"
results.append([problem or "OK", days, str(date.today())])
if problem and d not in known:
known[d] = jira("POST", "/rest/api/3/issue", json={"fields": {"project": {"key": "OPS"}, "issuetype": {"name": "Task"}, "summary": f"{d}: {problem}"}})["key"]
new.append(f"{known[d]} {d}: {problem}")
elif not problem:
known.pop(d, None)
values.update(spreadsheetId=SHEET_ID, range="Domains!B2", valueInputOption="RAW", body={"values": results}).execute()
if new:
notify.slack("New site problems\n" + "\n".join(new), channel="#ops")
state.set("known", known)
return {"checked": len(domains), "new": len(new)}FAQ
Common questions
What does it check?
Which columns are updated?
What happens when a problem is fixed?
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
Log daily Jira metrics to a sheet
Each day a row in your sheet records tickets created, resolved, open, stale and the load per person, with an optional summary by email.
See how it worksCreate Jira onboarding tickets from a new-hire sheet
When HR adds a new hire to the sheet, Jira tickets for their accounts and equipment are created and the ticket keys appear in the row.
See how it worksTurn sheet rows into Jira tickets
Requests added to your sheet become Jira tickets within minutes, with the ticket key written back into the row.
See how it worksKeep exploring
Set up “Check a list of domains from a sheet and open Jira tickets for problems” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.