Add pulses to scheduled jobs
Connect
SPIRITT
CronlyCronly
No silent job failures
SPIRITT sets up Cronly heartbeats for every scheduled job and wires the pulse into the job itself, adds certificate checks for your domains, organizes them by project, and turns each alert into a ticket and a fix.
What you can do with Cronly.
Every job on a heartbeat
Create a monitor per job and add its pulse so missed runs surface right away.
Certificates never surprise
Add expiry checks for every hostname and port you serve.
Alerts turned into fixes
Read notifications, servers and backups, and act on what failed.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your infrastructure, data jobs or client sites.
02
Connect Cronly
Add your Cronly API key, then connect the repositories and tracker your jobs live in.
03
Hand over the watch
Ask SPIRITT to cover every job with a heartbeat or triage this week's alerts.
Hand over a mission.
Choose a mission. Make it yours.
Put Cronly to work.
Make every job report in
Questions
Cronly, with SPIRITT.
01What can SPIRITT set up in Cronly?+
Projects, cron heartbeat monitors and SSL certificate expiry checks, plus removal of any you retire.
02How do jobs report in?+
Each monitor has a pulse token. SPIRITT adds the pulse to the end of your job, and can pulse after its own scheduled routines succeed.
03Can SPIRITT act on Cronly alerts?+
Yes. SPIRITT reads notifications and the affected monitor, then opens tickets, pages the on-call engineer or confirms a fix.
04What else can it see?+
Monitors, projects, certificates, users, servers and crontab backups, plus your account timezone and plan summary.
05Does it handle pulse tokens safely?+
SPIRITT stores each token as a secret in the job's environment rather than in code or chat.
06What does the connection need?+
A Cronly API key for your company account.