GitLab binary file uploads fixed
Binary file uploads via the GitLab node now work correctly when n8n uses filesystem-based storage, fixing a bug where only ~7 bytes of metadata were uploaded instead of actual file content.
When n8n switched to filesystem-based binary data storage, the GitLab node started uploading corrupted files. The node was reading a storage reference (~7 bytes of metadata) instead of the actual file content. Binary file uploads via the GitLab node now resolve correctly regardless of storage mode. The same fix was previously applied to the GitHub node, and this change brings GitLab parity. Users can now upload binary files through the GitLab node without files being truncated to metadata references.
View Original GitHub Description
Summary
Fix binary file upload in the GitLab node when using filesystem-based binary data storage (N8N_DEFAULT_BINARY_DATA_MODE=filesystem).
The bug: When uploading binary files via the GitLab node (File → Create or Edit with binary data), the node sent binaryData.data directly — which in filesystem mode contains a storage metadata reference (~7 bytes) instead of the actual file content.
The fix: Use getBinaryDataBuffer() to correctly resolve the binary content regardless of storage mode, then convert to base64. This is the same fix applied to the GitHub node in PR #23497.
How to test:
- Set
N8N_DEFAULT_BINARY_DATA_MODE=filesystem - Create a workflow: Read File → GitLab (File → Create, binary data mode)
- Upload a binary file to a GitLab repository
- Verify the uploaded file has the correct content and size (not ~7 bytes)
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-4255 Fixes #24809
Review / Merge checklist
- I have seen this code, I have run this code, and I take responsibility for this code.
- PR title and summary are descriptive. (conventions)
- Docs updated or follow-up ticket created.
- Tests included.
- PR Labeled with
release/backport(if the PR is an urgent fix that needs to be backported)