Block 1 - Start
- Type / Role
- n8n-nodes-base.manualTrigger - manualTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
No Code: Convert Multiple Binary Files to Base64 Introduction This template provides a robust, purely no code solution for a common integration challenge: converting multiple binary files contained...
n8n-nodes-base.manualtrigger, n8n-nodes-base.compression, n8n-nodes-base.httprequest, n8n-nodes-base.splitout, n8n-nodes-base.extractfromfile, n8n-nodes-base.set, n8n-nodes-base.aggregate, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Viktor Klepikovskyi.
Original n8n.io sourceThis template provides a robust, purely no-code solution for a common integration challenge: converting multiple binary files contained within a single n8n item (e.g., after unzipping an archive) into a structured JSON array of Base64 encoded strings.
Many external APIs, especially those handling batch file uploads or complex data structures, require files to be submitted as a single JSON payload. This payload typically needs an array containing two elements for each file: the reconstructed file path/name and the Base64 encoded content. This template automatically handles the file isolation, encoding, path reconstruction, and final JSON aggregation, replacing the need for complex custom JavaScript Code nodes.
{{ $binary.keys()[0] }} to ensure the correct binary file is targeted and converted to Base64.path (including the directory, if present) for each file.files array, ready for your final API call.For a detailed walkthrough, including the explanation behind the dynamic expressions and why this is superior to the custom code solution, check out the full blog post: The No-Code Evolution: Base64 Encoding Multiple Files in n8n (Part 2).
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Convert multiple binary files to base64 JSON arrays with no custom code |
|---|---|
| Complexity | intermediate |
| Nodes | 8 |
| Categories | File Management |
| Author | Viktor Klepikovskyi |
| Published | 11 Oct 2025 |
Use the JSON export at /data/workflows/9481/9481.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
No Code: Convert Multiple Binary Files to Base64 Introduction This template provides a robust, purely no code solution for a common integration challenge: converting multiple binary files contained...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your File Management use case.