Is there any Google Docs Line Item support coming?

Hi @WAV-Tech 

Perhaps you can outline a specific example for us to provide more context on the inputs and outputs you are working with, thanks.

Also, feature requests can be submitted via Zapier Support: https://zapier.com/app/get-help

We have CognitoForms passing repeating fields data via JSON to our Zap. After numerous other steps, eventually the repeating fields data (currently arrays that are seen as line items) gets passed to a Google Docs template to be turned into a scope of work. To be able to grab each piece without having to perform even more steps to break it into usable chunks would be great. Each submission is already using 45 tasks on average: Checking each field’s data/error catching, Checking & creating folders on Google Drive, moving attachments to each folder, creating a scope of work and other documents, and finally sending emails out. Every little thing eats up several tasks and I’m looking to trim it down so I was hoping there was a built-in way to utilize the line items output as individual variables to be called without burning through more task allowance. Did I miss a simpler way to use that data or is the only choice to have to run through more steps? - I figured I’d check so I don’t request a feature that already exists.

I left out: here they show QuickBooks Zap being able to use line items https://zapier.com/help/create/basics/use-line-items-in-zaps but yet there’s no way to reference those same items in a Google Docs Zap.

@WAV-Tech 

Most Zap app integration are created and managed by the app developer, rather than by Zapier, altho I’m not sure who owns the GDocs integration and the QBO integrations.

QBO is an app that is more suited for line items (e.g. Estimate/Invoice), which is why the Zap app integration natively supports line items.

GDocs, on the other hand, is an app that isn’t primarily used for line items, thus why the Zap app does not natively support line items.

Code steps in Zaps can be used to do more dynamic data handling and thus one approach to lessening the number of Zap steps/tasks: https://zapier.com/apps/code/help

NOTE: Some Zaps have combo options, such as Find/Create OR Create/Update, that can help simplify the logic involved in Zap configurations.

Keep in mind the time savings being achieved, where usually good automations are worth the investment of extra Tasks or a higher plan.

@WAV-Tech 

Also, these advanced apps might be worth looking into…

Formatter > Utilities > Line Items: https://zapier.com/help/doc/how-use-line-items-formatterv2

Looping: https://zapier.com/apps/looping/integrations

Sub-Zaps: https://zapier.com/apps/sub-zap-by-zapier/integrations

Looking at the JSON trigger step, it see’s the data nested properly.

The loop action pulls everything except my components labels in the correct nests so I tried formatter (as seen below). So far, nothing will separate the items into the proper sections, the closest I’ve gotten to proper nesting again is this.

There are 10 sections. Section 1 has a single item in it and section 2 has 3 items in it, the other 8 sections are null - but - formatter is only creating 8 sections with all of the items included in each.

-This is why the original question, I had hoped there was a simpler way to pull nested values straight to Google Docs.

Now I’m on to codesteps trying to parse JSON data…. still no luck.

No matter what I try, it seems Zapier can’t dig into nested arrays from JSON. Searching across Google, there’s no answers or support on it, though similar questions seem to be asked often enough.

@WAV-Tech 

Consider hiring a Zapier Expert to help: https://zapier.com/experts