IFTTT Buyer's Checklist: What to Verify Before You Pay

IFTTT invented the "if this then that" category. The core mechanic hasn't budged much since. What has changed is the pricing structure, the free tier's generosity, and the field of competitors now circling it. This checklist walks through what to verify — plan by plan, limit by limit — before you commit money or a workflow to it.

Who this checklist is for

Linking a Philips Hue bulb to a location trigger? Cross-posting a blog to Facebook via RSS? Asking an AI assistant to act across 1,000+ consumer services through IFTTT's new MCP integration? This tool fits. Trying to route new HubSpot deals into Slack with conditional branches and an audit trail? Keep reading. You want the alternatives section.

The product doesn't fence out business users entirely, either. Vendor testimonials describe real business use: a small business owner (Juan Segui) reports automating social posts, invoices, and project management, saving 13 hours a week; a content creator (Violette Laurent) saves 10 hours a week publishing to multiple sites via RSS. Both are single-trigger, single-action chains. That's exactly what IFTTT is built to do well.

Step 1: Confirm the free tier can actually run your workflow

Test whether the free plan covers your need before you even look at paid tiers. The limit to watch now is credits, not Applet count.

• Unlimited Applets, 1,000 credits a month. Triggers and successful actions use credits; unused credits don't roll over, and Applets pause when the balance runs out until the monthly reset.
• Every Applet feature. Multi-action Applets, queries, filter code, webhooks and AI services are on the free plan too.
• Slowest polling — polling Applets check every hour, not realtime.
• No free trial on paid plans any more — the Free plan is how IFTTT lets you try it.

Key takeaway — The free tier is a real starter plan now: every feature, unlimited Applets. What it caps is activity — 1,000 credits a month and hourly polling. Busy Applets or time-sensitive triggers? Budget for a paid tier from day one.

Step 2: Map your workflow against the three paid tiers

IFTTT no longer offers a free trial; the Free plan, with every Applet feature, is the way to try it. A custom plan is available by quote. A downgrade takes effect at the end of the current billing cycle.

Key takeaway — Filter code is the only place in IFTTT where you can add if/then branching inside an Applet — and it's now on every plan, Free included. Paid tiers buy credits and speed, not logic.

Step 3: Note how the two billing cycles are priced

Starter, Pro and Pro+ each display two numbers on ifttt.com/plans: a month-to-month rate, and a lower per-month rate for annual billing, with a SAVE 30% badge shown on the annual toggle.

• Starter: $2.99 a month billed monthly, or $2.09 a month billed annually — charged as $25.08 a year.
• Pro: $7.99 a month billed monthly, or $5.49 a month billed annually — charged as $65.88 a year.
• Pro+: $19.99 a month billed monthly, or $13.99 a month billed annually — charged as $167.88 a year.

Those are the figures IFTTT displays and the totals they resolve to. Confirm the number showing at your own checkout matches what's listed here before committing to a year upfront — an annual commitment doesn't unwind the way a monthly plan does if your needs change six months in.

Step 4: Decide if the architectural ceiling matters to you

This is the single most important thing to check before buying for anything beyond personal use. IFTTT has no branching logic, no loops, no data transformation built into its core. Conditional logic exists only through filter code, now on every plan — a genuine architectural ceiling, not something a higher plan tier removes. Upgrading buys more credits and faster polling. It does not buy a different automation engine.

Filter code lets you write a short JavaScript condition inside a single Applet — skip an action if a field is empty, say. It doesn't let one trigger fan out into multiple decision branches the way a visual workflow builder does.

"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."

That's Zapier's framing, and yes, a competitor talking its own book. But the underlying point — IFTTT's consumer/IoT lean versus business SaaS depth — is borne out by IFTTT's own integration catalog, covered next.

Step 5: Check integration depth against your specific stack

IFTTT lists 1,000+ supported brands and services, with homepage-featured integrations including Discord, Gmail, Google Sheets, Slack, Notion, Spotify, Philips Hue, Todoist, WhatsApp, and AI services from ChatGPT, Gemini, and Anthropic Claude. Broad, for consumer and IoT use.

Thin, for business software. HubSpot integration is absent entirely. The Jira integration got paused in September 2025 after an upstream API deprecation — a concrete reminder that IFTTT's third-party integrations lean on other companies' APIs staying stable, and that IFTTT doesn't always keep up proactively.

Key takeaway — If your must-have integration is a mainstream CRM, help desk, or project tool, check IFTTT's live service directory first. Don't assume "1,000+ services" means your specific tool is covered with real depth.

Step 6: Test for polling delays before relying on time-sensitive triggers

Polling Applets check every hour on Free, every 15 minutes on Starter and every 5 minutes on Pro and Pro+. Even on paid tiers, delays of 1–15 minutes get reported, so faster polling beats the free tier, sure, but "instant" isn't literal. Building something where a 30-second response actually matters — a security alert, a time-boxed notification? Test the real latency on your specific trigger/service pair before treating it as production-ready.

Step 7: Confirm whether you need team access — because IFTTT doesn't offer it

No role-based access control. No shared or team accounts. No audit logs. If more than one person needs to touch a workflow, the only option is sharing login credentials — a real operational and security gap for team use, and independent reviews flag it specifically. There's also no self-hosting option, which matters if data residency or on-prem requirements are part of your evaluation.

This is where the product's consumer roots show most clearly. It was built for one person automating their own devices and accounts. Multi-user support was never architected in — not an oversight, just not the job it was built for.

Step 8: Evaluate the AI features with appropriate skepticism

IFTTT now advertises AI services — summarizing, transforming, translating information — plus AI-powered Applet templates using ChatGPT, Gemini, and Anthropic Claude, available on every plan. It also shipped an MCP (Model Context Protocol) integration connecting Claude, ChatGPT, Cursor, Microsoft Copilot, Perplexity, and OpenClaw to its 1,000+ services, letting an AI assistant search, build, and run Applets on a user's behalf.

Here's the honest read: nothing in the available evidence confirms IFTTT has built or embedded a proprietary AI model. What it has is a deterministic if-this-then-that engine with API hooks into third-party AI providers (OpenAI, Google, Anthropic), plus a bridge — MCP — that lets those providers' assistants operate IFTTT's existing automation layer. Genuinely useful connector. Just don't mistake the "AI Services" branding for a native capability IFTTT built itself. If AI matters to your buying decision, verify the specific model and data-handling terms directly rather than assuming any IFTTT plan ships a homegrown AI feature.

Step 9: Read the billing and support fine print

Reviews on Trustpilot skew heavily negative — worth naming since it's the outlier among the platforms tracked here — with recurring complaints about being charged after trying to cancel a trial, and about "price locked forever" promises to long-time Pro subscribers that got changed anyway. Other review sources (G2, GetApp, TrustRadius) skew considerably more positive. Treat Trustpilot as one lens, not the full picture.

Recurring, cross-platform issues worth checking against your own account before renewing:

• Billing sync bugs. One App Store reviewer paid for a full year of Pro that never activated on their account, then hit multi-day support delays.
• Silent third-party breakage. One reviewer had Applets fail when TP-Link Kasa dropped IFTTT support without a clear announcement — and initially assumed it was IFTTT's fault.
• Persistent marketing emails, despite repeated unsubscribe attempts, per at least one App Store review.
• Support bandwidth. IFTTT's headcount sits around 50 people, and an independent analysis ties that to slower support turnaround and roadmap velocity next to bigger competitors.

On the flip side, review themes also include cases where persistent contact eventually got a real person to fix a webhook bug, plus at least one refund issued after a billing complaint. Support can work. It's often just slow getting there.

Step 10: Check current service status for anything mission-critical

The Jira pause in September 2025 is a useful case study: third-party API deprecations happen, and IFTTT's public status page (status.ifttt.com) is the place to check before you build a workflow around any single integration you can't afford to lose. This goes double for services with smaller user bases inside IFTTT's catalog — they get far less scrutiny than the Alexa/Google Home/Philips Hue integrations most users actually lean on.

Step 11: Weigh security posture if compliance matters

Third-party security profiling lists SSO support (Okta, Google, Microsoft, SWA) and multiple 2FA methods (SMS, email, hardware, software, TOTP, U2F), plus a public bug bounty program. Compliance certifications including SOC 2, PCI, HIPAA, GDPR, ISO 27001, and FedRAMP show up in independent security profiling but aren't confirmed on IFTTT's own marketing pages in the material reviewed here. If compliance is a procurement requirement, ask IFTTT directly for current certification documentation. Don't rely on third-party lists for this one.

Step 12: Decide if a competitor fits your actual job better

None of these matches IFTTT's setup speed for a single consumer automation — that's IFTTT's actual advantage, not a weakness to route around. Pick a competitor for the job it does, not because IFTTT did something wrong on this one.

Key takeaway — Buy IFTTT for what it was built to do: one trigger, one action (multi-action Applets and filter code on every plan), fast to set up, across a huge catalog of consumer and smart-home services. Buy something else for branching logic, team accounts, or CRM depth — no IFTTT plan adds those.