Using Zapier trigger for Firestore inserts produces a JSON error (‘unexpected }’). I’ve tried variations with a new query as shown:
"sortBy": [{
"attribute": {
"path": "createdOn"
},
"sortOrder": "ASCENDING"
}]
How can I view or fix the JSON?
The error I encountered was similar to what your thread describes. In my case the issue turned out to be due to invisible whitespace issues introduced by copy-pasting JSON from an external editor. After retyping the section manually, the error disappeared. I recommend trying to reformat the JSON in a simple text editor to detect any hidden characters that might be misinterpreting the JSON structure. Additionally, comparing the working JSON structure with your problem section helped me identify discrepancies that might not be evident on a casual code review.
I encountered a similar problem while integrating Firestore with Zapier some time ago. It turned out that the error ‘unexpected }’ was caused by a small syntax error in the JSON that was easy to overlook. When I revisited my configuration, I found an extra comma that resulted in an unexpected bracket closure. Running the JSON through a validator helped pinpoint the mistake. I suggest verifying that every object and array conforms exactly to valid JSON without device-specific trailing punctuation or misaligned brackets, as this approach helped resolve my issue.
In my experience, the root of these JSON errors often lies not in the obvious syntax but in hidden characters. I once battled an error similar to the one you described while integrating Firestore with Zapier. In my case, the problem was due to some non-printable characters that crept in when the JSON was transferred between different editors. I resolved it by pasting the code into a basic text editor and then copying it into an online JSON validator, which made the issue apparent. Ensure that the editor you use does not introduce any unintended formatting.
hey, i had a sim issue with misplaced commas in my json. i retyped it in a basic editor and spotted a stray bracket. maybe a simple re-check of quotes and commas will clear it up.