v4.5.0

[sojan-official]

Changelog

• Suppot for media templates in whatsapp
• Ability to sync whatsapp templates manually
• Ability to onboard existing business numbers via whatsapp embedded signup
• Automation rules support for conversation_resolved event
• Multiple attachments support for Slack integration
• Custom OpenAI endpoint config for Captain
• Bug fixes and performance improvements
• New Languages
  • Bulgarian

Thanks to @hahuma, @clairton, @victoreduardo for the contributions

---

This discussion was created from the release v4.5.0.

[LucasLeandroBR]

Issue on add the chat widget #12252 on version 4.5

[javierreyesmonterroza1481-droid]

Chat de WhatsApp con Jhony Medina Calvo-Organized.pdf

[fernandescontabilidade]

The "media_name" variable (filename in api cloud whatsapp) was missing inside the "header" to prevent the files from being left without a name, as shown in the image. When the client saves the file, the name becomes the entire text content of the model. You should use the same variables as the WhatsApp API, this way it would be transparent and everything would work without errors.

[muhsin-k]

The "media_name" variable (filename in api cloud whatsapp) was missing inside the "header" to prevent the files from being left without a name, as shown in the image. When the client saves the file, the name becomes the entire text content of the model. You should use the same variables as the WhatsApp API, this way it would be transparent and everything would work without errors.

@fernandescontabilidade Could you please share both your template(use the below CURL request) and the specific message you're trying to send? We'll take a look at it.

curl --location 'https://graph.facebook.com/v20.0/{{business_account_id}}/message_templates?access_token=<access_token>'

[fernandescontabilidade]

The error occurs in any template, even this simple template that sends only a .PDF document in the header.

To reproduce the problem: 1. Send a PDF via template. 2. View the template in the client. 3. PDF name: no title. 4. When saving the PDF: the name will be the entire body content, due to the absence of a filename in the header.

{
"name": "envio_documentos_servicos",
"parameter_format": "POSITIONAL",
"components": [
{
"type": "HEADER",
"format": "DOCUMENT",
"example": {
"header_handle": [
"https://scontent.whatsapp.net/v/t61.29466-34/420523356_1770261516827279_2318285257630979791_n.pdf?ccb=1-7&_nc_sid=8b1bef&_nc_ohc=-PQhtjSL0JcQ7kNvwGGs_5Q&_nc_oc=AdlUgV1_O0JUGacUVuPLMewE3pzr_eyUvuwlA95z5FsaMb7ksfwTSG0Alv1clmuMgyH6A8lP4JQjCgbovQZstrHL&_nc_zt=3&_nc_ht=scontent.whatsapp.net&edm=AH51TzQEAAAA&_nc_gid=Z0pbCbRa6Rj3etH4m86hBQ&oh=01_Q5Aa2QFl6dbwLmXB3BjDbmg3Wkng4R9__55uRWQj4Jul9VMP-w&oe=68CFBC8A"
]
}
},
{
"type": "BODY",
"text": "Caro cliente voc\u00ea est\u00e1 recebendo o(s) documento(s) pertinente(s) ao(s) servi\u00e7o(s) solicitado(s)."
},
{
"type": "FOOTER",
"text": "Fernandes Contabilidade - Servi\u00e7os e Solu\u00e7\u00f5es Premium"
}
],
"language": "pt_BR",
"status": "APPROVED",
"category": "UTILITY",
"id": "1770261513494047"
},

[muhsin-k]

The document link is just an example, I changed the real link to a fake one to post here.

{ "content": "Caro cliente você está recebendo o(s) documento(s) pertinente(s) ao(s) serviço(s) solicitado(s).", "message_type": "outgoing", "template_params": { "name": "envio_documentos_servicos", "language": "pt_BR", "processed_params": { "header": { "media_url": "https://baserow.fernandescontabilidade.com/media/user_files/lBWKm8sZ24l7JLkz5V253Yt0RWG4ypfu_e5a8419c8e6f9a3e58d868bd065f4a4d7cea6a30b4716c380a9b0e1628596d9f.pdf", "media_type": "document" } } } }

Got the issue here. We will adding a fix for the same.

[fernandescontabilidade]

Important: filename is only accepted in the Whatsapp Cloud API if the media type is: document. For images to be placed, an error occurs in the API, so this must be handled depending on the type of media.

[muhsin-k]

Important: filename is only accepted in the Whatsapp Cloud API if the media type is: document. For images to be placed, an error occurs in the API, so this must be handled depending on the type of media.

Yes. Tracking via #12284

[fernandescontabilidade]

Using part of the link as the file name instead of "media_name" is bad because the file may often have a long name by default: ("https://baserow.fernandescontabilidade.com/media/user_files/lBWKm8sZ24l7JLkz5V253 Yt0RWG4ypfu_e5a8419c8e6f9a3e58d868bd065f4a4d7cea6a30b4716c380a9b0e1628596d9f.pdf"); It is much better to allow a "media_name" variable, so that it is possible to give any name, as occurs in the Whastapp cloud API. Example: customer_charge.pdf

[muhsin-k]

#12462