Is there any Google Docs Line Item support coming?
Is there an easier way to include line items into our Google Docs templates than having to run custom scripts on everything? I’ve looked, and it seems to me that it would make sense if it was a default part of Zapier’s Google Docs actions, but no such luck. I have many sets of line items that need to be referenced in the template on what is already a very complex Zap, adding several more steps to break all of the data apart and utilize it seems like it should’ve been made unnecessary early on in Zapier’s lifetime. - Any developments coming? Does the dev team read these and make improvements?
If nothing else, is there a leaner, more efficient way to handle this?
Page 1 / 1
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.
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.
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…
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.
I just came across this and wanted to add that there is an existing feature request for line items to be supported with Google Docs. So I’ve gone ahead and added @WAV-Tech’s vote to that.
I can’t make any promises as to when this feature would be added but we’ll be sure send an email notification as soon as it is! For anyone that comes across this closed thread and would like to be added to the feature request, please contact our Support team and they will be happy to add you to it!
