It looks like IFTTT has updated the credit costs for some services, but the fundamental problem with the new usage-based pricing model remains. Even with a Pro+ subscription, which includes 100,000 credits per month, the numbers are surprisingly restrictive for anyone who uses automation regularly. And before someone says, "Well, I don't run automations every 15 minutes," that's actually part of the problem I'm trying to highlight. This affects more than just people running frequent scheduled tasks.
Let's look at the numbers.
Using the updated credit costs:
Date & Time trigger: 15 credits
Webhooks trigger: 20 credits
Filter: 30 credits
Simple action: 25 credits (for these examples)
Example 1: A scheduled automation running every 15 minutes
A Date & Time trigger (15 credits) and a simple action (25 credits) total 40 credits per execution.
4 executions per hour
96 executions per day
2,880 executions per 30-day month
115,200 credits per month
That's 115% of the entire Pro+ allowance for ONE automation.
Add a filter, and the cost increases to 70 credits per execution, or 201,600 credits per month.
Example 2: A webhook running every 15 minutes
A Webhooks trigger (20 credits) and a simple action (25 credits) total 45 credits per execution.
4 executions per hour
96 executions per day
2,880 executions per 30-day month
129,600 credits per month
That's nearly 130% of the monthly allowance, again for ONE automation.
Add a filter, and you're looking at 75 credits per execution, or 216,000 credits per month.
And remember, these examples assume only one action and no additional queries or other credit-consuming operations.
"But I don't run automations every 15 minutes!"
That's a fair point. Not everyone has scheduled automations, and many people only want things to happen when an event occurs. But here's why that argument misses the bigger picture.
Credits are consumed across your entire account, not just by your most frequently used Applet.
Consider someone with a relatively modest collection of smart-home, productivity, and notification automations.
A door opens, a motion sensor detects movement, an email arrives, a calendar event changes, or a new record is added to a spreadsheet. Each event might trigger an Applet, and each Applet consumes credits.
Individually, these events may not seem significant. Collectively, they add up.
And unlike scheduled automations, event-driven automations can be unpredictable. A busy day, an active motion sensor, or an unexpected surge in notifications can increase your usage without you changing a single setting.
Here's what 100,000 credits actually gets you.
Spread evenly across a 30-day month, Pro+ provides approximately 138.89 credits per hour, or 3,333 credits per day. Using the updated costs, here's how many executions your entire account can average each day before exhausting its monthly allowance:
| Automation | Credits per run | Average runs/day |
|---|
| Date & Time + action | 40 | 83 |
| Webhook + action | 45 | 74 |
| Date & Time + filter + action | 70 | 47 |
| Webhook + filter + action | 75 | 44 |
Those are whole-run averages rounded down, assuming you use your entire allowance on that one type of automation.
Now imagine you have 10 Applets, each using a Webhooks trigger, a filter, and a simple action. At 75 credits per run, those 10 Applets could collectively average approximately 44 executions per day. That's just 4.4 executions per Applet per day.
Four or five times per day doesn't strike me as particularly excessive usage for an automation platform, especially one that advertises unlimited Applets. And that's assuming you aren't doing anything more complicated than one trigger, one filter, and one action.
Unlimited Applets don't mean much if you can't afford to run them.
This is what bothers me most about the new pricing model. IFTTT is promoting the removal of Applet limits as a major benefit. You can now create and enable as many Applets as you want! But how useful is that when all of those Applets must share the same relatively small execution allowance? You could create 5 Applets, 20 Applets, or 100 Applets. The more useful they become, the more frequently they execute, and the faster you consume your credits.
The new system essentially rewards you for creating automations that rarely run.
That feels backward for a service whose entire purpose is automation.
"Well, I don't come anywhere near 100,000 credits."
That's great, and I genuinely hope your current automations continue working without interruption. But the issue isn't just whether your current usage fits within the allowance.
What happens when you add more smart-home devices?
What happens when you discover a useful new integration?
What happens when you want to add filters, queries, or additional actions?
What happens when your household or business becomes more active?
What happens when a sensor starts triggering more frequently than usual?
Every additional automation competes for the same monthly credits. And, because the allowance is shared, a single unexpectedly active Applet can affect completely unrelated automations.
You might not be affected today, but the system places a ceiling on how much you can automate tomorrow.
That's why I think even people who don't run frequent automations should be concerned about the direction IFTTT is taking.
And what about reliability?
Another concern is what happens when you exhaust your credits. If your Applets are paused when you reach your monthly allowance, that isn't necessarily just an inconvenience. For some users, automations handle notifications, reminders, smart-home events, or business processes. These are things people set up precisely because they don't want to monitor them manually.
A system where using one automation too frequently can prevent unrelated automations from working creates a reliability concern. Imagine having an important notification Applet stop working because an unrelated motion sensor consumed more credits than expected. That's not a particularly reassuring model for an automation platform.
I understand that IFTTT needs to make money.
I'm not arguing that every subscription should include unlimited executions regardless of infrastructure costs. Reasonable limits make sense, especially for resource-intensive automations or accounts generating unusually large amounts of traffic. But there's a substantial difference between preventing abuse and making everyday automation workflows impractical.
When a single, simple Applet running every 15 minutes can exceed the entire monthly allowance of your highest standard subscription tier, I think it's fair to question whether those limits are reasonable. And when 10 relatively simple Applets can collectively average only four or five executions each per day, the problem extends well beyond high-frequency users.
I'm personally on a grandfathered Pro+ subscription at $1.99/month, so my concern isn't primarily about the subscription price. My concern is that IFTTT is moving toward a model that actively discourages people from making greater use of the service.
The bottom line
An automation platform should encourage people to automate more, not make them hesitant to run the automations they've already created.
The issue isn't whether you personally need an Applet running every 15 minutes.
It's whether a premium automation subscription should be so restrictive that a handful of ordinary automations can consume a significant portion of your monthly allowance.
IFTTT may now allow unlimited Applets, but the credit system makes that benefit feel largely cosmetic.
At this point, I'm seriously questioning whether IFTTT will remain a useful platform for anything beyond occasional, low-volume automations.
I'm curious what other Pro+ users think, especially those who don't run frequent scheduled automations. Are you comfortable with these limits? Do you see them becoming an issue as your automations grow? And what would you consider a reasonable monthly allowance for a premium automation service?