Hi there, ​@tandadigital! 

Hope you don’t mind but I’ve moved your post here out into a new topic so we can address it separately. 

Nested line items can be a bit tricky! Could you share a screenshot of how the line items appear in the Zap? Also, can you confirm which specific fields are you trying to select? This will help us determine the correct custom pill mapping reference to use. Just a quick reminder—please blur or remove any personal information (names, emails, addresses, etc.) before sharing screenshots. A tool like Zappy can help with that.

Looking forward to hearing from you!

Hey ​@SamB – sure I already posted a screenshot before: 

 

I need to select all of them under lead_variables, and the issue is that their names + number can change. Sometimes for example {{nodeID__lead_variables__City}} will be there, other times it'll not. So I need a way to extract WHATEVER happens to be nested in lead_variables.

I solved this already with a Raw Web Hook, but if there's a way to do it that's simpler than Raw Web hook → Code → everything else, that would be nice.

Ah I see, ​@tandadigital. Sorry for completely missing that the other post you referenced was your own! 

Glad you were able to solve things using a Raw Web Hook trigger and Code action. As Troy mentioned in the other topic, the Catch Raw Hook trigger would get you all the fields, unparsed in the Raw Body field. That would be the only way to select all the fields that are sent in a single field. It’s not possible to select all fields under the lead_variables section by using a single custom pill mapping reference, you’d have to reference each field individually with custom pill mapping.

I’m not sure what app is sending the webhook but if you fill out all the possible fields for a new test lead, that should allow you to load in a new test record with all the possible fields available for you to select, without needing to use the custom pill mapping approach to select them. And if there’s a varying number of line items in the webhook you want to run actions for individually then you could use a Looping action to process a varying number of line items. You can learn more about that here: Loop your Zap actions.

That said, you mentioned that their field names and (line item?) numbers may change, so is it that you’ve got multiple forms that are capturing lead information with differently named fields and sending them to the Zap via a webhook? If so, you could potentially load in test records for each form to and map each equivalent field into the fields of subsequent actions of the Zap as needed. For example if there were 5 different forms with 5 differently named City fields, you’d select a each form’s City field from each form’s test record in the relevant City field on the action. Then when the Zap runs it will use the value that’s in whichever of the 5 selected fields contains a value. 

Hope that helps!