A Trigger.dev alternative for jobs that don't need a codebase
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.
Add an SDK and config to a projecthandledDeploy to change a schedulehandledWrite a webhook endpoint to trigger taskshandledKeep the CLI and SDK versions in stephandled
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.
A 14-step workflow becomes one sentence
Workflow builders make you place every trigger, filter, branch and formatter yourself, then fix it when one breaks. Here you describe the result and your assistant writes the code.
- 01 Shopify trigger
- 02 Filter > $500
- 03 CRM: find
- 04 Router
- 05 Path A: new
- 06 Path B: existing
- 07 Formatter
- 08 AI: summarise
- 09 Text parserfailed
- 10 Slack: post
- 11 CRM: add note
- 12 Error handler
- 13 Set variable
- 14 Delay 2 min
“When a Shopify order over $500 comes in, check the customer in HubSpot. If they're new, post to #sales with an AI summary of the order. Otherwise add a note to their contact.”
Here's the automation. It runs on each new order.
- When
- Shopify · new order (webhook)
- Uses
- Shopify, HubSpot, Slack and AI
Trigger.dev and ClickRuntime compared
| Topic | 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 |
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 in five steps
Your assistant does the rewriting, you check the result.
- Step 1Pick standalone tasksMove scheduled and webhook tasks that only call APIs. Keep tasks your app triggers from its own code, or long-running ones, where they are.
- Step 2Ask your assistant to rebuild itConnect 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.
- Step 3Save your keys in the ClickRuntime dashboardSecrets 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.
- Step 4Test itYour 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.
- Step 5Switch the old one offRemove the task from your project and deploy, or delete its schedule in Trigger.dev.
This is a Trigger.dev scheduled task. Rebuild it on ClickRuntime.
- Daily signupsWeekdays 8:00 · Ready
- GitHub issue triageTrigger link · Ready
- Video transcodingStays on Trigger.dev · Needs a key
One job, moved from Trigger.dev
“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.”
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 |
Send us your task files. We'll help you move it.
Email it with a line about what each one does. A person reads it, tells you how it maps to ClickRuntime, and helps until your automations are running.
Email your task files
Leave out API keys and other secrets.
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.
- Built-in AI
Label each new signup's use case from the sign-up form's free-text answer
“Change my signups report so it groups yesterday's signups by what they said they'd use us for.”
- Memory between runs
Remember which signups were already posted, so none repeat
“Change my signups automation so it posts each new signup once, with name and plan, and never repeats one.”
- Trigger links
React to GitHub releases with a changelog post
“Add an automation with a trigger link that GitHub calls on release published, and posts the release notes to #product.”
- Any app or API
Send the daily number to a Notion page as well
“Add to my signups report: append each day's number to my Metrics page in Notion.”
- Multi-step logic
Flag days with zero signups as a likely tracking problem
“Change my signups report so a day with zero signups sends me an email saying tracking may be broken.”
- Schedules
Move the report earlier on Mondays
“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.