Skip to main content

My mistake with line items in Zapier (3 products, only 1 row in Google Sheets)

  • Nov 20, 2026 6:07 PM UTC
  • 1 reply
  • 22 views

Sharing this because I wasted more time on it than I would like to admit, and I keep seeing the same question here.

I had a simple Zap: new order comes in, add it to Google Sheets. It worked fine in testing. Then a real order came in with 3 products, and I got one row with "Shirt,Hat,Socks" squeezed into a single cell. The quantities were in one cell too, "2,1,1".

My mistake: I was using "Create Spreadsheet Row" (one row) and mapping the product fields straight into it. Zapier sends the products as line items, which is basically a list inside one field. When you put a list into a normal field, Zapier just joins it with commas.

I then tried to fix it with Formatter steps to split the text, which got messy fast. The real fix was much simpler.

How to avoid it:

  • If you want one row per product, use "Create Multiple Spreadsheet Rows" instead and map the same fields there. That was it for me. One step changed and every product got its own row.
  • If you need to do something for each product (create a task, send a message), add Looping by Zapier with "Create Loop From Line Items". The steps after it run once per product.
  • If you just want a readable list in an email or Slack, use Formatter > Utilities > Line-item to Text and choose a separator like a new line.

One more thing I learned the hard way: test with an order that has more than one product, and ideally one with an empty field (like no size). My test order only had one product, so I never saw the problem until it was live.

Has anyone else run into this? Curious what tripped you up the first time.

1 reply

MahdiEqbal
  • New
  • Nov 21, 2026 1:06 PM UTC

One extra check I'd add is verifying the result after the rows are created

For each order, compare the expected line-item count with the number of rows actually written to Sheets, using the order ID to group them.

I'd also check that the quantities and product IDs still match the original items, especially when some optional fields are empty.

That catches cases where the Zap runs successfully but the destination data is incomplete or misaligned