API Health Monitor
Given an API endpoint + expected behavior, returns a structured health read: latency, status, expected vs actual response shape.
Example automations applied to the boring infra hygiene nobody schedules but everybody needs.
Backups, monitors, SSL/DNS watchers, log scanners, GitHub digests, postmortem drafts.
InTouch is a general-purpose automation platform. This page shows how it can be applied to DevOps / SRE / IT-ops workflows using example skills and jobs from the InTouch Hub. The same platform handles use cases far beyond DevOps; the examples here are starting points to adapt.
The examples below are scheduled or trigger-driven jobs that run alongside your existing monitoring/CI stack. They don't replace Datadog or Prometheus โ they handle the gaps where a custom script + a cron would normally live.
These are examples, not turnkey products. Read the README and YAML for each before running. Most expect either a Sheet, an HTTP endpoint, or an env var pointing at your infrastructure.
SSL certs expire on Saturday morning. DNS records get changed by someone you don't remember authorizing. Disk fills up the day before quarter-end. Backups silently fail and you don't know until you need them.
Your team pushed 47 commits this week, opened 12 PRs, merged 9. Weekly digest of activity beats opening GitHub. Release notes drafted from commit messages. Bad commit message? Catch it on push.
Your prod logs have 3,200 ERROR lines yesterday. Half are duplicates, half are real. Scan, dedupe, surface the actually-new ones. Postmortem draft from an incident thread.
AWS bill jumped 40% last month. You didn't notice. A daily Cost Explorer pull + threshold alert catches it before the invoice does.
Given an API endpoint + expected behavior, returns a structured health read: latency, status, expected vs actual response shape.
Paste a log slice; get a deduped summary of the actual unique errors, frequencies, and likely root causes. Better than `grep ERROR | sort | uniq`.
Given an incident timeline + Slack thread, drafts a postmortem skeleton: what happened, contributing factors, timeline, mitigations, action items.
Summarize a repo's week: commits, PRs opened/merged, issues filed/closed, notable changes. Useful for weekly engineering reports.
Take a vague commit message ("fix stuff", "WIP"); return a structured conventional-commit style message based on the actual diff.
Draft a release notes section from commits between two tags. Categorize by type (features, fixes, breaking changes).
Daily check of a list of hosts; alert at 30/14/7 days before any cert expires. Sheet-backed list of hosts to watch.
Periodic check of DNS records for a list of domains. Alert on any change (A, CNAME, MX, NS). Catches unauthorized changes early.
Periodic HTTP HEAD against a list of URLs. Alert on non-200 or slow responses. Cheap external monitor.
Trust but verify: scheduled check that your backups (S3, local NAS) actually contain recent files, not just an empty success status from yesterday's cron.
Per-host disk fill alerts. SSH out, run df, alert if any mount is over threshold. Headless servers especially.
When a PR is opened, post a Claude-drafted code review comment with suggested improvements. Augments human review, doesn't replace it.
Scheduled cleanup of S3 prefixes older than N days. Prevents your dev/staging buckets from drifting to thousands of dollars/month.
Daily AWS Cost Explorer pull. Alert if today's spend trajectory exceeds a threshold (catches stuck-on EC2 instances and S3 explosion early).
Daily summary of your DB: row counts per table, growth, key metrics. Spot anomalies before customers report them.
InTouch runs as a single JAR on any host with Java 17. Or in a container, or on a Kubernetes pod. Free Personal edition for evaluation.
Each job reads from either a Sheet, an HTTP endpoint, or an env var. Read the README, set the placeholders, point at your infrastructure.
InTouch runs the job on cron-style schedules, logs every run, alerts via your existing channels (email, Slack, Discord, Teams, PagerDuty webhook).
Personal edition is free. Install on your dev box or homelab server. Take a single example, point it at your infrastructure, see if it saves you an hour this week.