Looking at your issue with WhatsApp file naming, this is a common problem when sending files through HTTP requests. The filename that appears in WhatsApp is determined by how the binary data is structured in your workflow.
Here are a few solutions to try:
• **Use the WhatsApp Business Cloud node instead of HTTP Request** - This node has better file handling and allows you to set the filename properly through the “Input Data Field Name” parameter.
• **If you must use HTTP Request**, ensure your binary data has the correct `fileName` property set. You can use an **Edit Fields (Set) node** before the HTTP Request to modify the binary data:
-
Set the operation to “Add/Update”
-
Choose “Binary” as the data type
-
Set the field name to something like `data.fileName`
-
Use an expression to reference your desired filename
• **Check your file preparation** - Based on the [community.n8n.io]( Generate the CSV file name and pass CSV file as part of Body to HTTP POST ) examples, when working with binary files, make sure to reference `$binary.data.fileName` rather than `$json` expressions for the filename.
Could you share your workflow so we can see exactly how you’re handling the file data? This will help provide a more specific solution.