Changes to HTTP API Actions - Improved JSON parsing, new guidelines for new columns
⚡ Changes to your HTTP API Actions ⚡ - Hey Everyone! We just made a change to HTTP API actions to fix some issues with parsing JSON bodies. Here’s what you need to know about the changes:
- 1.
We now added a query string input where you can input key value pairs and everything will be automatically URL encoded
- 2.
We now, automatically JSON stringify Column tokens in your body JSON, to avoid failed to parse your body input issues when a piece of text has a character like quotes. This means that tokens in Clay should no longer be wrapped in quotes. See below for an example.
In order to make these changes, we had to make a new version of the HTTP-API action, so your existing workflows will continue to work as is. However, any new HTTP-API columns will require you to follow these new guidelines. cc Chris F. Nathan L. Mike R. dan (. Elliot T. and others that have consistently noticed Failed to parse body input issues.