# Assistant scheduled tasks or ClickRuntime: which one for the job

Source: https://clickruntime.com/alternatives/chatgpt-claude-scheduled-tasks

> ChatGPT, Claude and Gemini can each run a prompt on a schedule and give you the answer. That's ideal for a briefing you read in the chat. When the job has to call your APIs with your keys, remember what it did last time, react to webhooks or post to Slack, your assistant can set it up on ClickRuntime instead.

## What ClickRuntime adds to your assistant's own tasks

- **Memory between runs.** Each automation keeps state, so it can act only on new items and alert only when something changed.
- **Your keys, kept out of the chat.** API keys are saved in the ClickRuntime dashboard and read by the script when it runs. The assistant never sees them.
- **Results outside the chat.** Email, Slack, a Google Sheet, a CRM, any API. Nobody has to open a conversation to see the result.
- **Webhooks, not just schedules.** A trigger link starts a run when Stripe, GitHub or a form sends an event.
- **Code that does the same thing every time.** A script gives the same result for the same input. Use AI inside it only where judgement on text helps.
- **Works from every assistant.** Set it up from ChatGPT, Claude, Cursor, Gemini CLI or any MCP client, and change it from another.

## Assistant scheduled tasks and ClickRuntime compared

|  | Assistant scheduled tasks | ClickRuntime |
|---|---|---|
| What runs | A prompt, answered by the assistant's model | A Python script, with AI where you ask for it |
| Where results go | The chat, plus the assistant's notifications | Email, Slack, Sheets, any app with an API |
| Memory between runs | Each run starts from the prompt | State and counters kept with the automation |
| Your API keys | Not built for keeping keys | Saved in the ClickRuntime dashboard, masked in logs |
| Webhooks | Schedules only (Claude Code cloud tasks, an assistant feature, also take API and GitHub triggers) | Trigger link for any service, with signature checks |
| How often | Depends on the assistant and plan; Claude Code cloud tasks no faster than hourly | Every 5 minutes or slower |
| How many | A limit on active tasks per plan | No cap on automations; plans count runs |
| Who can use it | The person who made the task | Everyone in the workspace, unlimited users |

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

## Assistant scheduled tasks or ClickRuntime?

### Choose Assistant scheduled tasks when

- You want to read the answer in the chat: a morning briefing, a research summary, a reminder.
- The task is open-ended and benefits from the model browsing or reasoning fresh each time.
- It needs your local files or apps, which the Claude assistant's local scheduled tasks can open while your computer is on.

### Choose ClickRuntime when

- The result has to land somewhere else: Slack, email, a sheet, a CRM.
- It needs your API keys, or must remember what it already handled.
- Something outside should start it: a payment, a form, a GitHub event.
- You need it every 5 or 15 minutes, or the same exact steps every time.

## Move from Assistant scheduled tasks

1. **List your scheduled tasks.** Open the tasks or scheduled actions list in your assistant and copy each prompt and schedule.
2. **Ask your assistant which to move.** With ClickRuntime connected, paste the list and ask which need memory, keys, webhooks or delivery outside the chat. Those become draft automations you read before anything runs.
3. **Save your keys in the ClickRuntime dashboard.** Secrets from the chat 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 or pause the old scheduled task once the automation has run a few times.

## One job, moved from Assistant scheduled tasks

Before: A scheduled task in the assistant

```text
Every weekday at 8:00:
"Check our signups dashboard and tell me how many people signed up yesterday,
compared with the day before."

→ The answer appears in the chat. The task can't log in to your API,
  doesn't remember yesterday's number, and can't post to Slack.
```

After, the prompt: "Create a ClickRuntime automation: 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 Assistant scheduled tasks piece goes

| In Assistant scheduled tasks | In ClickRuntime |
|---|---|
| Scheduled task prompt | An automation's script, written by your assistant from the prompt |
| Task schedule | A schedule in plain words, in your timezone |
| Answer in the chat | Email, Slack or any app's API |
| Starting fresh every run | State kept between runs |
| Editing the task | Asking any connected assistant to change the automation |

## 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.

- **Post the signups number only when it moves by more than 20%** (Memory between runs)
  Prompt: "Change my signups report so it only posts when the number differs from the day before by more than 20%."
- **Announce each new paying customer as Stripe reports it** (Trigger links)
  Prompt: "Add a trigger link automation that Stripe calls on checkout.session.completed and posts the plan and country to #metrics."
- **Have AI write the one-line takeaway, while the numbers come from code** (Built-in AI)
  Prompt: "Change my signups report to add one sentence on what stands out, without changing how the numbers are counted."
- **Keep the numbers in a Google Sheet for a chart** (Any app or API)
  Prompt: "Add to my signups report: append the date and number to my Signups sheet each day."
- **Combine signups, revenue and churn in one morning post** (Multi-step logic)
  Prompt: "Change my signups report to also include yesterday's Stripe revenue and cancellations in the same post."
- **Check the signups API every 15 minutes during a launch** (Schedules)
  Prompt: "Add to my signups report: during launch week, post a running count every 15 minutes from 9:00 to 18:00."

## Moving from Assistant scheduled tasks

### Can ChatGPT run a task on a schedule?

Yes. ChatGPT's scheduled tasks re-run a prompt and give you the answer, with a limit on active tasks per plan. For jobs that need your API keys, memory between runs, webhooks or Slack, ask ChatGPT or another assistant to set them up on ClickRuntime.

### Does Claude have scheduled tasks?

Yes. Claude Cowork has scheduled tasks on paid plans, and Claude Code has cloud scheduled tasks in research preview that run no faster than hourly. ClickRuntime is for jobs that need your keys, memory, webhooks or delivery outside the chat, set up from Claude or another assistant.

### Can I use both?

Yes. Many people keep briefings as assistant tasks and move the jobs that touch other systems to ClickRuntime. Your assistant can set up and check ClickRuntime automations from the same chat.

### Does ClickRuntime use AI on every run?

Only where the script calls it. Counting, comparing and posting are plain code; the built-in AI is used for summarising or classifying text, including on the free plan.

### 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 tasks?

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