I had a Zap working successfully, and now it’s throwing this error:
invalid json response body at https://functions.prod.internal.glideapps.com/api/apps/1owJSHcd2cg1YqNV1Fab/tables/native-table-4lhcNq5YCOgXiRFQCWkK/rows reason: Unexpected token < in JSON at position 0
Not sure if it has to do with the inputs or something on Glide’s side. I don’t see any characters that need escaping in the values being sent to Glide.
That usually means that the JSON is malformed. Do you have a < character somewhere that doesn’t belong?
No, the inputs are just dates, Row IDs, and plain text that doesn’t include < / , etc.
This is using the new Glide Tables integration, not the API directly, BTW.
Do you have any single or double quotes in any of your values?
I don’t. But it’s not clear to me why that should matter in this case. When I was using the API to add rows, right before the Glide Tables integration came out, I used Zapier formatting steps to deal with special characters. But now with the Zapier integration directly to Glide Tables, I have a different Zap that adds rows to Glide tables and it handles double quote marks just fine without any extra formatting steps. This Zap was working and yesterday it stopped.
In programming languages, a string of text usually begins and ends with single or double quotes. I’ve seen plenty of times where something as simple as an apostrophe in a name can throw everything out of whack (ex. O’Reilly) because it prematurely ends the text string. That’s why proper escaping is so important, and why I asked if you had any single or double quotes which would include apostrophes. It was only a thought of something to check. Dates and RowID’s should be pretty stable, but text is unpredictable.
Other than that, it’s hard to say without seeing the actual JSON or the inputs. You may need to create a support ticket.
I ran into that using the API, because we use " for inches in most of our description fields. But my other Zap handles that just fine, so I know it is at least possible for the Glide Tables integration to not require escaping quote marks. I’ll try filing a ticket.