If you belong to one or more Zapier Teams, select your desired account.

List the inputs to accept from "Call a Sub-Zap" and they will show up as fields. Add the word "required" to the label if you would like it to be required in the calling Zap.

Will only list "Sub-Zaps", which require the use of both the "Start a Sub-Zap" trigger and a "Return from a Sub-Zap" action.

To properly use a "Call a Sub-Zap" action you must create another Zap that contains *both* the "Start a Sub-Zap" trigger and "Return From a Sub-Zap" action. For your convenience, you can use [this link to create a Sub-Zap](https://zapier.com/app/editor?create=true&template__0__selected_api=SubZapCLIAPI%400.10.8&template__0__type_of=read&template__0__action=start_subzap&template__1__selected_api=SubZapCLIAPI%400.10.8&template__1__type_of=write&template__1__action=return_subzap).

List the keys and values to return to the original "Call a Sub-Zap". For example, you could ask for an email address and use it later in the Zap. It is generally safe to add more return values, but be careful about removing items that parent Zaps may rely already on!

Build reusable Zap components and systems by building and calling "Sub-Zaps".

Zapier Automation Platform

PRODUCTS

CAPABILITIES

By use case

By app

By team

By company size

How Zapier Zaps

How Zapier Uses AI

By team

Learn more

Get help

Zapier quick-start guide

Developer resources

Sub-Zap by Zapier Integrations

Sub-Zap by Zapier Help & Support

Build reusable Sub-Zaps

About Sub-Zap by Zapier

Related categories