An Activepieces alternative you build by describing it
Activepieces builds flows from pieces on a canvas, in the cloud or self-hosted. ClickRuntime skips the canvas: you tell your AI assistant what should happen, and it writes, tests and turns on a Python automation.
Drag pieces onto a canvashandledMap fields between stepshandledPay extra credits for AI stepshandledWait for a piece to existhandled
Why people choose ClickRuntime over Activepieces
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.
AI isn't priced per step
Built-in AI calls are part of the run. They use the workspace's monthly AI tokens, including on the free plan, not extra credits per step.
Any app with an API
No connector to wait for. If an app has an API or sends webhooks, an automation can use it.
Any logic you can describe
Automations are real code, so loops, branches, parsing and several APIs in one run are ordinary.
State and versions built in
Each automation remembers what it saw last time. Every change is a new version, and a failed deploy never replaces the working one.
Unlimited users
Plans are per workspace. Invite the whole team at no extra cost.
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
Activepieces and ClickRuntime compared
| Topic | Activepieces | ClickRuntime |
|---|---|---|
| Building | Flow builder with pieces | Describe the outcome in your AI assistant |
| Usage | Credits: 1 per run, more for AI steps | One run per execution; AI uses monthly AI tokens |
| Free plan | 1,000 credits | 250 runs a month with webhooks, code and AI |
| Paid plans | Plus $20 for 10,000 credits; Team $200 for 50,000 | From $9 a month for 2,000 runs |
| Code | Code steps in TypeScript | The whole automation is Python, with pinned PyPI packages |
| Apps | Activepieces pieces, plus HTTP | Any app with an API or webhooks |
| Hosting | Cloud or self-hosted (open source) | Hosted only |
Activepieces or ClickRuntime?
Choose Activepieces when
- You need to self-host the automation platform on your own servers.
- Your team prefers to see and edit flows visually on a canvas.
- A piece already does exactly what you need and you don't want any code at all, even code you never read.
Choose ClickRuntime when
- You'd rather describe the flow in the assistant you already use than build it.
- Flows use AI on every run and you don't want AI steps priced separately.
- The logic is awkward on a canvas: loops, parsing, several APIs, memory between runs.
Move from Activepieces in five steps
Your assistant does the rewriting, you check the result.
- Step 1Describe or screenshot the flowOpen the flow and take a screenshot, or list its trigger and steps. Start with one that runs often or uses AI.
- Step 2Ask your assistant to rebuild itConnect ClickRuntime to ChatGPT, Claude or Cursor, paste the flow steps or screenshot and say what should happen. It saves a draft you can read before anything runs.
- Step 3Save your keys in the ClickRuntime dashboardSecrets from Activepieces 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 offPoint the app's webhook at the automation's trigger link, then turn the flow off in Activepieces.
This is my Activepieces flow. Rebuild it on ClickRuntime.
- Typeform lead routerTrigger link · Ready
- Weekly AI digestMondays 9:00 · Ready
- Sheet cleanupEvery day 6:00 · Needs a key
One job, moved from Activepieces
“Rebuild this Activepieces flow on ClickRuntime: when a Typeform response arrives, classify the message as sales, support or other with AI. Sales → create a HubSpot contact. Support → post to #support in Slack.”
Where each Activepieces piece goes
| In Activepieces | In ClickRuntime |
|---|---|
| Flow | Automation |
| Schedule trigger | A schedule in plain words, in your timezone |
| Webhook / app trigger | Trigger link, with signature checks |
| Pieces | Calls to each app's API inside one script |
| Router and branches | Ordinary if statements |
| Loop on items | A for loop, counted as part of the same run |
| AI pieces | ai.generate, the built-in model |
| Connections | API keys saved as secrets, or sign-in through the app's OAuth |
Send us your flow. 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 flow
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
Pull company name and budget out of the Typeform message into HubSpot fields
“Change my Typeform lead router so it also extracts company name and budget from the message and saves them on the HubSpot contact.”
- Memory between runs
Skip repeat submissions from the same email within a week
“Change my Typeform lead router so a second submission from the same email within 7 days is ignored.”
- Schedules
A Monday summary of last week's leads by label
“Add to my Typeform lead router: every Monday at 9, email me how many sales, support and other messages came in last week.”
- Any app or API
Log every submission to a Google Sheet with its label
“Add to my Typeform lead router: add a row to my Submissions sheet with the date, email, label and message.”
- Multi-step logic
Send big-budget leads to a different channel
“Change my Typeform lead router so leads with a budget over $10,000 also go to #big-deals in Slack.”
- Trigger links
Take the same flow for a second form
“Change my Typeform lead router so it also accepts responses from our demo request form and marks which form each came from.”
Moving from Activepieces
Is ClickRuntime open source like Activepieces?
No. ClickRuntime is hosted only. If you need to self-host, Activepieces is the better fit.
How is AI charged?
AI calls in a script use the workspace's monthly AI tokens, which every plan includes, including the free plan. They aren't charged as extra credits per step.
Is there a visual builder?
No. You describe the result and your assistant writes the code. Each automation shows a plain summary of what it does, and the script is there to read.
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 flows?
Yes. Email hello@clickruntime.com with what each flows does, or the Activepieces code or config, and we'll help until it's running. Never send API keys or other secrets.