IFTTT Review: What Works, What Breaks, and the Pricing Math

IFTTT popularized the "if this, then that" automation model over a decade ago, and it's still the tool most people picture when they think of connecting apps without code. That reputation is earned for a narrow slice of use cases and increasingly strained outside of them. Here's what the pricing, the architecture, and the actual user experience show.

What IFTTT Actually Does

The core unit is the Applet: one trigger from one service, one or more actions in another. You can build one from scratch in the composer or grab one from IFTTT's published library — connect Google Sheets to Gmail, sync Google Calendar with Todoist, or have a Philips Hue bulb flash when your Ring doorbell rings. Applets can also include "queries," which pull conditional data mid-workflow (IFTTT's own example: fetching current temperature before deciding an action).

That's the entire mental model, and it's genuinely quick to learn. Independent testing scored IFTTT's ease-of-use at the top of its cohort, with "an applet in under a minute" described as a consistent, reproducible experience that no comparable automation tool matches. For anyone who's tried to build even a two-step workflow in a more powerful tool, that speed is the whole appeal.

The catch is what that model can't do natively: no loops, no branching, no data transformation. Those come later, and only partially.

IFTTT's published tiers, per ifttt.com/plans:

IFTTT advertises a "SAVE 40%" badge on the annual toggle for both paid tiers, reflecting the drop from $4.99/mo to $2.99/mo on Pro and from $14.99/mo to $8.99/mo on Pro+ when you commit to a year up front.

A 7-day free trial applies automatically to the first Pro or Pro+ signup, and you can downgrade or cancel anytime, with paid access continuing through the end of the current billing cycle. There's also an Enterprise tier — "behavioral insights, enterprise reliability, and dedicated support" — but no price is published; it's a contact-sales arrangement.

The Free Tier Is a Trial, Not a Plan

Free gets you two active Applets, each limited to one trigger and one action (you can add a delay, but not a second action or a condition). That cap has tightened over time — from 5 to 3 to 2, per independent tracking — which suggests it could shrink further.

Two Applets is enough to test whether IFTTT fits your workflow. It is not enough to run one. An independent review calling the free tier "essentially useless for real workflows" cross-referenced sentiment from multiple sources, including the r/ifttt community, and that assessment tracks with the math: most people need more than two automations running simultaneously in daily life, let alone in a business.

What Pro and Pro+ Really Unlock

Pro's headline feature is multi-action Applets — one trigger firing several actions instead of one. It also switches some services from polling to faster "realtime" delivery and raises rate limits, plus it's required for Webhooks and Twitter/X Applets.

Pro+ adds the things that start to resemble real logic: queries and "filter code," described by the vendor as basic conditional JavaScript, plus the ability to connect multiple accounts per service and access IFTTT's AI Services. If you've ever needed an Applet to check a condition before firing — "only send this alert if it's after 6pm" — that capability lives exclusively behind Pro+'s filter code, not anywhere in the free or Pro tier.

That's a meaningful upgrade path for personal use. It's a much smaller one for business use, because filter code is still JavaScript snippets bolted onto a single-path automation, not a workflow engine with branches and error handling.

The Architectural Ceiling: Why This Isn't a Business Automation Tool

This is the finding that matters most if you're evaluating IFTTT for anything beyond personal or smart-home use. Independent scoring rated IFTTT's scalability near the bottom of its category, describing the limitation as architectural rather than volume-based — meaning no plan upgrade fixes it, because the constraint isn't how many Applets you can run, it's what a single Applet can logically do.

There's no native branching, no loops, no data transformation step, and no error-handling/fallback path if a step fails. Filter code in Pro+ adds conditional gating, but it doesn't add multi-path logic. Teams attempting real business deployments reportedly hit this ceiling within weeks, according to the same independent assessment.

"It's when you try to take IFTTT to work that the cracks start showing... your Philips Hue bulbs are thriving, but not your CRM, project management software, or any of the tools you actually use to make money." — Zapier's own comparison of IFTTT alternatives

Zapier has an obvious incentive to say that, but the architectural facts back it up independent of who's saying it.

Integration Depth: Strong on Smart Home, Thin on Business SaaS

IFTTT advertises "over 1,000 brands and services." That figure is real, but context matters: Zapier's blog puts its own catalog at 9,000+ apps, and a separate comparison cited in an independent review put IFTTT's library at roughly one-eighth the size of Zapier's. Neither number is disputed by IFTTT.

What's in the 1,000 leans heavily consumer and IoT: Google Assistant, Amazon Alexa, Philips Hue, iRobot, Withings, Blink, Smart Life, plus social platforms (Instagram, TikTok, Bluesky, X) and productivity apps (Notion, Todoist, TickTick, Google Calendar). Business software depth is comparatively thin — HubSpot isn't in the catalog at all, and the Jira integration was paused in September 2025 after an upstream API deprecation, per IFTTT's own status page.

Key takeaway — If your automations live in your house, IFTTT's catalog covers you well. If they live in your CRM, ticketing system, or team's project boards, expect gaps — and expect that a paused integration (like Jira) can happen with limited warning.

The AI Angle: What's Really There

IFTTT now markets AI features — "summarize, transform, and translate information with help from AI," plus AI-powered Applet templates tied to ChatGPT, Gemini, and Anthropic Claude, gated to Pro+. It also recently launched IFTTT MCP, which connects assistants like Claude, ChatGPT, Cursor, Microsoft Copilot, and Perplexity to search and trigger any of IFTTT's 1,000+ services on a user's behalf.

Worth being direct about what this is and isn't. IFTTT's core engine is a deterministic rule system — trigger fires, action runs — not a proprietary AI model. There's no evidence in IFTTT's own documentation or subprocessor disclosures of an embedded, IFTTT-owned AI system; the "AI" in the product is either a template wrapper around third-party models (ChatGPT, Gemini, Claude) or an MCP bridge letting external assistants act on IFTTT's behalf. Our assessment rates this partial AI capability with medium washing risk: the AI branding is real but shallow, closer to "if-then automation with an AI on-ramp" than an AI-native product.

That's not necessarily a knock — MCP support is a genuinely useful bridge for anyone already using Claude or ChatGPT who wants those assistants to flip smart-home devices or post to social accounts. Just don't buy Pro+ expecting IFTTT itself to reason about your data.

Real-World Use: What Actually Gets Automated

Two vendor-supplied case studies illustrate the range. Juan Segui, a small business owner, uses IFTTT for social media posting, email notifications, expense/invoice tracking, and project management syncing, reporting 13 hours saved per week. Violette Laurent, a content creator, automates publishing blog posts across sites and to Facebook via RSS, reporting 10 hours saved weekly.

Both are single-operator use cases built around content and personal-scale admin — exactly the profile IFTTT's architecture supports well. Neither involves a team, a CRM, or conditional branching, which lines up with where the tool's strengths actually sit.

Reliability in Practice: The Polling Delay Problem

"Instant" isn't quite accurate at any tier. Independent testing found polling delays of 1–15 minutes persisting even on paid plans, meaning time-sensitive automations — a security alert, a real-time notification — aren't reliably instant even after upgrading.

Third-party service changes compound this. One Apple App Store reviewer ("Medengineer") described a TP-Link Kasa smart plug silently dropping IFTTT support; the automation broke with no clear notice from IFTTT, and the fix was switching hardware brands entirely, to Govee. That reviewer eventually restored their subscription and rating once the cause was clear — but the debugging burden fell entirely on the user.

Key takeaway — Build in slack for 1–15 minute trigger delays regardless of plan, and check status.ifttt.com before assuming a broken Applet is your configuration's fault. Third-party API changes on the other end are common and often unannounced.

Security, Compliance, and Support Bandwidth

Third-party security profiling lists SSO support (Okta, Login with Google, Login with Microsoft) and multiple 2FA methods (SMS, email, hardware keys, TOTP, U2F), a public status page, and an active bug bounty program. Compliance certifications including SOC 2, PCI, HIPAA, GDPR, ISO 27001, and FedRAMP appear on that same third-party profile, though we'd recommend confirming current certification status directly with IFTTT before relying on it for a regulated workflow, since these weren't independently confirmed on IFTTT's own pages in our research.

One structural fact worth weighing: IFTTT's headcount is estimated at roughly 50 people, cited as a constraint on both support responsiveness and roadmap velocity. That estimate lines up with recurring support complaints below.

There's no role-based access control and no audit logs — a real gap for any team wanting more than one person touching a shared automation. Multiple people using the same workflow means sharing login credentials, which is its own security liability.

What Users Say When Things Go Wrong

IFTTT's iOS App Store rating sits high overall, with one reviewer ("FarmerBob") calling it "the root of my IoT" and praising cross-vendor interoperability. That's the ceiling of the experience when it works.

The complaints cluster around a few repeat themes. On Trustpilot specifically — a platform that skews toward complaints generally, so treat this as one data point rather than a consensus — reviewers describe billing and cancellation problems, including being charged after attempting to cancel a trial, with refunds sometimes delayed or denied. Trustpilot reviewers also describe "price locked forever" promises to early Pro subscribers that were later reversed, and report Applets or integrations (YouTube, Discord, Instagram, Blink among them) failing or firing with long delays. Support unresponsiveness is a recurring complaint on that platform too, though at least one reviewer noted that persistent follow-up eventually got a real person to fix a webhook bug, and another reported eventually receiving a refund after complaining.

Apple App Store reviews echo some of this from a different angle: one user ("Hdeanz") paid for a full year of Pro through the App Store that never activated, with what they described as an extremely delayed support response over multiple days. Another ("Adamkan1") described a previously free workflow breaking, with paid tiers not restoring functionality and an unresponsive help center. A third ("Larry D. Cawley Jr.") reported persistent marketing emails despite repeated unsubscribe attempts over a year.

Key takeaway — Screenshot your billing confirmation and plan terms at signup. Multiple independent complaint threads describe billing/activation mismatches between app-store purchases and account status, and support resolution — when it happens — can take days.

None of this means IFTTT is badly built for its core job. It means the business side of the operation — billing sync, support staffing, subscription communication — shows real friction, and it's worth going in with that expectation rather than being surprised by it.

How IFTTT Stacks Up Against the Alternatives

An independent head-to-head of IFTTT, Zapier, and Make rated IFTTT ahead specifically on price-for-unlimited-simple-automations and learning curve — and behind on integration count, conditional logic, multi-step workflows, team collaboration, and business SaaS depth. That's a fair summary of the trade-off: IFTTT wins on friction, loses on ceiling.

Who Should Actually Use IFTTT

This tool earns its keep in a specific zone: personal and smart-home automation, individual content workflows, and simple cross-posting where a single trigger genuinely maps to a single action.

• Smart-home owners stitching together Philips Hue, Google Assistant, Alexa, Blink, or Smart Life devices across brands that otherwise don't talk to each other.
• Solo content creators auto-publishing blog posts to multiple channels or syncing RSS feeds to social accounts, similar to the Violette Laurent case study.
• Individuals managing personal admin — syncing calendars and task apps, location-triggered thermostat or lighting changes, weather-based energy adjustments.
• Anyone already using Claude or ChatGPT who wants those assistants to act on smart-home or social accounts via IFTTT MCP, without wiring up a separate integration layer.

It's easy to assume this tool is only for hobbyists, but the accessibility cuts both ways: a freelancer or one-person business handling their own invoicing and social scheduling (like Juan Segui above) gets real value here too, as long as the workflow stays single-path.

Who Will Outgrow It Fast

Any workflow that needs "if X, then A — but if Y, then B instead" runs into the architectural ceiling immediately, and Pro+'s filter code only partially closes that gap. Teams needing shared accounts, audit trails, or role-based permissions won't find them at any tier. And anyone building around a core business SaaS tool — a CRM, a ticketing system, a data warehouse — should check the catalog before subscribing rather than after, given the confirmed HubSpot gap and the recent Jira pause.

IFTTT still does one thing better than almost anything else in this category: turning a single "if this happens, do that" idea into a working automation in under a minute, with a catalog that's genuinely deep for smart-home and consumer apps. For that job — and for solo creators and personal productivity — it remains a legitimate, low-friction choice, and the ratings above reflect that split personality: strong marks on ease of use and breadth, weaker ones wherever billing and reliability come up.

Where it falls short is anything resembling business automation. The lack of branching logic isn't a missing feature waiting for a future plan tier — it's a structural choice, and independent scoring on scalability reflects that. Layer on recurring billing/support complaints and a catalog that's thin on the SaaS tools most businesses actually run on, and the case for using IFTTT beyond personal-scale automation gets thin fast. If your automation involves a CRM, a team, or more than one conditional branch, look at Zapier or Make first and treat IFTTT as the tool for what happens after your smart lights turn on.