I think the "IFTTT is aimed at non-developers" argument is just dumb. Add a webhook channel, and people who don't know what webhooks are will just ignore it, the same way they ignore all the other channels for things they don't use. Noone is going to be more confused by the webhooks channel than they are already confused by the weemo channel.
Put a [for web developers] tag on it if you must, but a man shouldn't be denied steak just because a baby can't chew it.
We are a small, young startup and we have to be very particular about the things that we focus on. It's really hard to say "no" or "not now" sometimes. When I started one of the first things I thought for sure I would push for was a webhook channel. As a developer I want it myself. As I become more familiar with the people who use IFTTT I don't think it's the right thing to do for them right now. This doesn't preclude us from doing it in the future, but I think there are some better ways to solve the same problems that will cater more to the audience who has identified with the service.
Bingo. Right now I don't find IFTTT very useful because the pre-made options don't fit my use-cases very well, but if I had the flexibility to do what I pleased with the data, I would be telling everyone I know about it.
Put a [for web developers] tag on it if you must, but a man shouldn't be denied steak just because a baby can't chew it.