IT OPS

On-Demand TLS Health Check for a Single Domain

Accepts a domain via webhook, fetches its live certificate chain, and returns expiry, issuer, and chain validity in seconds.

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerwebhook
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWebhook receives target domain payloadHTTP webhook
  • ActionOpen TLS connection and fetch served cert chainShell
  • LogicParse expiry, issuer, SANs; compute days remaining
  • LogicBranch: valid / expiring soon / invalid chain
  • OutputReply to requesting Slack thread with verdictSlack

What it does

Gives engineers a one-call way to inspect any domain's TLS certificate on demand. Send a domain to the webhook and the flow connects to the host, reads the served certificate, and reports the expiry date, issuer, subject alternative names, and whether the chain is currently valid.

When to use it

During an incident when you suspect a cert problem and don't want to wait for the next scheduled sweep, or before a launch to confirm a freshly provisioned cert is live and trusted. Pairs well with a Slack slash command or a runbook button.

How it works

  1. 1An inbound webhook receives a JSON payload with the target domain (and optional port).
  2. 2A shell step opens a TLS connection and extracts the served certificate and chain.
  3. 3The flow parses notBefore/notAfter, issuer, and SANs, then computes days remaining.
  4. 4A branch decides the verdict: valid, expiring soon, or invalid/untrusted chain.
  5. 5The structured result is posted back to the requesting Slack thread with a clear pass/fail badge and the raw details for debugging.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect ShellRun sandboxed commands inside the workspace.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.