Skip to content
ClickRuntime

Make alternative

A Make alternative where loops don't cost extra

Make uses a credit for each module action, and again for every item a scenario iterates over. ClickRuntime counts one run per execution, however many items it handles. Describe the scenario to your AI assistant instead of building it on a canvas.
Add to ChatGPTAdd to Claude
Get help moving from Make
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client
Daily order sync, 200 orders1 run
1Get yesterday's orders+1
2Iterate over 200 orders+200
3Look up each customer+200
4Update each row in Sheets+200

Make credits

601 credits

ClickRuntime

1 run

Why ClickRuntime

Why people move from Make

  • Loops are free

    Handling 10 items or 1,000 in one execution is still one run. You don't have to batch work to save credits.

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

  • 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 app with an API

    No connector to wait for. If an app has an API or sends webhooks, an automation can use it.

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

  • AI included

    Automations can classify, summarise and extract with a built-in AI model, no API key needed, including on the free plan.

No workflow builder

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.
The usual wayStep 9 failed
Shopify trigger
Filter > $500
CRM: find
Router
Path A: new
Path B: existing
Formatter
AI: summarise
Text parser
Slack: post
CRM: add note
Error handler
Set variable
Delay 2 min
14 steps3 branches6 field mappings
With ClickRuntimeLive
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.
Large order routingLive
When
Shopify · new order (webhook)
Uses
Shopify, HubSpot, Slack, AI

Side by side

Make and ClickRuntime compared

Make compared with ClickRuntime
MakeClickRuntime
UsageA credit for each module action, including each item an iterator processesOne run per execution, however many items it handles
BuildingDrag modules onto a canvas and map fields between themDescribe the outcome in your AI assistant
LogicRouters, iterators, aggregators and filtersAny logic in Python: loops, branches, parsing, calculations
AppsMake's apps, plus HTTP and custom appsAny app with an API or webhooks
Free plan1,000 credits a month, 15-minute minimum interval250 runs a month with webhooks, code and AI
StorageData stores, sized by your creditsState and counters built into every automation
UsersTeams and roles on the paid planUnlimited users on every plan
Running outScenarios stop and webhooks queue until credits are addedRuns pause until next month or a plan change. Nothing is deleted

See ClickRuntime pricing

Pricing

Credits add up with every item

Make counts each module action, so a scenario that iterates over 200 records and does three things with each uses about 600 credits a run. On ClickRuntime that's one run.

The free plan includes 250 runs a month. Paid plans start at $9 a month for 2,000 runs, with unlimited users.

Per month, for a daily job that handles 200 records

Make≈ 18,000 credits
Annual$32.40
ClickRuntime30 runs · free plan
AnnualFree

Make's price is estimated from its annual pricing: $9 for 5,000 credits, then $1.80 per 1,000. A short scenario with no loops uses few credits and can cost less on Make.

Migration

Move from Make in five steps

Your assistant does the rewriting, you check the result.

  1. Export the scenario blueprint

    In Make, open the scenario and export its blueprint. It's a JSON file with every module and setting.

  2. Ask your assistant to rebuild it

    Connect ClickRuntime to ChatGPT, Claude or Cursor, attach the blueprint and ask it to rebuild the scenario. It saves a draft you can read before anything runs.

  3. Add your keys

    Accounts connected in Make 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.

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

  5. Switch over

    Where an app sends webhooks, replace the Make URL with the automation's trigger link. Then turn off the scenario in Make.

{ } order-sync.blueprint.json
This is my Make scenario. Rebuild it on ClickRuntime.
It gets yesterday's orders and updates a sheet for each one. Here it is as one automation.
Daily order syncEvery day 6:00Ready
Form leads → CRMTrigger linkReady
Invoice reminders1st of monthNeeds a key

Translation

Where each Make piece goes

Make features and their ClickRuntime equivalents
In MakeIn ClickRuntime
ScenarioAutomation
ScheduleA schedule in plain words, in your timezone
Webhook moduleTrigger link, with signature checks for Stripe, GitHub, Shopify, Typeform and HMAC
ModulesCalls to each app's API inside one script
Routers and filtersOrdinary if statements
Iterators and aggregatorsA for loop and a list
Data storesState built into every automation
ConnectionsAPI keys saved as secrets, or sign-in through the app's OAuth app
Execution historyRun log with output and errors, secrets masked

Migration help

Send us your scenario blueprints. 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.

Email hello@clickruntime.com

Moving from Make

Is ClickRuntime cheaper than Make?
For scenarios that loop over many items or have many modules, usually, because ClickRuntime counts one run per execution. For a short scenario with few modules and no loops, Make's per-credit price can be lower.
Can I import my Make scenarios?
Yes. Export the scenario's blueprint, attach the JSON in ChatGPT, Claude or Cursor with ClickRuntime connected, and ask your assistant to rebuild it. It becomes a draft you review before it runs.
Is there a visual editor?
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 if you want to read it.
Do I need to know how to code?
No. You describe what should happen and your AI assistant writes, tests and fixes the code. You can read every version in the ClickRuntime dashboard if you want to.
Which apps can I use?
Any app with an API or webhooks. Save the app's API key as a secret in the ClickRuntime dashboard, or add the app's OAuth details and sign in. Public web pages and feeds work too.
Can my team use it?
Yes. Plans are per workspace with unlimited users, and everyone shares the workspace's connections and monthly runs.
Will you help me move my scenarios?
Yes. Email hello@clickruntime.com with what each scenario does, or its export from Make, and we'll help until it's running. Never send API keys or other secrets.

Keep exploring

Move your first Make automation today

Free plan. No credit card.

Add to ChatGPTAdd to Claude