Skip to main content
Best answer

Zapier changed the way how to parse JSON

  • February 8, 2021
  • 3 replies
  • 2852 views

I recently notice Zapier changed the way how to parse JSON data, I have JSON data like:

{

User:{

FirstName:’John’,

Address:{

City:’Toronto’

}

}

}

before Zapier flat data to User_Address_City, but now, first level and second level is fine, but city not able to be find as token.

 

Instead change our data model, is there easy way to change settings and make it work. thanks.

 

Best answer by SamBBest answer by SamB

Just wanted to follow up here to add that it appears that the second level of JSON data that isn’t being parsed correctly is nested JSON data.

For anyone that’s also having issues parsing nested JSON data, there’s a related article in Community that talks about how to parse nested JSON data that would be helpful :)
 

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

GetUWired
Forum|alt.badge.img+12
  • Zapier Expert
  • 1030 replies
  • February 10, 2021

Hi @dzhu2005 

What app are you using? Are you retrieving this data from a webhook action? 


  • Author
  • Beginner
  • 3 replies
  • February 19, 2021

Hello, I created another question, maybe the new one is more easy to understand.

 

My app is Scarlett Network - BETA


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7472 replies
  • Answer
  • September 22, 2021

Just wanted to follow up here to add that it appears that the second level of JSON data that isn’t being parsed correctly is nested JSON data.

For anyone that’s also having issues parsing nested JSON data, there’s a related article in Community that talks about how to parse nested JSON data that would be helpful :)