Zapier co-founder here.<p>This is seriously the biggest change to our product since launching the company. We've been working on it for a year (including a beta w/ several thousand users) and are very excited to finally release it. Before, Zapier only supported 1-to-1 integrations which limited it's power. Multi-Step Zaps open up a huge array of new power...<p>- transforming data (like dates, string manipulation)<p>- executing JS code in between steps (can do manipulation, extra API calls, etc.)<p>- looking up data inside other apps<p>- if an item isn't found when looking it up, create it<p>More details in our release notes: <a href="https://zapier.com/blog/workflow-automation/" rel="nofollow">https://zapier.com/blog/workflow-automation/</a><p>How we built this: <a href="http://blog.invisionapp.com/redesigning-interactive-editor/" rel="nofollow">http://blog.invisionapp.com/redesigning-interactive-editor/</a><p>I know a ton of folks in the HN community use Zapier. Thank you so much for your support. I can't wait to see what you build now!
This is HUGE! So excited to see this. I automate huge swaths of my life with Zapier.<p>I have been relying on a little self-hosted web app to "fork" some web hooks and this seems to me to eliminate that need entirely.<p><a href="https://github.com/deadlyicon/deploy-hook-forker" rel="nofollow">https://github.com/deadlyicon/deploy-hook-forker</a>
Good stuff - I know this has been in the pipeline for sometime. Excited to see it out in the wild. Congrats to the Zapier team on producing an awesome product - look forward to using multi-step zaps.
I love Zapier, with one exception. For some reason the webhook zap doesn't provide the whole post body. Strips the root {} meaning it shows up as text without structure. Very odd choice that I wish they'd fix. Besides that am big fan
Anyone who uses Zapier for personal workflows - I am curious why use Zapier over IFTTT?<p>Note: this is NOT a challenge to why something like Zapier exists for business, nor a comment directly on the new multi-step Zaps.
I'm super excited about this. Well done!<p>One of my biggest pain points was the lack of ability to determine if a record already exists before choosing to use an Update or Create action. (You'd think a service's API would treat Update the same as Create if no matching record is found, but that's not always the case.) So I've had to err on the side of caution and always use a Create action, thus filling the CRM (or whatever) with many many duplicates.<p>The search feature looks like it will handle this. Will be implementing shortly.
Very cool, congratulations on the launch.<p>I'd be curious to read a blog post about if/how you beta tested this feature and ensured "fit" of the final shipped feature. Did you have an early adopter / guinea pig group?<p>If I wanted to make a Zap DAG, would I just arbitrarily linearize it ? i.e. if my deps were,<p><pre><code> A -> B
B -> X
B -> Y
B -> Z
X -> C
Y -> C
Z -> C
C -> D
</code></pre>
one linearization is A -> B -> X -> Z -> Y -> C -> D<p>Do you notice implicit dependencies and do actions in parallel where there is no dependency ? Maybe it doesn't matter except for very deep / wide zaps.