Description
Summary I need an experienced Make.com automation/API specialist to fix one issue in an existing Make.com scenario. The automation connects: Tally form → Make.com → Lofty CRM API Most of the workflow already works. Please do not rebuild it from scratch. The current issue is with one HTTP module in Make.com: HTTP 6 — POST [https://api.lofty.com/v1.0/notes](https://api.lofty.com/v1.0/notes) This module posts notes into Lofty for existing contacts. It is failing with this error: “Bad control character in string literal in JSON” “InvalidConfigurationError” “The provided JSON body content is not valid JSON” The issue appears to be caused by Tally form answers that contain hidden characters such as line breaks, carriage returns, tabs, or pasted text that is breaking the JSON body. What I need done: 1. Review the existing Make.com scenario. 2. Fix only HTTP 6’s Body content. 3. Sanitize all free-text Tally fields inside the JSON note body. 4. Make sure the JSON body remains valid. 5. Do not change the existing workflow logic unless absolutely necessary. 6. Do not rebuild the scenario. 7. Do not change the API token, router, lead creation module, or other working modules. 8. Test the failed run or process the queued record. 9. Confirm the Lofty note posts successfully. 10. Confirm the scenario remains active. Important context: The scenario already handles: * Tally form submissions * Searching Lofty by email * Creating new leads * Adding Source = FundMyKeys * Adding Lead Type = Buyer * Adding Segment = Real Money Survey * Posting full survey answers into Lofty notes The current problem is specifically the existing-contact note module, HTTP 6. You should have experience with: * Make.com / Integromat * HTTP modules * JSON body formatting * API request troubleshooting * Escaping or sanitizing JSON string values * Working with Make.com blueprints * Tally or form-based automations * CRM API integrations Ideal fix: Sanitize risky mapped Tally fields using Make functions such as replace(), split(), join(), char(), or the correct Make-supported equivalent to remove or replace: * newline characters * carriage returns * tabs * hidden pasted characters Please only apply a targeted fix. I do not want the scenario rebuilt. Deliverables: * Fix HTTP 6 Body content * Confirm the failed JSON error is resolved * Confirm queued records process successfully * Confirm Lofty note is posted * Confirm the scenario is Active * Briefly explain exactly what was changed Please only apply if you are strong with Make.com HTTP modules and JSON body debugging. Please do not apply if you plan to rebuild the scenario. This is a targeted debugging job only.