n8n alternative
An n8n alternative with nothing to host and no nodes to wire
Why ClickRuntime
Why people move from n8n
Nothing to host
No server, database, updates or scaling. Automations run on our servers on a schedule or when an event arrives.
Python with real packages
Each automation is a Python script that can use pinned PyPI packages, not a Code node with a short list of allowed modules.
Built from the assistant you already use
Ask in ChatGPT, Claude, Cursor or any MCP client. It already has your context, writes the automation, tests it and fixes it.
Any logic you can describe
Automations are real code, so loops, branches, parsing, calculations and several APIs in one run are ordinary. You think in outcomes, not nodes.
State and versions built in
Each automation remembers what it saw last time. Every change is a new version, and a deploy that fails never replaces the working one.
Unlimited users
Plans are per workspace. Invite the whole team at no extra cost.
No workflow builder
A 14-step workflow becomes one sentence
- When
- Shopify · new order (webhook)
- Uses
- Shopify, HubSpot, Slack, AI
Side by side
n8n and ClickRuntime compared
| n8n | ClickRuntime | |
|---|---|---|
| Hosting | Self-host and maintain it, or use n8n Cloud | Nothing to host |
| Building | Connect nodes on a canvas | Describe the outcome in your AI assistant |
| Code | Code node. On Cloud, Python can't import libraries and JavaScript has only crypto and moment | Whole Python scripts with pinned PyPI packages |
| Free option | Self-hosted Community Edition, or a Cloud trial | Free plan with 250 runs a month, nothing to host |
| Versions | Git version control on Business and Enterprise | Version history built in on every plan |
| Users | Shared projects by plan | Unlimited users on every plan |
| AI | AI nodes with your own model provider | Built-in AI model, no API key needed, on every plan |
Migration
Move from n8n in five steps
Download the workflow JSON
In n8n, open the workflow and download it as JSON. It contains every node and connection, without credential values.
Ask your assistant to rebuild it
Connect ClickRuntime to ChatGPT, Claude or Cursor, attach the JSON and ask it to rebuild the workflow. Code nodes are rewritten in Python. It saves a draft you can read before anything runs.
Add your keys
Accounts connected in n8n don't move over. Save each app's API key as a secret in the ClickRuntime dashboard, or sign in through the app's own OAuth app. Keys never go into the chat.
Test it
Your assistant turns each automation on, sends a test event or runs it once, and fixes it until the run succeeds. You can run both side by side for a while.
Switch over
Where an app sends webhooks, replace the n8n URL with the automation's trigger link. Then turn off the workflow in n8n.
This is my n8n workflow. Rebuild it on ClickRuntime.
Translation
Where each n8n piece goes
| In n8n | In ClickRuntime | |
|---|---|---|
| Workflow | Automation | |
| Schedule Trigger | A schedule in plain words, in your timezone | |
| Webhook node | Trigger link, with signature checks for Stripe, GitHub, Shopify, Typeform and HMAC | |
| App nodes and HTTP Request | Calls to each app's API inside one script | |
| IF, Switch and Merge | Ordinary Python | |
| Code node (JavaScript or Python) | The script itself, in Python | |
| Static data | State built into every automation | |
| Credentials | API keys saved as secrets, or sign-in through the app's OAuth app | |
| Error workflow | An email when a run fails, and a run log to ask your assistant about | |
| Executions | Run log with output and errors, secrets masked |
Migration help
Send us your workflow JSON. 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. Leave out API keys and other secrets.
Moving from n8n
Can I import my n8n workflows?
Can I self-host ClickRuntime?
Can I use Python packages?
Do I need to know how to code?
Which apps can I use?
Can my team use it?
Will you help me move my workflows?
Keep exploring