IFTTT review

IFTTT is a hosted automation service, not a library, CLI or server you install in your own stack. Its core unit is an Applet: a trigger from one connected service starts an action in another. Users can enable ready-made Applets or build their own through IFTTT's app and website.

In a typical stack, IFTTT sits between SaaS apps, consumer devices and AI services. It handles the connections and runs the automation in its hosted environment; your own application does not need to run a workflow engine. The service lists more than 1,000 integrations, including Slack, Gmail and Philips Hue, and adds webpage-change triggers for things such as prices, listings and job postings.

That model suits lightweight, cross-service tasks where a visual trigger-and-action flow is enough. IFTTT also offers AI agents that query, filter and act across connected services, plus AI app connections for summarizing, translating and drafting. It is less suited to teams that need to own the runtime or build complex workflows in application code.

The integration surface IFTTT presents is its Applet builder, connected service integrations, an integration called Webhooks, and the IFTTT.ai MCP server. The homepage describes MCP as a way to connect AI tools to IFTTT services and automations. It also describes Applets as trigger-and-action workflows and says they can link two or more apps.

For AI workflows, IFTTT lists connections to ChatGPT, Claude and Gemini, as well as custom-trained agents. Agents can query, filter and take action across connected services; AI app connections can summarize, translate and draft content. These are hosted automation paths rather than a documented code-first runtime in the product overview.

Before adopting IFTTT as a code dependency, confirm supported SDKs, languages, API contracts and authentication flows in the vendor's docs. The product is easiest to integrate by selecting supported services and configuring Applets; MCP is the named protocol surface for connecting AI tools. The homepage also promotes ready-made Applets, which can reduce setup for common workflows but may not match application-specific logic.

The Free plan costs $0 and includes 1,000 credits per month, unlimited Applets, all services and integrations, and all features unlocked. That is enough to try automations, but the credit allowance is the main usage ceiling. The pricing page does not itemize the cost of extra credits, so ask IFTTT how overages are handled before relying on a workflow at higher volume.

Starter is $2.09 per month and lists 5,000 credits, Applet speeds every 15 minutes and basic support with an 18-hour reply time; its annual total is $25.08. Pro is $5.49 per month, or $65.88 billed annually, for 20,000 credits, speeds every five minutes and prioritized support with a 12-hour reply time. Pro+ is $13.99 per month, or $167.88 billed annually, with 100,000 credits, speeds every five minutes, multiple accounts per service and dedicated support with a six-hour reply time. Enterprise has custom credits and support terms, with pricing by contacting sales. Annual billing saves about 30%, according to the pricing page.

IFTTT is presented as a hosted service, not a self-hosted server. Its homepage does not present an open-source licence, so teams should treat it as a hosted, proprietary service unless IFTTT provides different terms. That means the automation runtime and service connections remain under the vendor's control.

The integration model also creates some lock-in: Applets depend on IFTTT's connectors and the APIs of the services they link. If a connector is changed or discontinued, a workflow may need to be redesigned around another integration path. Reddit users report that some integrations, including Alexa, have been discontinued.

Before using IFTTT for critical workflows, ask whether Applet definitions, configuration and run history can be exported, and what happens to connected-service credentials if you leave. Treat a move to another platform as a potential rebuild rather than assuming Applets can be imported. Developers who need a self-hosted runtime should evaluate that requirement before adopting IFTTT.

The published plans set credit allowances and Applet speed tiers, but they do not establish a general API rate limit or a reliability guarantee for automation execution. Starter lists speeds every 15 minutes; Pro and Pro+ list speeds every five minutes. Those intervals matter for time-sensitive workflows, and the credit allowance matters as automation volume grows. Confirm what consumes credits and how a workflow behaves when its allowance is reached.

The service runs in IFTTT's hosted environment, so workflows also depend on IFTTT and each connected service being available. Reddit users report slow responses, discontinued integrations and a preference for local automation in Home Assistant. Those are user reports, not service-level measurements, but they flag real dependencies to test against your own requirements.

Before putting a workflow on a production path, check service permissions, handling of failed actions, retry behavior, logging, data retention and the vendor's security and compliance terms. The support reply times listed by plan are targets to consider, not a substitute for an operational fallback. Keep critical actions independently observable and avoid making IFTTT the only path for a high-impact task.