# Scheduled jobs that don't belong in a CI pipeline

Source: https://clickruntime.com/alternatives/github-actions-cron

> Plenty of scheduled jobs live in GitHub Actions only because it was there: a nightly report, a price check, a sync. ClickRuntime runs those as Python on a schedule or a trigger link, keeps state between runs, and is set up from your AI assistant.

## Why people move scheduled jobs off GitHub Actions

- **Memory between runs.** Each automation has its own state and counters. No committing a JSON file back to the repo or juggling caches to remember what the last run saw.
- **Webhooks from any service.** Each automation has a trigger link that Stripe, Typeform or any service can call, with signature checks. GitHub's repository_dispatch needs a GitHub token, so third-party webhooks can't call it directly.
- **Doesn't go quiet.** A ClickRuntime schedule keeps running until you pause it. It doesn't depend on activity in a repository.
- **Built from the assistant you already use.** Ask in ChatGPT, Claude, Cursor or any MCP client. It writes the script, tests it and turns it on.
- **Alerts and a run log.** Every run is logged with its output and errors, secrets masked, and you get an email when a run fails.
- **AI included.** Scripts can classify and summarise with a built-in AI model, no API key needed, including on the free plan.

## GitHub Actions cron and ClickRuntime compared

|  | GitHub Actions cron | ClickRuntime |
|---|---|---|
| Made for | CI/CD next to your code: builds, tests, releases | Jobs that run on a schedule or when an event arrives |
| Shortest interval | Every 5 minutes | Every 5 minutes |
| Timing | Scheduled runs can be delayed during periods of high load | Runs at the scheduled time |
| Timezone | UTC, or an optional IANA timezone on the schedule | Your timezone, in plain words |
| Stays on | Scheduled workflows in public repos are turned off after 60 days without repository activity | Runs until you pause it |
| State between runs | None built in. Use caches, artifacts or commit files | State and counters built into every automation |
| Webhooks | repository_dispatch and workflow_dispatch, called with a GitHub token | A trigger link per automation, with Stripe, GitHub, Shopify, Typeform and HMAC signature checks |
| Run length | Up to 6 hours per job on GitHub-hosted runners | Short jobs: a time limit per run |
| Cost | Free for public repos. On GitHub Free, private repos get $12 of compute a month | 250 runs a month free; paid plans from $9 for 2,000 runs |
| Building | Write workflow YAML and commit it | Describe the job in your AI assistant |

ClickRuntime pricing: https://clickruntime.com/pricing

## GitHub Actions cron or ClickRuntime?

### Choose GitHub Actions cron when

- The job is part of building, testing or releasing your code. That's what GitHub Actions is for.
- It needs the repository checked out, a container, or more than a few minutes of compute, such as a nightly test suite or a database dump.
- Your team wants every change reviewed as a pull request next to the code.

### Choose ClickRuntime when

- The job talks to APIs, not your codebase: reports, syncs, price checks, reminders.
- It has to remember what it saw last time, or react to webhooks from other services.
- People who don't use GitHub need to ask for changes, from their own AI assistant.

## Move from GitHub Actions cron

1. **Pick the jobs that aren't CI.** List your scheduled workflows. Keep builds, tests and releases in GitHub Actions; move the reports, syncs and checks that only call APIs.
2. **Ask your assistant to rebuild it.** Connect ClickRuntime to ChatGPT, Claude or Cursor, paste the workflow YAML and the script it runs and say what should happen. It saves a draft you can read before anything runs.
3. **Save your keys in the ClickRuntime dashboard.** Secrets from GitHub don't move over. Save each API key as a secret in the ClickRuntime dashboard, or sign in through the app's OAuth. Keys never go into the chat.
4. **Test it.** Your assistant turns the automation on, runs it once or sends a test event, and fixes it until the run succeeds. Run both side by side for a few days if you like.
5. **Switch the old one off.** Delete the schedule block from the workflow, or the workflow file, once the new automation has run a few times.

## One job, moved from GitHub Actions cron

Before: .github/workflows/daily-signups.yml

```yaml
on:
  schedule:
    - cron: "0 8 * * 1-5"   # 08:00 UTC, weekdays
jobs:
  report:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with: { python-version: "3.11" }
      - run: pip install requests
      - run: python scripts/signups_to_slack.py
        env:
          API_KEY: ${{ secrets.YOURAPP_API_KEY }}
          SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK }}
```

After, the prompt: "Move this GitHub Actions job to ClickRuntime: every weekday at 8:00 London time, count signups from our API in the last 24 hours and post the number to #metrics in Slack, with the change from the day before."

The ClickRuntime script:

```python
from clickruntime import on_trigger, credentials, http, notify, state

API = "https://api.yourapp.com/v1/signups"

@on_trigger
def run(event):
    key = credentials.secret("YOURAPP_API_KEY")
    rows = http.get(API, params={"since": "24h"}, headers={"Authorization": f"Bearer {key}"}).json()["data"]
    yesterday = state.get("count")
    state.set("count", len(rows))
    change = "" if yesterday is None else f" ({len(rows) - yesterday:+d} on the day before)"
    notify.slack(f"Signups in the last 24 hours: {len(rows)}{change}", channel="#metrics")
    return {"signups": len(rows)}
```

## Where each GitHub Actions cron piece goes

| In GitHub Actions cron | In ClickRuntime |
|---|---|
| Workflow with on: schedule | Automation with a schedule |
| on: repository_dispatch / workflow_dispatch | Trigger link, or “run now” from chat or the ClickRuntime dashboard |
| Steps: checkout, setup-python, pip install | Nothing: Python 3.11 with common packages, plus up to 15 pinned PyPI packages |
| Repository secrets | Secrets saved in the ClickRuntime dashboard, masked in logs |
| Cache, artifacts or a committed state file | State built into the automation |
| Actions run log | Run log with output and errors, and an email when a run fails |

## Extend it: what you can add next

Once the first job is moved, these are the changes people usually ask for next. Each is one message to your assistant, not a new service to set up.

- **Compare with the day before and only post when the number moves by more than 20%** (Memory between runs)
  Prompt: "Change my signups report so it only posts when today's number differs from yesterday's by more than 20%."
- **Post each new paid signup the moment Stripe sends the event** (Trigger links)
  Prompt: "Add a trigger link to my signups automation that Stripe calls on checkout.session.completed, and post each new paid signup to #metrics."
- **Add a one-line AI read of the trend over the last two weeks** (Built-in AI)
  Prompt: "Change my signups report so it keeps 14 days of counts and adds one sentence on the trend."
- **Append each day's number to a Google Sheet for charts** (Any app or API)
  Prompt: "Add to my signups report: append the date and count to my Signups sheet every day."
- **Split signups by plan and country in one run** (Multi-step logic)
  Prompt: "Change my signups report so it breaks the count down by plan and by country."
- **Add a weekly roll-up every Monday** (Schedules)
  Prompt: "Add to my signups report: every Monday at 9, post last week's total and the best day."

## Moving from GitHub Actions cron

### Why did my scheduled GitHub Actions workflow stop running?

GitHub turns off scheduled workflows in public repositories after 60 days without repository activity, and scheduled runs only use the workflow on the default branch. On ClickRuntime a schedule runs until you pause it.

### Why does my GitHub Actions cron run late?

GitHub says scheduled runs can be delayed during periods of high load, especially at the start of an hour. ClickRuntime runs at the scheduled time.

### Can ClickRuntime receive webhooks like repository_dispatch?

Each automation has its own trigger link that any service can call, with signature checks for Stripe, GitHub, Shopify, Typeform, Standard Webhooks and HMAC. No GitHub token is involved.

### Should I move my CI to ClickRuntime?

No. Builds, tests and deployments belong next to your code in GitHub Actions. ClickRuntime is for jobs that call APIs on a schedule or when an event arrives.

### Do I need to know how to code?

No. You describe what should happen and your AI assistant writes, tests and fixes the Python. You can read every version in the ClickRuntime dashboard.

### What does ClickRuntime cost?

The free plan includes 250 runs a month with webhooks, code and AI. Paid plans start at $9 a month for 2,000 runs, with unlimited users. A scheduled check that finds nothing new and sends nothing isn't counted.

### Will you help me move my workflows?

Yes. Email hello@clickruntime.com with what each workflows does, or the GitHub Actions code or config, and we'll help until it's running. Never send API keys or other secrets.
