Working with Excel files
Configured with Ftp, Google Drive, HTTP Request, Microsoft One Drive, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Files / media
- Trigger
- Web / API
- Transform
- Integration
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Read Binary File | Files / media | Read Binary File | See node parameters |
| On clicking 'execute' | Trigger | Manual Trigger | See node parameters |
| Write Binary File | Files / media | Write Binary File | See node parameters |
| Download from Google Drive | Files / media | Google Drive | download |
| Download from Microsoft OneDrive | Files / media | Microsoft One Drive | download |
| Download Excel File | Web / API | HTTP Request | See node parameters |
| Work out Age | Transform | Edit Fields | See node parameters |
| Upload to SFTP | Files / media | Ftp | upload |
| Upload to Google Drive | Files / media | Google Drive | See node parameters |
| Upload to Microsoft OneDrive | Files / media | Microsoft One Drive | See node parameters |
| Read Spreadsheet File | Integration | Spreadsheet File | See node parameters |
| Write Spreadsheet File | Integration | Spreadsheet File | toFile |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleDriveOAuth2ApimicrosoftOneDriveOAuth2Apisftp
Workflow notes
Working with Excel files
Working with Excel files
- Load the spreadsheet file into the workflow (.xls, .xlsx, .csv).
- Convert the file with Spreadsheet File node. This allows other nodes to access the data.
- Transform and manipulate the spreadsheet data as needed
- [Optional] Convert back to a spreadsheet file
- [Optional] Save file locally or upload to a server
ℹ️ This template shows how to work with spreadsheet files themselves. Use the Microsoft Excel 365 node to interact with the Microsoft Office 365 cloud platform.
Read Binary File
Fetches a local file
2. Convert the file into JSON format
2. Convert the file into JSON format
JSON data can be used by nodes
Download Excel File
Fetches file from server
Working with Excel files
Working with Excel files
Purpose and structure
This folder contains the Working with Excel files workflow. Its executable nodes use ftp, googleDrive, httpRequest, manualTrigger, microsoftOneDrive, readBinaryFile, set, spreadsheetFile, writeBinaryFile. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
On clicking 'execute'
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Microsoftonedrive/0276_Microsoftonedrive_Readbinaryfile_Automation_Webhook.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- 1A. From a public URL
- 1. Load file into workflow
- 1C. From a cloud platform
- 4. [Optional] Convert node data back to .xls file
- 3. Manipulate or transform your spreadsheet data
- 4B. To a webserver via (S)FTP
- 5. Save or upload new file
- 4A. To a local filesystem
- 4C. To a cloud service
- 1B. From the local filesystem