1What it does
A builder wired inbound GHL SMS to a Make webhook, got a good OpenAI reply, then hit a 422 'no message' error sending it back. The fix: escape the AI text before mapping it into the JSON body.
2Who it is for
- Industry
- Any local business
- Platform
- HighLevel and Make together
- Category
- Conversation AI
- Tools used
- HighLevelMakeOpenAILeadConnector API
3How it works
Every step, in order, is in Workflow at a glance, pinned on the right as you scroll.
- 01 Trigger
Inbound SMS in HighLevel (workflow webhook).
- 02 Action
Webhook to Make.
- 03 AI / action
OpenAI module writes the reply.
- 04 Action
Transform to JSON (or Create JSON) on the reply text.
- 05 Action
HTTP POST to the LeadConnector Conversations API with type SMS, contactId and message.
- Trigger
- Inbound SMS in HighLevel (workflow webhook).
- AI step
- Any reply prompt.
4How it went
The webhook and OpenAI parts worked. Sending back failed with 422 until the text was escaped, per the Make community answer.
Only what the source reports. The source did not report numbers.
5Worth knowing
- AI text has quotes and line breaks that break raw JSON.
- 'Transform to JSON' output already includes the quotes. Do not wrap it in another pair.
6Recipe
Creator's settings Taken from the source as published.
Body: {"type": "SMS", "contactId": "{{1.contact_id}}", "message": {{4.json}} }
where module 4 is Transform to JSON on the OpenAI text.
Or inline: {{ replace(replace(3.text; "/([""\\])/g"; "\$1"); "/\r?\n\r?/g"; "\n") }}7Source
Open the original Make Community by @MomBossAi, answer by @samliew →
Source opened and read on 2026-10-11.