Description
Summary Description: We have a conversational agent built in n8n that connects to GoHighLevel (GHL) through the official GHL API (coexistence with the official WhatsApp Business API). The agent works correctly for text messages, but we have a specific bug when sending media files (images, audio, video — the issue is the same across all formats). The problem: We send the request to the GHL messaging endpoint with: type: WhatsApp, contactId, message (used as caption) and attachments (public URL, WhatsApp-supported format, already verified). If we send with a caption: the message arrives, but only the text (caption) shows up — the image does NOT reach the GHL UI or WhatsApp. If we send without a caption: nothing arrives at all. n8n doesn't throw any error — the request processes "successfully," but the file never reaches the destination number on WhatsApp. Everything points to GHL parsing/processing the attachment but failing to forward it correctly to the WhatsApp API. What we've already tried: Verified that the file's format and URL are valid and publicly accessible (confirmed). Tried using the official WhatsApp nodes in n8n for more flexibility — but this requires connecting the number via a Meta Developer App, and if the phone is connected there, it can't be connected to GHL at the same time (exclusive connection conflict). What we're looking for: Someone who already knows the root cause and the fix for this specific issue — we're not looking for someone to come in and investigate or trial-and-error their way through it. If you've worked with GHL in coexistence mode with the official WhatsApp Business API and have run into this bug (or a similar one) with attachments not going through, we want to talk to you. You should be able to tell us upfront: What's causing the attachment to not be forwarded to WhatsApp even though GHL processes it. How to fix it (payload adjustment, headers, account configuration, or whatever it takes). Implement the fix and confirm it with a real end-to-end send. We have a video explaining the issue in more detail, shared upon hiring. https://www.loom.com/share/149c24f9a07642d88924d4abc24cc6e0