Curious how this handles applets that need multi-step confirmation
before firing - for anything irreversible (locking a door, sending a
message to the wrong channel), I'd want Claude to explicitly confirm
before triggering, not just execute on the first ask. Would love to
hear directly from the team: is there a built-in confirmation layer
for higher-stakes actions, or is that left entirely to how the user
phrases their request?
Hey Product Hunt 👋 I’m Linden, founder and CEO of IFTTT. After 16 years, we’re turning the page: today, IFTTT becomes IFTTT.ai.
In December 2010, I wrote IFTTT’s first blog post to explain the name: if this, then that. The idea was that a simple structure of triggers and actions could let anyone get creative with their digital tools. Today’s launch is about opening that up to more people than ever.
Starting today, every core feature and every service on IFTTT is available to everyone, including multiple actions, filters, queries, and Webhooks. You can now build as many Applets as you want. Plans are now based on credits, so you pay for Applet runs, not which features you can use.
We’re also launching new AI features and upgrading the ones you already know. Our AI Agent can keep an eye on a web page for you, catching new listings or a number that changes, like a price or new job listing. The Agent can also run queries and actions across your connected apps when you describe them in plain words. AI Action assist writes your Applet’s action dynamically each time it runs based on the trigger, and can skip the action when appropriate. As a bonus, all of our existing AI queries now run on better models.
An Applet can notify you when a competitor changes their price, log the new number to a spreadsheet, and post it to your team’s Slack. Another Applet can read your bill emails and add each due date to your calendar. Not sure where to start? Describe what you want in IFTTT’s chat, or ask your AI assistant through our MCP.
Putting the internet to work for you is still what IFTTT does. AI just means we can do a lot more of it.
I’d love to know what you’d automate first. Tell us below, the team and I will be here all day answering questions.
Long time! Big fan of If This Then That since 20211.
I'd love to automate our upcoming PH launch activities. If you have one created for your launch, please share 😉
@vijayanandkailash Thanks Vijayanand! Love this idea. A trigger for your own launch, like a new comment or upvote, would make launch day so much easier. Our Product Hunt service only watches new launches by topic today, so we've added a launch trigger to our to-do list. Good luck with your launch!
Always loved IFTTT but for some reason didn't use it much lately, perhaps this is the reason to start using it again.
@erikkarlberg Welcome back, Erik! Every plan, including Free, now includes every service, so it's a good time to try again.
Congrats on the launch and the new features! I remember writing a lot about IFTTT when I was working with uHoo, an indoor air quality sensor. They had many automations via IFTTT, and it was so cool how it can control the appliances.
@heyitsirenechan Thank you Irene! uHoo is a great example of what IFTTT is for: the air gets worse and the purifier turns on by itself. Thanks for writing about it back then.
Congratulations on a confident step into the future! The updated mobile app is especially polished and genuinely fun to use. Great work from the OG in automation.
I'm in the middle of moving my automations from Zapier to n8n, so plain-English setup caught my eye. When a run fails, what does the user see? That's usually where non-technical teams give up.
@theashleygross Hey Ashley! I’m Josh, one of the PMs at IFTTT.
Great question and you’ve hit on the exact thing we obsess over. Plain-English setup only gets you halfway. If a run fails and all you get is a cryptic error, non-technical folks walk away, and fair enough.
When an Applet fails on IFTTT, you get a notification and an entry in that Applet’s activity log that says what went wrong in plain language, like “Google Sheets needs to be reconnected” or “the spreadsheet couldn’t be found.” Most failures come down to an expired connection, and in those cases we point you straight to the fix so you can reconnect in a tap.
If something still doesn’t make sense, you can ask our Chat directly. Something like “why did my Sheets Applet fail last night?” works, and it’ll help you get it running again without digging through logs. No one is perfect, so making failures easier to understand and fix has always been a focus for us. And if all else fails, our stellar Community Team is always available to help!
I’d love to hear where Zapier and n8n have lost you on this. That kind of feedback goes straight into what we build next!