Automatically Mapping JSON Keys to Columns in Clay | Clay

Automatically Mapping JSON Keys to Columns in Clay

Hello! Is there a built-in way for Clay to automatically detect a text field containing JSON and allow me to quickly select which JSON keys to use for creating individual columns, similar to the parent/child column workflow? Here’s the context:

I have an HTTP API enrichment that returns a text field in JSON format.
Currently, I manually use formulas (like JSON.parse) to extract each key/value pair.
I’d like Clay to recognize the JSON structure and let me easily map JSON keys (for example, “company_name”, “all_products_reviewed”, “product_description”, etc.) to their own columns.

Any guidance or recommended configuration for this would be greatly appreciated! Thank you!

14 comments

Channeled
APP
·
·
Yes, when you have data from an enrichment that returns JSON or nested data, you can easily create individual columns from specific endpoints. Here's how: 1. Click on the cell containing your JSON data to open the Cell details panel 2. Hover over the specific JSON key/endpoint you want to use 3. Click Add as column on the right 4. Enter a description for your new column 5. Click Create column to generate the individual columnFor HTTP API responses specifically, you can also use the "Field Paths to Return" option when setting up the enrichment to specify which JSON fields you want to retrieve. For nested parameters, use dot path notation (e.g. object1.object2.name). Sources: Table columns overview | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Channeled
APP
·
·
Was that helpful?
Brian
·
·
Hm, I can’t follow this approach because Clay is recognizing it as text rather than as structured data. So it seems like the solution is to have the HTTP API response be recognized as JSON, instead of just returning text in JSON notation. Can you point me to a resource to show me how to do that?
Channeled
APP
·
·
To ensure your HTTP API response is recognized as JSON, you need to properly set up two key components: 1. Set the Content-Type header: • Add a header with Content-Type: application/json in your HTTP API enrichment setup 2. Use the "Field Paths to Return" option: • Specify the JSON fields you want to extract • For nested data, use dot path notation (e.g., object1.object2.name) • Separate multiple field paths with commasIf you're still seeing parsing issues, verify that your API response follows proper JSON formatting: ** Strings must be in double quotes ** Keys must be properly separated by commas * No trailing commas at the end of objects Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT Authentication with Clay
Channeled
APP
·
·
Is that what you were looking for?
Channeled
APP
·
·
Hi Brian! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Brian
·
·
Confirming that Content-Type: application/json is set up in the HTTP API enrichment setup
I’ve tested the JSON response to confirm proper formatting
I tried using the “field paths to return” option, but it gave me an empty result
If helpful, I can provide as screenshot of what the Cell Details looks like in clay, so you can see the JSON key and value pairs look like in the text format:
Channeled
APP
·
·
To ensure Clay properly recognizes your HTTP API response as JSON, follow these troubleshooting steps: 1. Verify your API response formatting: • Ensure all strings are in double quotes • Check that keys are properly separated by commas • Remove any trailing commas at the end of objects 2. In the HTTP API enrichment setup: • Confirm Content-Type is set to "application/json" in headers • Use the "Field Paths to Return" option to specify which JSON fields you want to extract • For nested data, use dot path notation (e.g., object1.object2.name)If you're still experiencing issues, try validating your JSON response using a tool like JSONLint to identify any formatting problems.If the JSON is valid but Clay still isn't recognizing it properly, you may need to request human support to investigate further. Sources: HTTP API integration overview | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API with JWT Authentication with Clay
Channeled
APP
·
·
Did that answer your question?
Channeled
APP
·
·
Looks like you're still looking for help. We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Brian
·
·
Thank you — here’s the URL: https://app.clay.com/workspaces/407055/tables/t_ZGUaUENJkyv3/views/gv_zu32WsqaBVaT
Owen C.
·
·
Hey Brian, thanks for reaching out! Just to confirm, what would be difference in having these values be individual outputs returned in the HTTP API column versus parsing this response with formulas columns as what's already done in the table?
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.