Sub-Zap

A Sub-Zap is a Zap that another Zap calls, like a reusable chunk of workflow. The main Zap uses a "Call a Sub-Zap" step to hand it some data. The Sub-Zap does its job and uses a "Return from Sub-Zap" step to pass the result back, and then the main Zap carries on.

They're useful when several Zaps need the exact same logic, like formatting an address or looking up a client, because you build it once and change it in one place.

I use them sparingly. The Call and Return steps both use tasks, so they cost more than you'd expect. They also make a workflow harder to follow, because the logic is split across more than one Zap. Most of the time I keep everything in one Zap and use Paths and Filters to branch it, so it's cheaper to run and easier for the client to edit. I only reach for a Sub-Zap when the same logic genuinely has to be shared by lots of Zaps.

Say a business has five Zaps that each need to find or create the same client in their CRM before doing anything else. You could build that lookup as one Sub-Zap: each Zap calls it with the client's email, the Sub-Zap finds or creates the record, and it returns the record ID. If the lookup ever changes, you fix it in one place.