Zapier is a staple in the toolbox of so many small businesses, myself included. – and thanks to years of slow and steady effort, I consider myself a pretty savvy Zapier user.

But recently I learned a little Zapier trick and immediately knew I had leveled-up.

My long time friend Kevin Mogavero introduced me to a Zapier feature called Sub-zaps – and the power and utility hit me like a ton of bricks.

What are Zapier Sub-Zaps?

Essentially it’s a set of Zapier steps that you plan to be able to repurpose.

So, if there are common actions you want to bake into other Zapier recipes, you can build it as a sub-zap, and then just summon it as needed.

Here’s an article from the Zapier help center.

When would I use Zapier Sub-zaps?

There are lots of use cases – but essentially you could use a Sub Zap any time you have multiple Zapier recipes with multiple identical steps.

For me, the ton-of-bricks use case that came to mind was some progress tracking Zaps I had built for a course of mine.

The triggers all needed to be unique, but the subsequent steps didn’t – so I could have consolidated by sending all the initial triggers into a single sub-zap and saved myself a ton of time.

How do I set-up Zapier Sub-Zaps?

Here’s a robust walk-through from Kevin with two example use cases to illustrate just how this works:

Another way of thinking about this, for the old-time Keap users among us – subzaps are kind of like legacy Infusionsoft action sets. You bundle together things you want to have happen, then just ‘call’ that set of actions as part of another process.

Huge shout out to Kevin for turning me onto this beta Zapier feature – and for his permission to share the video with you all.

Hopefully you found this post valuable – if you have any questions feel free to drop them in the comments below. Thanks for reading (and watching).