OneDrive Node in n8n Ignores Custom File Name When Uploading

Based on the information provided:

• The custom File Name field in the Microsoft OneDrive node currently seems to be ignored when binary data (from sources like the HTTP Request node) already contains a filename property.
• This issue has been raised in the community (Microsoft OneDrive Node does not obey the filename property) and, as you noted, appears to still be present in version 1.21.1.
• In the meantime, a common workaround is to modify the binary data before it reaches the OneDrive node so that the desired file name is used. For example, you can use a Set node to override or remove the incoming filename property and then supply your custom file name in a way that the OneDrive node can use.

While the official documentation lists all the available file operations (including uploading files), it does not provide details on this particular behavior. If you rely on the custom File Name setting, you might consider one of the following approaches:

1. Manipulate the Binary Data:
   Use a Set node to adjust the properties of the binary data. You can either remove the filename property or set it to your custom file name before passing it to the OneDrive node.

2. Monitor the Community Thread:
   Since this issue is already discussed in the community forum, keeping an eye on that discussion might help you track when an official fix or workaround is provided in a future release.

For now, using the Set node workaround is generally the recommended approach. If you need assistance with configuring such a workaround, let me know and I can provide an example configuration.