Inconsistent JSON Output from Clay Table APIs: Need Guidance
Hi Team, I am having an issue with my Clay table, can someone please take a look? Workspace/Table: https://app.clay.com/workspaces/542459/workbooks/wb_0szjcdiYiXyviEFZJqD/tables/t_0szji6wDejRxCCye8Rw/views/gv_0szji6wwfu6ycrh2Zwe Columns involved:
Hubspot Lead Creation API ā returns the entire JSON wrapped in a single value field (desired).
Update Sureconnect HTTP API ā returns individual key/value fields (problematic).
Configuration (both columns):
Field Paths to Return / Response values to return: empty for both columns.
Expected behavior (per docs/support guidance):
When āField Paths to Returnā is empty, Clay should return the entire JSON as a single value field.
When specific field paths are listed, Clay should return only those fields expanded.
Actual behavior:
Despite the setting being empty in both columns, one column returns value (desired), while the other expands all fields. This inconsistency is causing downstream JSON parsing issues.
Impact:
I forward Clay outputs through a Make.com webhook to my server. The differing shapes ({ "value": "<json>" } vs expanded fields) break parsing and require special casing.
Steps to reproduce:
- 1.
Open the table (link above).
- 2.
Compare outputs from Hubspot Lead Creation API and Update Sureconnect HTTP API columns.
- 3.
Note that both have āResponse values to returnā empty, but their outputs differ as described.
What I need:
Confirmation whether this is a bug or if there is another setting that controls whether the response is wrapped in value vs expanded (e.g., a column-level toggle, response handling, content-type expectation, etc.).
Guidance on how to force both columns to consistently return the full response in a single value field.
Contact: murugan@zams.com Optional example (shape only):
Desired: { "value": "{...full JSON string...}" }
Current (problematic): { "company": "...", "domain": "...", ... }