Troubleshooting Unmapped JSON in Send Table Data Action

Peter N. · 2025-07-01 15:31:25.342571+00

Hi there! I'm having trouble with a "Send table data" action. I've got a table that receives information from Calendly, then I'm mapping the contact data into a unified contacts table. My field names match exactly (including case) but they end up in unmapped JSON. When I look at the raw JSON from the unified contacts record, the key values match. What could be wrong here?

Troubleshooting Unmapped JSON in Send Table Data Action | Clay

7 comments

· Sorted by newest

Anaum K.
·
·
Hello Peter! I'm glad you were able to figure it out! I'll go ahead and close out this ticket now, but don't hesitate to reach out again if you need any help in the future.
Peter N.
·
·
I figured it out
Peter N.
·
·
https://app.clay.com/workspaces/435571/workbooks/wb_0syovt7bUg3EkFTrWZz/tables/t_0syozoxcKGrTD5CcoSV/views/gv_0syozoyWSnGaiGEpZ9W
Peter N.
·
·
I'm not sending JSON, I'm using the send table data function. Fields are mapped and correctly reflect the target field
Clay
APP
·
·
Looking at your JSON data, the issue is likely that you're sending the entire JSON object as a single value rather than mapping individual fields. The "Send table data" action creates a new row on first send, then updates that same row for subsequent sends. Your JSON shows structured data with individual fields like "email", "first_name", "last_name", etc. To properly map these, you need to: 1. In your "Send table data" action, select individual columns from your source table 2. Map each field (email, first_name, last_name, etc.) to corresponding columns in your unified contacts table 3. Avoid sending the raw JSON object itself The action should map specific column values, not the entire JSON structure. Check your column mapping configuration to ensure you're selecting individual data fields rather than a JSON column.
Source: Send table data | Documentation | Clay University
Peter N.
·
·
JSON: { "size": "", "email": "test@test.com", "origin": { "type": "row", "tableId": "t_0syozoxcKGrTD5CcoSV", "recordId": "r_0syq59oXHvsGoMrUEJS" }, "request": "Test", "industry": "", "last_name": "is", "created_at": "2025-06-02T15:44:16.394Z", "first_name": "test", "hear_about": "Google / Search", "utm_source": "", "company_name": "Rise Productive LLC", "referrer_url": "https://api.calendly.com/routing_form_submissions/67afd845-85a5-442c-9b0c-ef9898f12ec2", "utm_campaign": "", "signal_source": "Calendly Demo" }
Clay
APP
·
·
When using "Send table data" in Clay, data ending up as unmapped JSON typically indicates a formatting or mapping issue during the transfer process. The "Send table data" action creates a new row in the destination table on first send, then updates that same row for subsequent sends. This behavior could cause data to accumulate as JSON if the mapping isn't properly configured. Since you mentioned JSON formatting issues, could you copy and paste the actual JSON data that's appearing in your unified contacts table so I can help troubleshoot the specific formatting problem?
Sources: Send table data | Documentation | Clay University Send table data | Documentation | Clay University Send table data | Documentation | Clay University

Loading comments

Anaum K.
·
·
Hello Peter! I'm glad you were able to figure it out! I'll go ahead and close out this ticket now, but don't hesitate to reach out again if you need any help in the future.
Peter N.
·
·
I figured it out
Peter N.
·
·
https://app.clay.com/workspaces/435571/workbooks/wb_0syovt7bUg3EkFTrWZz/tables/t_0syozoxcKGrTD5CcoSV/views/gv_0syozoyWSnGaiGEpZ9W
Peter N.
·
·
I'm not sending JSON, I'm using the send table data function. Fields are mapped and correctly reflect the target field
Clay
APP
·
·
Looking at your JSON data, the issue is likely that you're sending the entire JSON object as a single value rather than mapping individual fields. The "Send table data" action creates a new row on first send, then updates that same row for subsequent sends. Your JSON shows structured data with individual fields like "email", "first_name", "last_name", etc. To properly map these, you need to: 1. In your "Send table data" action, select individual columns from your source table 2. Map each field (email, first_name, last_name, etc.) to corresponding columns in your unified contacts table 3. Avoid sending the raw JSON object itself The action should map specific column values, not the entire JSON structure. Check your column mapping configuration to ensure you're selecting individual data fields rather than a JSON column.
Source: Send table data | Documentation | Clay University
Peter N.
·
·
JSON: { "size": "", "email": "test@test.com", "origin": { "type": "row", "tableId": "t_0syozoxcKGrTD5CcoSV", "recordId": "r_0syq59oXHvsGoMrUEJS" }, "request": "Test", "industry": "", "last_name": "is", "created_at": "2025-06-02T15:44:16.394Z", "first_name": "test", "hear_about": "Google / Search", "utm_source": "", "company_name": "Rise Productive LLC", "referrer_url": "https://api.calendly.com/routing_form_submissions/67afd845-85a5-442c-9b0c-ef9898f12ec2", "utm_campaign": "", "signal_source": "Calendly Demo" }
Clay
APP
·
·
When using "Send table data" in Clay, data ending up as unmapped JSON typically indicates a formatting or mapping issue during the transfer process. The "Send table data" action creates a new row in the destination table on first send, then updates that same row for subsequent sends. This behavior could cause data to accumulate as JSON if the mapping isn't properly configured. Since you mentioned JSON formatting issues, could you copy and paste the actual JSON data that's appearing in your unified contacts table so I can help troubleshoot the specific formatting problem?
Sources: Send table data | Documentation | Clay University Send table data | Documentation | Clay University Send table data | Documentation | Clay University