IFTTT connects your apps, devices, and services so they work together automatically.
Create Applets that trigger real actions across 1000+ services: post on Instagram and it saves to Drive, a package arrives and your lights flash, a Google Sheet logs every new Slack message.
Whether you're automating your home, syncing your tools, or building workflows for your team, IFTTT handles the repetitive stuff so you don't have to.
This is the 34th launch from IFTTT. View more
New small business tools by IFTTT
Launched this week
A whole new stack of business tools just hit IFTTT. Connect HubSpot, Figma, Customer.io, Xero, FreshBooks, SendGrid, Apollo, and 13 more to automate the parts of running a business that eat up your time.
Whether you're onboarding a new hire, sending invoices, launching a product, or keeping your website up, it all runs once connected. Even your domain expiration won't catch you off guard. Hook it all up to Slack, Google Sheets, SMS, and more.
Free
Launch Team / Built With
IFTTT
For a small community/launch team this is the glue layer we always end up hand-rolling, wiring Linear or HubSpot events into a Slack channel without standing up our own webhook plumbing. The one thing I'd test first: when a downstream action fails (a SendGrid rate limit, or a Slack post to an archived channel), does the applet retry, surface the failure somewhere I'll actually see, or silently drop it? And since you asked, Discord as a first-class action (not just via generic webhook) would cover most of the community side for us.
IFTTT
@hazy0 I'll have someone from our product or engineering teams confirm the failure/retry. We do have Discord actions! https://ifttt.com/discord
Great expansion to your automated platforms. Currently I tend to use a competitor of yours for these sorts of tasks but given you have Xero now I will be experimenting with IFTTT a bit moving forward. Given the growth of agentic/automated development, I am wondering if we can expect payments automation through your tools?
ie. IF invoice received > Pay from X
IFTTT
@jhooley That's a great question! Some of our existing tools, like Stripe, have actions like "Create a payment link". Would that work for the flow you have in mind?
For small businesses, the missing piece is usually not "can this automate?" but "can I understand what happened when it fails?" Activity history, replay/dry-run, and a clear approval step for irreversible actions would make these integrations much easier to trust in the messy weekly operations layer.
IFTTT
@krekeltronics Love that feedback. We have a detailed activity history for each Applet that you can view at any time. The replay and approval features would be great additions as well.
The MCP path is what caught my eye, since you now have Claude composing applets across 20-odd services. When we exposed a big pile of tool integrations to an agent over MCP, the failure wasn't a single action erroring, it was the model confidently wiring up a plausible-but-wrong pair when two services had near-identical capabilities (a 'post message' living in both Slack and Discord, say). The preview step catches the obvious mis-wires, but does the MCP hand the model enough per-service context to disambiguate before it even proposes the applet?
The domain expiration trigger alone is worth installing this for - that's the kind of thing that never surfaces until it's already broken something. Between invoicing, onboarding, and keeping a website up across a few different companies, most of my "running the business" time is just remembering which system to check. Connecting Xero and FreshBooks into one automation layer instead of checking each dashboard separately is a real time save.
for actions that are hard to undo (like sending a message or triggering a smart lock), is there any built-in confirmation step before Claude actually fires the applet, or is that entirely up to how carefully the user phrases the request?
IFTTT
Hi @ulykbek11! Love this question!
Short answer: it's not left up to phrasing. Claude (via our MCP) always shows you the applet it's about to create and exactly what it will do, so nothing gets set up without you seeing it first. And for anything with physical or social side effects (smart locks, sending messages, etc.) you are notified whenever the applet runs. A first-class confirmation step before high-consequence actions fire is high on our list too. Appreciate you pushing on this! :pray: