Trickiest project. A complex Zap was already in place, the problem was that JotForm data was coming to Zapier and being tested successfully when done manually. However during production, no data was passed, so Zap was not going well. My role was to figure out the issue and code extensively Python for this Zapier step to get the data right. We figured out that this is a Zapier limitation which ultimately Zapier never listed anywhere and they answered it in the community well. So I applied a separate strategy to get this data into Zapier and process that well.
Here are a couple of use cases I worked for here -
1. Fix Python code running in Zapier while testing inside Zap manually but not on Production. Code was for taking JotForm data in the form of multiple rows for a few product types and converting row-wise data into respective field-wise data.
2. Fix Python code running in Zapier while testing inside Zap manually but not on Production. Code was for taking JotForm data in the form of multiple rows for a few product types counting the number of rows for the respective product type and then appending that with the respective Product type Label.
3. Handle the case in zap for “Create multiple spreadsheet rows” inserting empty data for all columns except timestamp which is not provided for the respective product type on JotForm.
4. Fix the existing zap to reset the background color of newly inserted rows in Google Sheets by Zapier as it was copying the formatting of the previous row.
5. Zap optimization from 42 tasks to 24 tasks by usage of Google App script and Google Sheet Formula Automation to remove some actions.
6. Modification of zap to tweak Python step to format JSON data from JotForm and then replacing 6 action steps with a single one to resolve empty row creation problem in aritable and to reduce task usage.
