Block 1 - Extract from File
- Type / Role
- n8n-nodes-base.extractFromFile - extractFromFile
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
How it works This workflow changes the file name, and therefore the extension and MIME type, of any binary file passed to it. This is perfect for converting file formats on the fly, like turning a ...
n8n-nodes-base.extractfromfile, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.stickynote, n8n-nodes-base.executeworkflowtrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Lucas Peyrin.
Original n8n.io sourceThis workflow changes the file name, and therefore the extension and MIME type, of any binary file passed to it. This is perfect for converting file formats on the fly, like turning a Telegram voice message (.oga) into an MP3 for an AI transcription service.
SET OUTPUT FILE NAME node is where you define the desired output file name and extension (e.g., audio.mp3). It also dynamically captures the property name of the incoming binary (e.g., data).Setup time: < 1 minute
This workflow is designed to be used as a sub-workflow.
SET OUTPUT FILE NAME node.output_file_name value to your desired file name (e.g., voice_message.mp3 or document.pdf).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 | ๐ ๏ธ Change Binary MimeType/Extension |
|---|---|
| Complexity | intermediate |
| Nodes | 8 |
| Categories | File Management |
| Author | Lucas Peyrin |
| Published | 23 Jun 2025 |
Use the JSON export at /data/workflows/5155/5155.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.
How it works This workflow changes the file name, and therefore the extension and MIME type, of any binary file passed to it. This is perfect for converting file formats on the fly, like turning a ...
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.