OpenSourcePicks

Open source alternatives to popular software, with live GitHub data

GitHub stats refreshed every day

Open source alternatives to IFTTT

IFTTT links apps and smart devices with simple 'if this, then that' Applets. These open source tools handle the same kind of event-driven automations on hardware you control, from a Raspberry Pi to a server.

2 alternatives, sorted by GitHub stars as of 21 October 2026. Reviewed .

  1. Huginn

    Self-hosted agents that watch the web, create events and act on them for you

    50.1k starsMITLast commit Self-hosted

  2. Node-RED

    Low-code flow editor for event-driven automations, from home automation to API glue

    23.8k starsApache-2.0Last commit Self-hosted

What IFTTT does

IFTTT, short for “if this, then that”, connects apps and devices with Applets. An Applet waits for a trigger, such as a new photo, a location change, a weather forecast or a smart-home sensor, and then runs an action in another service. IFTTT says more than 1,000 brands and services are connected, and many people use it through its mobile app to link smart-home devices with personal productivity tools.

Why people look for an alternative

  • Few Applets on the free plan. The free plan allows two Applets at standard speed. Pro raises that to 20 and adds faster runs, multi-action Applets and webhooks. Filters, queries, AI services and unlimited Applets are reserved for Pro+.
  • Conditional logic costs extra. Anything beyond a straight trigger-to-action rule, such as filter code or conditions, needs the top plan.
  • Cloud dependency. Every Applet runs on IFTTT’s servers, which its privacy policy says are hosted and operated in the United States. A home automation that only links two devices on your own network still has to go through the internet and depends on the service being available.
  • Integrations you cannot fix. You depend on IFTTT and its partners to keep each service connection working.

IFTTT does let you export your data from your profile, which helps with record-keeping, but Applets cannot be imported into other tools.

What to compare in an alternative

  1. Device and service support. MQTT, local HTTP APIs, smart-home hubs, and the web services you use.
  2. Logic. Conditions, multiple actions, delays and scheduled digests without paying per Applet.
  3. Where it runs. On a small device at home or on a server, and whether it keeps working without the internet for local devices.
  4. Maintenance. Updates, backups and securing the editor if it is reachable from outside your network.

Which one to choose

Node-RED is the closest match for smart-home and device automations. It runs on a Raspberry Pi, speaks MQTT and HTTP out of the box, has thousands of community nodes and is Apache-2.0 with no paid edition. Remember that its editor needs a password set before you expose it. Huginn is a better fit for web-based IFTTT recipes: watching websites, RSS feeds, weather and inboxes, then sending emails, chat messages or digests. It is MIT-licensed and runs with Docker. If your Applets mostly connect business SaaS apps, a Zapier-style builder such as Activepieces will have more ready-made integrations. The workflow automation guide compares them all.

IFTTT is a product of IFTTT, Inc.. OpenSourcePicks is not affiliated with IFTTT, Inc. or with the projects listed. More tools in Workflow Automation.