Creating a Packing Slip from Wave Invoice in Google Docs or Sheets

Hi ​@Gdog ,

This looks challenging. Can you try converting the item tables in Google Doc Templates to line items?  Also can you tell us why are you using Google Doc to create invoice and not some other platform.

Hello ​@jayeshkumarbhatia ,

All I want to do is prepare a packing slip. Wave has all the information I need and I can actually get the data. The only problem I have is, I have a couple of lines in the invoice such as Product 1 and Product 2. If I use Google Docs, I can place every piece of data using Fieldnames except the line items. If I use Google Sheets, I can get the line items but I can’t design the packing slip. So I am stuck :)

Hi ​@Gdog,

Welcome to the Community.

Consider using a combination of Google Sheets and Google Docs to handle line items and create packing slips. Set up a Zap triggered by a new Wave invoice to add line items to a Google Sheet. Then, use Google Docs to create a packing slip from a template, replacing placeholders with invoice data. While line items would need to be added manually from the sheet, this workaround balances design and functionality.

I hope this helps! Let me know if you have any other questions.
 

Hello ​@JammerS , thank you for your help. I have done the same thing all the way to Google Docs. However, in Google Docs, I pick “create document from template” in the action events. Then I have to map the data from Sheets to Docs. I set up a simple template with the fieldnames {{Product1}} {{Quantity1}} and right under {{Product2}}{{Quantity2}} thinking that I would have to create a separate fieldnames for each item. However in the fieldmap dropdown menu that comes from Sheets, I can add “PRODUCT” and “QUANTITY” which has the first row of the Sheets or “Rows Col A” and “Rows Col B” which has the two different lines in the Sheets. I have been adding both to Docs with no success. How would I enter line items separately into Docs?

Hi ​@Gdog,

Zapier’s Google Sheets integration processes rows as separate triggers, so it doesn’t natively handle mapping multiple rows into a single Google Doc template. Workarounds include using a Formatter step to join rows, using a third-party app like Airtable to manage multiple records, or adding a Code step to pull various rows. Note that the Google Docs action creates one document per Zap run, requiring separate Zaps for each document.

I hope this helps. Let me know if you have any other questions.