Hi!
I have created some Sub-Zaps and they are running nicely.
But one thing is either not working or I misunderstood the concept.
You can define (required) input fields for the Sub-Zap. But so far I have not found a way to actually do anything with those fields in my Sub-Zap. I cannot reference them anywhere through the normal “previous step” output selection, and the Copilot suggested syntax of {{<zap_id>__<input field name>}} also does not show any data.
What am I missing?
Quick update, in a very simple test Zap the input field suddenly appeared after a few draft/publish/test iterations.
Now to check whether my production zap behaves the same way.
[Update] Yes it does.
So either it takes some time (hours rather than minutes) to propagate the input fields all through the Zapier backend, or it was broken and now it is fixed again.
+6Hey
If test is working as expected, it should work in production as well. For live zaps, you can see Zap history to spot any issues- https://zapier.com/app/history. Hope it helps!
+14Hi
Help links for using Sub-Zaps in Zaps: https://zapier.com/apps/sub-zap-by-zapier/integrations#help
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
