# A Trigger.dev alternative for jobs that don't need a codebase

Source: https://clickruntime.com/alternatives/trigger-dev

> Trigger.dev is a background-job framework for TypeScript apps: tasks live in your repo and deploy with it. ClickRuntime is for jobs that stand on their own, a report, a sync, a webhook handler, written in Python by your AI assistant and running without a project to deploy.

## When ClickRuntime fits better than Trigger.dev

- **No project needed.** An automation is one script with its schedule or trigger link. Nothing to add to a repo, build or deploy.
- **Webhooks built in.** Each automation has its own trigger link with signature checks for Stripe, GitHub, Shopify, Typeform and HMAC.
- **Built from the assistant you already use.** Ask in ChatGPT, Claude, Cursor or any MCP client. It writes the automation, tests it and fixes it.
- **Python first.** Scripts are Python 3.11 with common packages available and up to 15 pinned PyPI packages.
- **State built in.** Each automation remembers what it saw last time, so it can act only on new items.
- **AI included.** Automations can classify, summarise and extract with a built-in AI model, no API key needed, including on the free plan.

## Trigger.dev and ClickRuntime compared

|  | Trigger.dev | ClickRuntime |
|---|---|---|
| Made for | Background jobs inside a TypeScript app | Standalone jobs on a schedule or webhook |
| Language | TypeScript; Python scripts via a build extension | Python 3.11 |
| Schedules | Cron with timezone. On Free, at most once an hour | Every 5 minutes or slower on every plan, in your timezone |
| Webhooks | Trigger tasks from your own endpoint or code | A trigger link per automation, with signature checks |
| Run length | No maximum duration | Short jobs: a time limit per run |
| Changes | Edit code and deploy | Ask your assistant; each change is a new version |
| Hosting | Cloud, or self-host (Apache-2.0) | Hosted only |
| Free plan | $5 of usage a month, 10 schedules | 250 runs a month with webhooks, code and AI |
| Paid plans | Hobby $10, Pro $50 a month | From $9 a month for 2,000 runs, unlimited users |

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

## Trigger.dev or ClickRuntime?

### Choose Trigger.dev when

- The job is part of your TypeScript product: triggered from app code, sharing its types, deployed with it.
- Runs are long (minutes to hours) or need retries, queues and concurrency controls across many runs.
- You want to self-host the job platform.

### Choose ClickRuntime when

- The job stands alone: a report, sync, monitor or webhook handler that calls APIs.
- You'd rather describe it to an assistant than add an SDK and deploy.
- People outside engineering should be able to set up or change jobs.

## Move from Trigger.dev

1. **Pick standalone tasks.** Move scheduled and webhook tasks that only call APIs. Keep tasks your app triggers from its own code, or long-running ones, where they are.
2. **Ask your assistant to rebuild it.** Connect ClickRuntime to ChatGPT, Claude or Cursor, paste the task file 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 Trigger.dev 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.** Remove the task from your project and deploy, or delete its schedule in Trigger.dev.

## One job, moved from Trigger.dev

Before: trigger/daily-signups.ts

```typescript
import { schedules } from "@trigger.dev/sdk";

export const dailySignups = schedules.task({
  id: "daily-signups",
  cron: { pattern: "0 8 * * 1-5", timezone: "Europe/London" },
  run: async () => {
    const res = await fetch("https://api.yourapp.com/v1/signups?since=24h", {
      headers: { Authorization: `Bearer ${process.env.YOURAPP_API_KEY}` },
    });
    const { data } = await res.json();
    await fetch(process.env.SLACK_WEBHOOK_URL!, { method: "POST", body: JSON.stringify({ text: `Signups: ${data.length}` }) });
  },
});
```

After, the prompt: "Move this Trigger.dev task 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 Trigger.dev piece goes

| In Trigger.dev | In ClickRuntime |
|---|---|
| schedules.task with cron | Automation with a schedule |
| task() triggered from your code or endpoint | Automation with a trigger link |
| Environment variables | Secrets saved in the ClickRuntime dashboard |
| npm dependencies | Pinned PyPI packages |
| Run dashboard | Run log with output and errors, secrets masked |

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

- **Label each new signup's use case from the sign-up form's free-text answer** (Built-in AI)
  Prompt: "Change my signups report so it groups yesterday's signups by what they said they'd use us for."
- **Remember which signups were already posted, so none repeat** (Memory between runs)
  Prompt: "Change my signups automation so it posts each new signup once, with name and plan, and never repeats one."
- **React to GitHub releases with a changelog post** (Trigger links)
  Prompt: "Add an automation with a trigger link that GitHub calls on release published, and posts the release notes to #product."
- **Send the daily number to a Notion page as well** (Any app or API)
  Prompt: "Add to my signups report: append each day's number to my Metrics page in Notion."
- **Flag days with zero signups as a likely tracking problem** (Multi-step logic)
  Prompt: "Change my signups report so a day with zero signups sends me an email saying tracking may be broken."
- **Move the report earlier on Mondays** (Schedules)
  Prompt: "Change my signups report to run at 7:30 on Mondays and 8:00 the other weekdays."

## Moving from Trigger.dev

### Is ClickRuntime a Trigger.dev replacement?

For standalone scheduled and webhook jobs, yes. For background jobs that are part of a TypeScript application, long runs, or self-hosting, Trigger.dev is the better fit.

### Can I write TypeScript?

No. Scripts are Python. Your assistant rewrites TypeScript logic in Python as part of the move.

### How often can a schedule run?

Every 5 minutes or slower, on every plan including 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 Trigger.dev code or config, and we'll help until it's running. Never send API keys or other secrets.
