I've long been interested in web automation as a complement to my iOS apps and workflows. While I expressed my fair share of skepticism about the practical benefits of web automation in the past – primarily due to a lack of native apps to trigger recipes on IFTTT and Zapier – with time I've learned to appreciate the ability to automate web services and let them perform tedious tasks for me. The fact that I'm increasingly relying on web services with iOS apps that are simple front-ends to data that lives in the cloud might be related, too.1 My use of web automation isn't dramatically creative: I have a couple of Do Button recipes to send automated emails with one tap; I forward YouTube updates and some RSS items to Slack; and, I let a couple of Twitter accounts tweet on my behalf with automated recipes because I'd forget otherwise. Nothing too revolutionary.
Today, Zapier – the power-user (and paid) alternative to IFTTT – is launching multi-step zaps (the equivalent of recipes in IFTTT), which I was able to test for the past week. I've long preferred Zapier to IFTTT for the additional controls that it offers when building complex web automations. Zapier lets you assign filters to actions, you can parse data from email messages with a dedicated Zapier Parser service, and, generally speaking, everything is built with an eye for people who, like me, want to tweak as much as possible. Multi-step zaps fit squarely into this strategy and they're, by far, the most powerful solution I've tried to chain multiple web services together and save time.