An IFTTT alternative for the applets that outgrew “if this, then that”
IFTTT is great at connecting one thing to another, especially phones and smart-home devices. When you need to compare with last time, loop over items, call any API or use AI on the text, describe it to your AI assistant and ClickRuntime runs it.
Squeeze logic into one trigger and one actionhandledWait up to an hour for a check on the free planhandledWork around missing serviceshandledLose track of what ran lasthandled
Why people move applets to ClickRuntime
Any logic you can describe
Automations are real code, so loops, branches, parsing and several APIs in one run are ordinary.
Remembers what happened
Each automation keeps its own state, so it acts only on new items and can compare with last time.
Any app with an API
No connector to wait for. If an app has an API or sends webhooks, an automation can use it.
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.
Checks every 5 minutes on every plan
The schedule interval doesn't depend on the plan. Checks that find nothing new aren't counted.
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
IFTTT and ClickRuntime compared
| Topic | IFTTT | ClickRuntime |
|---|---|---|
| Made for | Simple connections between apps, phones and smart devices | Automations with logic, memory and any API |
| Building | Pick a trigger and actions in the app | Describe the outcome in your AI assistant |
| How often it checks | Free hourly, Starter every 15 minutes, Pro and Pro+ every 5 minutes | Every 5 minutes or slower, on every plan |
| Usage | Credits per month | Runs per month; checks that find nothing aren't counted |
| Plans | Free (1,000 credits) to Pro+ ($13.99 a month billed yearly, 100,000 credits) | Free (250 runs) and paid from $9 a month for 2,000 runs |
| Webhooks | On every plan | A trigger link per automation, with signature checks |
| Logic | Filters and multiple actions | Any logic in Python |
| Phones and smart home | Native services for devices, location and phone events | Only through a device's cloud API |
IFTTT or ClickRuntime?
Choose IFTTT when
- The trigger is your phone, location or a smart-home device. IFTTT has native services for those; ClickRuntime doesn't.
- One trigger to one action is all you need, and an existing applet already does it.
- You want a mobile app to switch automations on and off.
Choose ClickRuntime when
- You need logic: comparisons with last time, loops over items, conditions across several apps.
- The app you need has an API but no IFTTT service.
- You want AI to read, classify or summarise text inside the automation.
Move from IFTTT in five steps
Your assistant does the rewriting, you check the result.
- Step 1Pick the applets that need moreKeep phone, location and smart-home applets on IFTTT. Move the ones where you want logic, memory, AI or an app IFTTT doesn't have.
- Step 2Ask your assistant to rebuild itConnect ClickRuntime to ChatGPT, Claude or Cursor, paste the applet's trigger and action and say what should happen. It saves a draft you can read before anything runs.
- Step 3Save your keys in the ClickRuntime dashboardSecrets from IFTTT 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 offTurn the applet off in IFTTT once the automation has run a few times.
This is my IFTTT applet. Rebuild it on ClickRuntime and add a summary.
- Blog feed to #newsEvery 15 minutes · Ready
- Weekly reading digestFridays 16:00 · Ready
- Lights on at sunsetStays on IFTTT · Needs a key
One job, moved from IFTTT
“Rebuild my IFTTT applet on ClickRuntime: every 15 minutes, check https://blog.example.com/feed and post new items to #news in Slack, with a one-line AI summary of each. Never post the same item twice.”
Where each IFTTT piece goes
| In IFTTT | In ClickRuntime |
|---|---|
| Applet | Automation |
| Trigger (if this) | A schedule that checks for new items, or a trigger link |
| Action (then that) | Calls to the app's API inside the script |
| Filter code | Ordinary Python |
| Webhooks service | Trigger link, with signature checks |
| Connected services | OAuth connections or API keys saved in the ClickRuntime dashboard |
Send us your applets. 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 applets
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
Only post feed items about the topics you care about
“Change my blog feed automation so it only posts items about pricing or product launches, judged from the title and summary.”
- Multi-step logic
Follow several feeds and tag which one each item came from
“Change my blog feed automation to also follow two more feeds and start each post with the site's name.”
- Schedules
A Friday digest instead of individual posts
“Change my blog feed automation so it collects items during the week and posts one digest on Friday at 16:00.”
- Any app or API
Save each item to a Notion reading list
“Add to my blog feed automation: add each new item to my Reading list database in Notion.”
- Memory between runs
Count posts per site per month
“Change my blog feed automation to count items per feed each month and email me the totals on the 1st.”
- Trigger links
Let a Typeform submission add a new feed to follow
“Add a trigger link to my blog feed automation that a Typeform form calls with a feed URL, and start following that feed.”
Moving from IFTTT
Can ClickRuntime control smart-home devices?
Only through a device's cloud API, if it has one. IFTTT's native device and phone services are the better choice for that.
How fast does it notice new items?
A schedule can check every 5 minutes on every plan. Services that send webhooks start a run the moment they call the trigger link.
Do I need IFTTT Pro for webhooks?
No, IFTTT includes webhooks on every plan. On ClickRuntime every automation can have a trigger link, including on 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 applets?
Yes. Email hello@clickruntime.com with what each applets does, or the IFTTT code or config, and we'll help until it's running. Never send API keys or other secrets.