The hourly job you keep meaning to set up
Most hourly jobs are short: fetch something, compare it, maybe send a message. The hard part is not the code. It's finding a place for it to run, keeping that place alive, storing what happened last time, and noticing when it breaks.
ClickRuntime handles that part. Your assistant sets up the automation. We run it every hour, save the log of each run, and keep any values the script remembers for the next run.
What an hourly script can do
Scripts run on Python 3.11 with a set of common packages already installed, including requests, httpx, BeautifulSoup, feedparser, openpyxl, PyYAML, Jinja2, the Slack and Stripe SDKs, and the Google API client.
- Call any HTTPS API, using API keys you save as secrets in the ClickRuntime dashboard.
- Remember a value between runs (the last price, the last item seen) so it only acts on changes.
- Email you directly with no email service to set up, or post to Slack through a connection.
- Write structured logs you can read on the run page.
Every hour, or more often
Ask for "every hour", "every hour at :15" or "every 10 minutes". The shortest interval is 5 minutes. Each run counts toward your monthly runs, so the assistant will suggest the slowest schedule that still does the job. Hourly comes to about 720 runs a month.
When something goes wrong
Every run records its status, how long it took, and a log with secret values masked. If a run fails, the automation page shows the error in plain language and the log lines around it. In your assistant, ask "why did the price watch fail?" and the assistant reads the same run, fixes the script and runs it again until it succeeds. Each change still asks for your approval in your assistant.