I’m working on building a custom Zapier application using their web interface. I have a situation where I need to create conditional field requirements.
Here’s what I’m trying to achieve:
First field: “Tax Rate Info” (text input)
Second field: “Tax Category” (dropdown selection)
I want the dropdown to become a required field only when the text input contains “0” or “0%”. If the user enters any other value in the first field, the dropdown should remain optional.
Is there a way to implement this conditional logic in Zapier’s app builder? I’ve looked through the documentation but couldn’t find clear examples of dynamic field requirements based on other field values.
Nope, Zapier’s web builder can’t handle dynamic field requirements like that. The platform only does static validation at the schema level - no conditional stuff. What you want would need custom JavaScript running client-side, but Zapier doesn’t give you those hooks in their visual builder. Your best move is handling this validation on your webhook endpoint instead. When the zap fires, check the tax rate server-side and throw a meaningful error if the category’s missing. Not great for UX since users won’t see the error until after they submit, but it’ll keep your data clean.
totally agree! the web interface can be a bit limiting, going with CLI will give you more control for those conditions. best of luck, hope it works out for ya!
Had the same issue when building my Zapier integration. The web interface can’t do dynamic field validation where one field depends on another - it’s just not possible. Here’s what worked for me: make both fields optional in Zapier, then handle the validation logic in your app’s backend. When Zapier sends the data over, check if the tax rate is “0” or “0%” and throw an error if the tax category isn’t filled. Yeah, you lose real-time validation, but you get accurate results and clear error messages that actually help users figure out what went wrong during testing.