The way I see it, Zapier is a subset of IFTTT, but it's not the functionality that separates them, it's the approach. For me it starts with the name -- IFTTT m

The way I see it, Zapier is a subset of IFTTT, but it's not the functionality that separates them, it's the approach. For me it starts with the name -- IFTTT means absolutely nothing to the average non-technical user, it sounds like alphabet soup or maybe a standards body or something. Zapier also doesn't mean anything, but it means nothing in a easy to distinguish way from other things. The audience for IFTTT (which is obvious once you know the acronym and makes sense) is for developers where Zapier is generally for smart forward-looking non-technical to fully technical people in the right domain. IFTTT might get a crazy article or two in tech-focused publications and some fanfare from nerds but Zapier is the kind of thing that silently chugs along to be everywhere in ~5 years once product managers/leads, managers, business analysis people get a hold of it -- and the tech isn't even bad. I don't work for Zapier, I don't push use or pay for their products, I have no connection to them except realizing when I first saw it that it was a excellent idea in a parched solution space with an above average to great implementation & UX. [EDIT] - Thinking about this some more, Zapier is a subset of IFTTT the concept as in I could Zapier's functionality in the sentence "if X then Y", but that statement actually doesn't mean anything because you can maneuver X to be just about anything and Y to be just about anything. Zapier supports non-trigger based workflows from what I understand and so does IFTTT... so maybe they're more equivalent than anything with Zapier focusing on enterprise-level polished integrations.