IFTTT Review — Simple Applets Across 1,000+ Services

What Is IFTTT?

This platform is an automation service built around two-part connections. You choose a service and an event as the trigger, then choose a second service and an event as the action. When the trigger fires, the action runs. The company launched the project in 2010 under the name it still trades on, and describes its core unit as an automation connecting two or more services to create a new experience.

The practical result is a layer that sits between services which were never designed to talk to each other. A mail trigger can add a row to a sheet, a fitness device can signal a webhook, and a video platform can feed a summarizer. Because the trigger-and-action model is fixed, the setup is short enough to build while you are still thinking about the problem.

How Applets Work

Every automation is an Applet, and IFTTT's free plan lets you keep two of them. Applets can be built by hand or adopted from the published library, and runs are not metered as individual operations on that tier. That single fact makes this unusually cheap for automations that fire constantly — a sensor reporting every few minutes does not generate a per-event invoice.

Paid plans widen the surface rather than the billing unit. Pro lifts the Applet ceiling to twenty and turns on faster execution speeds, multi-action Applets, webhooks, increased rate limits, and exclusive triggers and actions. Pro+ removes the ceiling entirely and adds the ability to connect several accounts of the same service, which is what a team with two inboxes or two stores actually needs.

Queries and filter code arrive at the top tier. They let an Applet narrow its timing and conditions, so an automation can fire on a value rather than on every single event. Until you are on Pro+, the honest expectation is that an Applet fires whenever its trigger fires.

• Free: 2 Applets, standard speeds, unlimited runs, published or DIY Applets
• Pro: 20 Applets, fastest speeds, multi-action Applets, webhooks, Twitter Applets, higher rate limits
• Pro+: unlimited Applets, everything in Pro, AI services, multiple accounts, queries and filter code
• Applets run without a per-operation charge on the free tier

The Service Catalogue and Its AI Services

The catalogue is the product. IFTTT states that over 1,000 apps, services, and devices are connected, and its own marketing points to users of those services relying on the connection layer. That figure is the honest reason to choose it: matching a smart-home brand or an obscure consumer service is usually faster here than on a business-first platform.

AI services are mixed into that catalogue. The directory lists a summarizer, translation, prompt handling, and AI helpers pointed at specific networks and platforms. The platform's own homepage positions this as giving an AI assistant more than 1,000 services to act on, and an MCP server is the mechanism: connect a client such as Claude, ChatGPT, Cursor, Copilot, or Perplexity and the assistant can trigger real actions rather than only describe them.

One detail deserves attention before you plan around it. Access to the AI services is listed as a Pro+ feature, so the assistant-adjacent capabilities sit on the $8.99/month tier rather than on free or on the $2.99 Pro plan. There is also a prompt-driven path for drafting an automation in plain language, which shortens the first attempt considerably.

• Over 1,000 apps, services, and devices connected
• AI services in the directory include summarising, translation, prompts, and network-specific helpers
• MCP server connects assistants such as Claude, ChatGPT, Cursor, Copilot, and Perplexity
• AI services require the Pro+ plan

How It Compares to Zapier, Make, and n8n

The three closest competitors solve the same problem with different billing units, and IFTTT's advantage shows up most clearly when you put the pricing side by side. Zapier charges per task, so a five-step automation that runs a thousand times a month consumes far more billable units than the equivalent on a credit-based platform such as Make. n8n bills per whole workflow execution and can be self-hosted, which wins on volume if you are willing to run infrastructure.

This tool sits at the other end of the trade. IFTTT Applets are deliberately simple, the free tier does not meter runs, and the entry paid plan costs a few dollars a month when billed annually. In exchange you give up the branching, multi-step sequencing, and error handling that those platforms are built for.

The category gap is real rather than marketing. n8n and Dify-style builders give a developer prompt control and self-hosting; relevance- and Gumloop-style platforms give a business team governed agent workforces. This product is aimed at a household or a very small operation, and it does not try to cross into those categories.

• Zapier, Make, and n8n bill per task, credit, or execution — this free tier meters no runs
• Its paid plans start around $2.99/month billed annually, below the typical automation entry price
• No branching or multi-step error handling; complex orchestration belongs to Zapier, Make, or n8n
• No self-hosting option and no API-first developer surface

Who It Fits and Where It Stops

This automation service fits when the link is a single, durable one between two things you already use. IFTTT is quick to set up for a smart-home routine, a lead dropped into a spreadsheet, a daily digest assembled from a handful of feeds, or a text handed to an AI service for cleanup. Because an Applet is short, you can usually build and verify one in a few minutes.

It stops when the work needs to branch. If an automation has to check a condition, try a second service, recover from a failure, and hand off to a human, you are describing Make or n8n rather than this one. The same applies to anything requiring volume: the platform has rate limits, and only the paid tiers increase them.

For the MCP angle, the useful question is not whether the assistant is clever but whether the target service already exists in the catalogue. The server is only as good as the 1,000-odd services behind it, so check the service list before designing the workflow around it.

• Good fit: single-step links between consumer apps, devices, and AI services
• Weak fit: conditional logic, retry handling, multi-department orchestration
• Check the rate limits before committing a high-frequency trigger
• For MCP work, confirm the target service exists in the catalogue first

IFTTT Pricing

Free $0 forever (2 Applets). Pro $2.99/mo, or $35.88 billed annually. Pro+ $8.99/mo, or $107.88 annually, which adds AI services, unlimited Applets, and multiple accounts. Yearly billing saves 40%. Checked September 2026; may change.

Best For

Recommended use cases and scenarios where IFTTT shines.

Frequently Asked Questions

Common questions about IFTTT, answered.