Impossible to send whatsapp templates #12330
|
Hi everyone! Is anyone able to send WhatsApp templates using the ChatWoot API? I wasted the whole afternoon trying in the most diverse ways and nothing... And look, I'm trying using the simplest pattern that exists, the "Hello World" created by Meta itself... I am using this endpoint: /api/v1/accounts/{account_id}/conversations The JSON is this: The message is created correctly within the conversation, and I can view it. However, it never reaches the user. It only appears in ChatWoot. 
I'm going crazy with this, can anyone help me? Edit: Version v4.5.2 |
Replies: 4 comments · 5 replies
|
@rpetribu which channel provider are you using ? |
|
WhatsApp Cloud. |
|
Ok, I found an old post here #5958 where @munawar050 manage to solve this using a code that is not in Chatwoot's API documentation. And miraculously it works. So, I am now facing another problem. Templates are only sent correctly if:
OR
This makes no sense at all. All templates are approved by Meta. I can even send them normally via API to Meta and through ManyChat. I would really like to know if anyone is able to use this feature normally, I am willing to pay for someone to be able to guide me.... |
|
@rpetribu thanks My template messages go irrespective of the conversation status (open close etc) |
|
@rpetribu We’ve recently made some updates to WhatsApp templates, you can find the guide here. Please also review the API documentation too ensure you’re using the correct flow. Could you check if anything is missing or unclear in the docs and let us know? |
|
Thank you @munawar050 and @muhsin-k for your help. I modified the code I was using following your instructions. I'm using n8n and sending a POST to open a conversation with a template using this API documentation. The code I'm using is this: 
The message isn't being sent, likely because the open conversation hasn't had any interaction with the contact in the last 24 hours. This doesn't make sense, as it's a template already approved by Meta. I tried to change the approach and, instead of creating a conversation, I tried to create a message. To do this, I divided the action into two steps.
POST: https://[MY URL]/api/v1/accounts/1/conversations/
POST: https://[MY URL]/api/v1/accounts/1/conversations/[ID CREATED ABOVE]/messages The result.... the same. Now, if the contact send me a message and i pick this conversation ID, I can send the template using the code above to that conversation. 
POST: https://[MY URL]/api/v1/accounts/1/conversations/32/messages 
And I also received the tempalte in my Whatsapp.... In short... The template only sends if I create a message in an already open conversation with the contact. Otherwise, it doesn't send. Using the Chatwoot UI, I'm getting it working normally, without any issues. |
|
Guys, I finally managed to resolve the issue, which was occurring due to incorrect information in the API documentation, which I humbly suggest be updated. This link provides instructions on how to CREATE a conversation. One of the required parameters is the source_id: 
The thing is, this parameter is not required (at least when trying to send a template) and if you try to generate any random number just to not sent it in blank, it will result in error. What I did was simply not send it. I used the same code shown above. The only difference was that I didn't send the source_id: It worked! Thanks again for your help. |
|
Was just about to mention this, glad you found the resolution |
|
Sending WhatsApp templates with dynamic URL buttons via Chatwoot API + n8n After hours of debugging, I found the correct format to send WhatsApp templates with dynamic URL buttons through the Chatwoot API. The official documentation does not cover this correctly. The problem The The solution Use the endpoint {
"message_type": "outgoing",
"private": false,
"content_type": "text",
"content": "Your message text here",
"template_params": {
"name": "your_template_name",
"category": "UTILITY",
"language": "pt_BR",
"processed_params": {
"body": {
"variable_name": "value"
},
"buttons": [
{
"type": "url",
"parameter": "dynamic-url-suffix",
"url": "https://yourdomain.com/{{1}}",
"variables": ["1"]
}
]
}
}
}Key points
How I found this The official docs were wrong. I inspected the actual network request made by the Chatwoot UI when sending a template manually via DevTools → Network → Fetch/XHR → Payload, and replicated the exact format. Chatwoot version: 4.12.1 É só copiar e colar no GitHub! Vai ajudar muita gente que passar pelo mesmo problema. 🚀 |
Guys, I finally managed to resolve the issue, which was occurring due to incorrect information in the API documentation, which I humbly suggest be updated.
This link provides instructions on how to CREATE a conversation.
https://developers.chatwoot.com/api-reference/conversations/create-new-conversation
One of the required parameters is the source_id:
The thing is, this parameter is not required (at least when trying to send a template) and if you try to generate any random number just to not sent it in blank, it will result in error.
What I did was simply not send it. I used the same code shown above. The only difference was that I didn't send the source_id: