IFTTT

YES

Replaceable in one session with an AI coding agent.

Simple automations between consumer services: if something happens here, do that there. Aimed at smart-home devices and social accounts rather than at business systems.

Promptfree, for everyone, and the only version there is

Build the automations whose services have real APIs. Keep the rest.

SORT THEM FIRST
- Anything with a documented API: build it
- Anything that is a consumer device talking to a manufacturer cloud: keep paying, or move the device to a local protocol

STACK
- A small Node worker on a machine that is always on, SQLite for state

TRIGGERS
- Webhook: one signed endpoint per automation, HMAC verified before anything happens
- Schedule: a cron expression
- Poll: a stored cursor per source so nothing is handled twice

ACTIONS
- Plain typed functions, one per service
- Timeout, retry with backoff and an idempotency key on every outbound call

FOR THE HOME DEVICES
- Home Assistant speaks local protocols directly and removes the manufacturer cloud entirely
- That is a bigger change than an automation, and usually the right one

Include the trigger router, the run log and one example automation.

What you lose

Integrations with consumer hardware — lights, plugs, doorbells — that often have no public API at all
A mobile app with location and phone triggers you cannot reproduce from a server
Partnerships that keep those connections alive as each manufacturer changes its cloud

If you would rather not build

A cron job and a script, for two automations

The escape hatch

open source · no votes, no paid placement

Home Assistant

Local control of smart-home devices, with automations that need no cloud.

home-assistant/corefree · open source

n8n

Workflow automation you host, with a large integration library.

n8n-io/n8nfree · open source

Why this verdict

our own opinion · changed only by a person

72/100

Verdict yes at 72 for anything with an API. Consumer hardware is the exception, and Home Assistant is the better answer there than a home-made bridge.

History

tracked since 10 Aug 2026 · nothing is ever overwritten

Interest · last 30 days

Nothing recorded yet. This chart fills in once the page has visitors, votes or prompt copies — it will not draw a flat line to look busy.

Questions about IFTTT

answered from the record above

Is IFTTT free?

No — the plan we track is $3.49 a month. Pro at around $3.49/month billed monthly, cheaper annually; Pro+ costs more and lifts the applet limit.

Can you replace IFTTT by building your own?

YES. Replaceable in one session with an AI coding agent. Replacement score 72 out of 100, build time one session. Read what you lose before you decide.

How much does IFTTT cost?

$3.49 a month on Pro — $41.88 a year. Recorded 10 Aug 2026.

What do you lose by replacing IFTTT?

Integrations with consumer hardware — lights, plugs, doorbells — that often have no public API at all; A mobile app with location and phone triggers you cannot reproduce from a server; Partnerships that keep those connections alive as each manufacturer changes its cloud. If any of those carry weight for you, keep paying.

Is there an open-source alternative to IFTTT?

Yes: Home Assistant, n8n. The prompt on this page is for when you want it your way instead.

Related entries

same category first, most replaced first

All 11 in Automation & notifications

Coming soon

Every week, something stops being worth paying for.

New verdicts, prices that moved, entries added. One email a week. Unsubscribe in one click.

free forever · no tracking pixel · every prompt stays free on the site