What goes wrong with a home-made cron job
A crontab line is easy to write and easy to forget. The machine gets replaced, the timezone is UTC when you assumed local, the script fails quietly for a month, or nobody remembers which box it lives on.
ClickRuntime gives the job a name, a plain-language schedule with an explicit timezone, a history of every run and a log for each one. You can pause or resume it from the ClickRuntime dashboard or by asking your assistant.
Schedules in plain language
There is no cron syntax to learn. Ask for every N minutes (minimum 5), hourly at a given minute, daily at a time, weekdays at a time, or one day a week. Before it goes live, you see the next three run times in your timezone, so there are no surprises about daylight saving or UTC.
Common cron jobs people move here
- Hit an internal endpoint that kicks off cleanup, reindexing or a report.
- Back up a small dataset from one API to another.
- Check that a certificate, domain or API key is not about to expire.
- Send a scheduled digest from a database or spreadsheet API.
Secrets stay out of the script and the chat
Tokens are saved in the ClickRuntime dashboard as secrets, and only your automations can use them. The assistant only ever sees the secret's name. Values are encrypted at rest, are never shown again after you save them, and are masked in logs.