I'm trying to use Kitt for emails and im having the following error when running: Failed to parse body input this is the code for the body: { "fullName": NormaliseFullNameParse , "domain": Company Domain , "realtime": true } Here is the workbook: https://app.clay.com/workspaces/443643/workbooks/wb_9tHV7fsip34Z/tables/t_GgbQbsYhv7hb/views/gv_55uFmuM3QJ8F Can you please help me get this right? I copied it from another workbook where it's working fine
The "Failed to parse body input" error typically occurs due to JSON formatting issues in the Body section of your HTTP API enrichment. To help you fix this, please copy and paste your exact JSON code into the chat. Common causes include:
1. Missing double quotes around keys and string values
2. Incorrect use of commas
3. Extra spaces or hidden characters
For example, your code should look like this: LBKS{ "fullName": "NormaliseFullNameParse", "domain": "Company Domain", "realtime": true }LBKS
Once you share your JSON, I can provide more specific guidance to resolve the error.
{ "fullName": NormaliseFullNameParse , "domain": Company Domain , "realtime": true }
The "Failed to parse body input" error is likely due to JSON formatting issues in your HTTP API enrichment. To fix this, we need to address the following in your provided JSON:
1. Add double quotes around keys and string values
2. Remove extra spaces
3. Ensure correct use of commas
Here's the corrected JSON: LBKS{ "fullName": "NormaliseFullNameParse", "domain": "Company Domain", "realtime": true }LBKS
If you're still encountering issues, please copy and paste your exact JSON code into the chat so I can provide more specific guidance.
Add double quotes to Clay fields and try again. It should work Basically { "fullName": "NormaliseFullNameParse", "domain": "Company Domain", "realtime": true }
To resolve the "Failed to parse body input" error, you need to fix the JSON formatting in your code. Here's the corrected version: LBKS{ "fullName": "NormaliseFullNameParse", "domain": "Company Domain", "realtime": true }LBKS
Key changes:
1. Added double quotes around keys and string values
2. Removed extra spaces
3. Changed "realtime" value to boolean (true instead of "true")
These modifications should resolve the parsing error. If you're still experiencing issues, please copy and paste your exact JSON code into the chat so I can provide more specific guidance.