-
Notifications
You must be signed in to change notification settings - Fork 48k
Description
Bug Description
When using the Google Drive node with the Share operation (attached to an AI Agent), the node appends an extra "." (dot) to the end of the file name. This results in the file ID being incorrect and leads to a 404 error (File not found) when attempting to share the file.
The issue does not occur when the same API request is executed through the HTTP Request node manually, which indicates that the problem is specific to the Google Drive node behavior.

To Reproduce
- Create a file from text using the Google Drive node (connected to an AI Agent node).
- Attempt to share the file using the Google Drive node with the Share operation (also connected to an AI Agent node).
- Inspect the logs — notice the file ID has a trailing "." at the end.
- The request fails with 404 File not found.
Note: AI Agent node was connected to a chat agent trigger and Mistrall Small LLM.
Expected behavior
The Google Drive node should share the file using the correct file ID without appending extra characters (e.g., "."), successfully granting public access without errors.
Debug Info
{
"errorMessage": "The resource you are requesting could not be found",
"errorDetails": {
"errorData": {
"error": {
"code": 404,
"message": "File not found: 1aLMrc34kh-lzH2pAPxzbbwmtoO6EyvV-.",
"errors": [
{
"message": "File not found: 1aLMrc34kh-lzH2pAPxzbbwmtoO6EyvV-.",
"domain": "global",
"reason": "notFound",
"location": "fileId",
"locationType": "parameter"
}
]
}
}
},
"n8nDetails": {
"time": "21/10/2025, 19:43:16",
"n8nVersion": "1.114.3 (Cloud)",
"binaryDataMode": "filesystem"
}
}
Operating System
Windows 11 pro
n8n Version
1.115.2
Node.js Version
v24.10.0
Database
SQLite (default)
Execution mode
main (default)
Hosting
n8n cloud