Ah ha! I understand what y’all are asking now. Sorry, took me a bit to connect on it.
The Zap Template builder relies on the static sample data you provide when you develop your triggers and actions. It does not make a live request for data at all, or spin up an actual listener to wait for hook messages like the real Zap editor does (only if you don’t configure performList
- which you should always do).
The user interfaces look the similar, but what you’re building is different than a real Zap. It’s a template for other users to create actual Zaps, with settings and auths specific to their accounts. So everything you configure has to be totally common to all users. Note that the Zap Template creator doesn’t allow you to configure a connected account, which is something necessary to even access your API or other APIs. That’s the purpose of the static sample object - to provide a “contract” for the data available for field mapping that’s going to be there every time a Zap runs, for any and all users who make Zaps out of the template.
For this reason making a template or even a shared Zap with a Webhooks by Zapier trigger isn’t supported today.