Having trouble sending my column data via HTTPI over to my CRM platform that has custom Fields and IDs. This is the response I get.
To resolve issues with sending column data via HTTP API to your CRM with custom fields and IDs, consider these steps: 1. Ensure field type matching: Make sure the data types in your Clay table match those in your CRM to avoid export errors. 2. Map fields correctly: When setting up the integration, carefully map your Clay columns to the corresponding CRM fields, including custom fields. 3. Use correct identifiers: Specify the record ID or a unique identifier (like email) for updating existing records. 4. Check JSON formatting: Since you're using HTTP API, ensure your JSON is correctly formatted. Could you please copy and paste the JSON you're using into the chat? This will help us troubleshoot further. If you need more assistance, please request human help by clicking on "Talk to a person".
Hi Doug, thanks for reaching out! It looks like the error is coming from the setup of your JSON body in the HTTP API column. The most common reason for Failed to Parse body errors is due to incorrect formatting of your variables and fields. Can you make sure all text and url strings are enclosed in ""? It should be "variable name": "/NameOfField" Here's a guide with more info: https://downloads.intercomcdn.com/i/o/w28k1kwz/1505818170/1c3512058a260d47315ff09315e5/674e8159dbe3f02599bbb8c2_671bf586cb568f0abaa57230_671bf3aef7555fff24ac5569_CleanShot-2525202024-10-25-252520at-25252014_32_33.avif?expires=1746228600&signature=1240b290327892f33bc8b4948e0670da6aff9b55035ff055c341998ced461e96&req=dSUnE8F%2FlYBYWfMW1HO4zd18HknimVIC3fQvxvuNenLjseT9%2BMtKaoQhM6g%2F%0AYmIz%0A
If this doesn't fix your error, do you mind sending the specific documentation for this endpoint you're trying to call?
Hi Tanvi R. I updated the JSON body and the lead went through but only 2 columns had data. Not sure why the others did not go through. Here's the API documentation. https://public-api.gohighlevel.com/#0097b747-33c2-452f-8c78-aab5ab36c071
Hey! Can you let us know which specific data didn’t go through and which row it was? Usually, if values are missing, it’s because those fields were empty at the time of the request. From what I see on our end, everything seems to be working correctly.
I've updated the code again just now. it appears it's all the custom Fields after the first one. There must be a different way to enter multiple custom Fields in the same string.
Hey, I checked the payload and saw that only the first custom field was getting through—this was due to incorrect formatting.
I copied your body into GPT and asked it to correct it. Here’s the fixed version: LBKS{ "email": "Email", "firstName": "First Name", "lastName": "Last Name", "companyName": "Company Name", "customField": { "HQsleliXRbq6sOEYQFQc": "Linkedin Profile URL", "ACBPRiyRuAGH2RmLz2hy": "Contact Source", "jnn2Zt3N46sf0sZiUbMe": "Recruiter Job Title", "aLMofnIHaOnLMZBMSmwp": "Job Posting URL", "D9ubcrE2biG68B5sD1sw": "Job Title For Hire", "pdE1kFKl26U9Polofd7D": "Domain", "vojFyJkjTsxYGWXtx2pK": "Job Poster" } }LBKS
Let me know if you need help testing this.
Worked like a charm! Thanks a ton!