Cronly
for LuumenAI
Read cron, certificate, and server monitors, then add new checks with approval
Connect Cronly and Luumen can read your monitors, projects, certificates, servers, and crontab backups on request. Ask which nightly jobs are missing a heartbeat, or which certificates expire soon, and get the answer from the live account. When a new monitor or project is needed, Luumen drafts it and shows you the details before anything is created. Luumen authenticates with an API key.
The Cronly toolbox
10 tools: 3 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet CompanyReturn safe organization, timezone, and subscription-summary fields for the connected Cronly account without exposing billing or integration secrets.
- ReadGet ResourceGet one monitor, project, certificate, user, server, or backup by its resource identity.
- ReadList ResourcesList notifications, monitors, projects, certificates, users, servers, or backups.
- WriteCreate Certificate MonitorCreate an SSL/TLS certificate-expiry monitor for a hostname and port. Approval by default
- WriteCreate MonitorCreate a cron-job heartbeat monitor and return its ID and sensitive pulse token. Approval by default
- WriteCreate ProjectCreate a project for organizing Cronly monitors and certificate checks. Approval by default
- WriteDelete Certificate MonitorPermanently delete an SSL/TLS certificate monitor by numeric ID. Approval by default
- WriteDelete MonitorPermanently delete a cron-job monitor by numeric ID. Approval by default
- WriteDelete ProjectPermanently delete a Cronly project by numeric ID. Approval by default
- WritePulse MonitorRecord a successful heartbeat for a monitor using its sensitive pulse token. Approval by default
One prompt, start to finish
What a governed Cronly run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create certificate monitor, create monitor, create project, delete certificate monitor, and more — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Cronly — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
DynatraceProblems, root-cause detail, and metrics beside the session.
DatadogMonitors, dashboards, and logs pulled into the investigation.
GrafanaRead Grafana health, rings, and dashboard data, then push log records with approval
PrometheusAlerts, metrics, and traces from Prometheus in the session that fixes them.Put Cronly to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.