Test and troubleshoot the Google Sheets Zaps
Build against a copy of the sheet with fictional data, then fix the five problems that cause most failed runs.
- 5/5 on G2
- 4.2 on Capterra
- Building QuoteCloud since 2013
Test every Zap on a copy of your sheet with @example.com contacts before pointing it at the real one. Most failures come from five things: no header row, a lookup value that doesn't match exactly, prices typed as text, a trigger that also fires on the Zap's own edits, and columns renamed after the Zap was built.
Last reviewed by the QuoteCloud team
How do I test the Google Sheets Zaps?
Copy the sheet
Make a copy of the real sheet, keep the same header row, and point every Zap at the copy while you build.
Use fictional data
Test rows and test documents use @example.com email addresses, so nothing reaches a client.
Test each step
Zapier's step test shows what each step received and wrote. Check the row or the document after every test.
Run it end to end
Add a test row or send, view and sign a test document, and watch the whole Zap run in Zapier's history.
Switch to the real sheet
Change the spreadsheet in each step, run one more test, then turn the Zaps on.
The usual problems, and the fix
No fields to map
Zapier needs a header row: Google Sheets' steps read row 1 as the column names. Add headers, then refresh the fields in the step.
Row not found
Lookup Spreadsheet Row needs an exact match. Check the Document column holds the number exactly as QuoteCloud writes it, with no spaces.
Price is zero or blank
The column holds text such as $5,940.00. Map a plain number, or add a Formatter by Zapier step to clean it.
Duplicate quotes
New or Updated Spreadsheet Row also fires when a Zap writes back to the row. Use New Spreadsheet Row, or set a trigger column the Zap never writes to.
Values in the wrong column
Columns were renamed, moved or inserted after the Zap was built. Zapier warns this can cause unexpected results; remap the step.
Nothing happens
Rows added in the middle of a sheet don't fire New Spreadsheet Row, which watches the bottom. Add rows at the end of the sheet, or type into the next empty row.
What a good test leaves behind
After an end-to-end test of the quote log, the copy of the sheet should have one new row per event, each with the time, the document number, the client, the event and the amount, and nothing in the wrong column.
For the row-to-quote Zap, the test document should be a draft from the right template with every data item filled, the price rows you expect, and its number written back on the row.
The quote log recipe
| When | Document | Client | Event | Amount | Owner |
|---|---|---|---|---|---|
| Mon 19 Oct, 9:12 am | TP-2838 | Harlow & Finch | Sent | $6,380.00 | Tom Achebe |
| Mon 19 Oct, 3:40 pm | TP-2838 | Harlow & Finch | Viewed | $6,380.00 | Tom Achebe |
| Tue 20 Oct, 11:05 am | TP-2841 | Mara Quinlan | Sent | $14,950.00 | Elena Brooks |
| Tue 20 Oct, 6:50 pm | TP-2841 | Mara Quinlan | Viewed | $14,950.00 | Elena Brooks |
| Wed 21 Oct, 8:22 pm | TP-2841 | Mara Quinlan | Signed | $14,950.00 | Elena Brooks |
| Wed 21 Oct, 8:24 pm | TP-2841 | Mara Quinlan | Part paid | $3,737.50 | Elena Brooks |
| Thu 22 Oct, 9:30 am (row added by a Zap) | TP-2846 | Priya Raman | Sent | $8,558.00 | Elena Brooks |
| Thu 22 Oct, 7:48 pm (row added by a Zap) | TP-2846 | Priya Raman | Viewed | $8,558.00 | Elena Brooks |
| Fri 23 Oct, 6:15 pm (row added by a Zap) | TP-2846 | Priya Raman | Signed | $8,558.00 | Elena Brooks |
| Fri 23 Oct, 6:17 pm (row added by a Zap) | TP-2846 | Priya Raman | Part paid | $2,139.50 | Elena Brooks |
| Sat 24 Oct, 12:01 am | TP-2829 | Corvel Partners | Expired | $11,240.00 | Tom Achebe |
- Proposals
- Log
- Summary
Row added by a Zap
Test it with a free trial
QuoteCloud's Zapier app is on the Essentials plan and up. Start a free 14-day trial and test every Zap on a copy of your sheet.
Why test on a copy with fictional data?
A Zap that adds rows can add hundreds before anyone notices a mistake, and a Zap that creates documents can send them. Testing on a copy keeps the real sheet clean, and @example.com addresses mean a test document can never reach a client.
It also keeps costs predictable. Every document a Zap creates carries the per-document fee, test documents included, so build the row-to-quote Zap with a handful of test rows, not a full list.
- Leave Create Document's Auto Send Document off until the drafts look right.
- Archive test documents in QuoteCloud when you're done, so they stay out of your reports.
Troubleshooting questions
Why did my Zap create the same quote twice?
Usually because the trigger also fires on the Zap's own write-back. New or Updated Spreadsheet Row fires on any change to the row, including the document number the Zap writes. Use New Spreadsheet Row, or Updated Spreadsheet Row with a trigger column the Zap never writes to.
Why can't the Zap find the row?
Lookup Spreadsheet Row matches the value exactly. Check the Document column holds the number as QuoteCloud writes it, without spaces or a different format. QuoteCloud's own Find Document by Field also matches the whole value exactly, including capitals.
Why are new rows not starting the Zap?
New Spreadsheet Row watches for rows added to the bottom of the sheet. Rows inserted in the middle, or rows in a sheet on a shared drive with the standard trigger, won't start it. Add rows at the end, and use the Team Drive trigger for shared drives.
Do test documents carry the per-document fee?
Yes, if a Zap or the API creates them. Every document created through Zapier or the API carries the fee, so test the row-to-quote Zap with a few rows. Zaps that only add or update rows create no documents and carry no QuoteCloud fee.
More on QuoteCloud and Google Sheets
Six use cases with the exact Zapier steps, then how to connect, test and what it costs.
- Log every quote event in Google SheetsSent, viewed, signed, paid and expired: each QuoteCloud event adds a row, and sheet formulas turn the log into a report.
- Keep a quote pipeline tracker in Google SheetsOne row per quote: a Zap adds it when the document is created and updates its status as it changes.
- Create quotes from Google Sheets rowsA new row creates the document from your template, with the row's details in data items and price-table rows.
- Fill a price table from Google Sheets linesOne sheet row per product line: a Zap looks the lines up and adds them to the new quote's price table.
- Feed the product library from a Google Sheets price listKeep prices in the sheet you already maintain: a Zap creates or updates each QuoteCloud product from its row.
- Google Sheets or QuoteCloud's Spreadsheet block?Two different spreadsheets: your Google Sheet outside, the Spreadsheet block inside the quote, and how a Zap reaches each.
- Connect Google Sheets to QuoteCloud, step by stepCheck the plan, set up the sheet's header row, connect both apps in Zapier and test your first Zap.
- Google Sheets column mapWhich column each Zap on this site writes or reads, which way it travels and a sample value.
- What QuoteCloud with Google Sheets can and can't doWhat the Zaps do, where they stop, Zapier or Make, and what we haven't confirmed yet.
- What the Google Sheets connection costsEssentials and up for Zapier, plus a fee only for documents a Zap or the API creates. Logging rows is free.
- FAQAnswers to the questions teams ask before connecting QuoteCloud and Google Sheets.
Tested, then trusted.
Start a free 14-day trial, copy your sheet and test each Zap with fictional data before it touches the real one.