Question

Line Items configuration help.

  • 26 March 2022
  • 2 replies
  • 60 views

So I’m working to build a zapier integration for our service. The data payload we send has a few different sets of arrays which I understand zapier refers to as “Line Items” 

I cannot figure out to work with these for the life of me. For example, we return a “contact like object” that, for the sake of this conversation, looks like 

 

[
  {

     first_name: “jane”,
     last_name: “doe,
     email: “jane@email.com”,
  },

  {

     first_name: “john”,
     last_name: “doe,
     email: “john@email.com”,
  },
]



When I test the Zap, it sees the object and displays them as line items. But when I got to access the data, the first name key returns a comma-separated list of each object's first name. I.e. “jane, john”. This is useless. 

So I searched, found, and played with the Formatter tool and Looping by Zapier, but no matter what I do or how I configure these according to the docs, I still end up with the exact string. 

For example, I tried to dumb it down and make a google spreadsheet adding a row just like it outlines in this article: https://zapier.com/blog/formatter-line-item-automation/. I followed this exactly, and it didn’t work. The result was a single row added where first_name was “jane,john”

What am I missing? Why is this so difficult?


This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

2 replies

Userlevel 7
Badge +14

Hi @jonathansimmons 

Can you clarify if you are building a Zap that uses an app in a step OR if you are building a Zap app on the Zapier Platform?

I resolved this issue yesterday and did not hit submit on my resolution. 

​​​@Troy Tessalone, I’m referring to building a Zapier app. However, the specific issue was that a test zap would not enable. 

The issue was resolved by changing what my subscribe and unsubscribe webhooks returned.  
When I began, my subscribe endpoint was returning a simple 200 header. As it turns out, Zapier expects a complete JSON response from that endpoint. Once I started producing a JSON payload with a status, the zap was successfully enabled.