I have one workflow that send the pdf to whatsapp through http request node node the problem occur was file name is correct in work flow but when sent to whatsapp filename is equal to google_id name how can i set this to file name

Questions
1

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

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.