Use “Register a certificate to watch” in Recued. Record one certificate file so Check the certificates will read it. Keyed on its path, so re-registering the same file converges.
Register a certificate to watch
Use “Register a certificate to watch” in Recued. Record one certificate file so Check the certificates will read it. Keyed on its path, so re-registering the same file converges.
Complete workflow
Certificate Watch
5 pinned recipes
Use Certificate Watch in Recued for tls, expiry, monitoring, and openssl. It includes 6 built-in actions and 4 ready-to-run workflows. Actions that change data use Recued's approval controls.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Check the certificates” in Recued. Read every registered certificate and record whether it is healthy, running out within thirty days, or unreadable. A file that cannot be parsed is reported as unreadable rather than counted as healthy, because those two answers look identical to the expiry check on its own.
Use “Show the certificates” in Recued. List watched certificates with their status, subject and expiry. Read-only — it re-reads no file and re-runs no check.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Use “One certificate” in Recued. Open one certificate from the list that names it, and read everything recorded about that certificate on one page.
Registering
Give the path of a PEM certificate file and a label you will recognise on the board.
⚠ unchecked is not ok. Nothing is read here — not even to confirm the file is a certificate. Check the certificates is what looks, and it is what will tell you a path is unreadable.
⚠ Register the LEAF certificate, not the private key. The key is not a certificate, so it would simply be reported unreadable — but there is no reason to point this at one.
⚠ The path is the key. If the file moves, register the new path; the old row keeps reporting on a file that is no longer there.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (13 steps)
label
trim
Trim whitespace from setting label
path
trim
Trim whitespace from setting path
inputs_valid
all
Check if all conditions are true
inputs_guard
guard
Stop if inputs valid equals
existing
recued-core.certificate-watch.certificate.search
Search certificate on certificate watch
existing_rows
default
Apply default
existing_count
count
Count items in existing rows
cert_exists
compare
Check if existing count is greater than 0
cert_create
recued-core.certificate-watch.certificate.create
Create certificate on certificate watch
skip: step.cert_exists equal true
cert_id
coalesce
Use the first available value from: cert create record id, existing rows 0 id
cert_recorded
compare
Check if cert id has data
cert_guard
guard
Stop if cert recorded equals
card
to_summary
Format results as a summary card
▼
Output
summary
card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
path
setting
=
[object Object]
label
setting
=
[object Object]
Uses (2 operations)
Pack operation
Search certificate on certificate watch
recued-core.certificate-watch.certificate.search
Pack operation
Create certificate on certificate watch
recued-core.certificate-watch.certificate.create
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
Write
Pack
Certificate Watch
external change
Read: certificate.search · No approvalWrite: certificate.create · No approval