I’m working with Zapier automation and need help with the Code by Zapier step. Currently I have to manually map each field from previous steps into the input data section. This gets really tedious when dealing with lots of fields.
Is there a way to grab the entire data bundle from a previous step as one complete object instead of mapping individual fields? I want to access it like a JSON object that contains all the available data.
My specific use case involves pulling survey responses from Google Forms and then processing all the question-answer pairs in my code step to format them for an email. Since the number of form fields can vary, manually mapping each one is not practical.
Any suggestions on how to accomplish this would be greatly appreciated!
I had the exact same problem! You don’t need input mapping at all - just reference the step output directly in your code. Skip inputData and use bundle.inputData instead, or bundle.cleanedRequest for webhook data. With Google Forms, I use bundle.inputData.step_name to grab everything at once. Here’s the thing - Zapier automatically makes all previous step data available through the bundle object. Leave the input section completely empty and just access what you need in the code. This saves so much time with variable form structures since your code can handle whatever fields get thrown at it.
You can grab the complete data object by using inputData in your Code step. When setting up Code by Zapier, there’s a way to pull the entire bundle without mapping each field manually. Just use inputData.stepName where stepName matches your Google Forms trigger step. This gets you the full JSON object with all responses. I’ve done this tons of times for dynamic forms where the field count changes. Make sure your input data config includes the step reference correctly. Once you’ve got the complete object, you can loop through all properties instead of hardcoding specific mappings. Makes your automation way more flexible for different form structures. Really handy for survey data since you never know when questions get added or removed.
another tip: when configuring your code step inputs, click the ‘show all options’ toggle. it reveals a ‘raw data’ option where you can use the full step output instead of manually mapping every field. your code can then access it as one complete object, super useful!