Back to Catalog

Create multi-sheet Excel workbooks by merging datasets with Google Drive & Sheets

Robert BreenRobert Breen
539 views
2/3/2026
Official Page

Create multi-sheet Excel workbooks in n8n to automate reporting using Google Drive + Google Sheets

Build an automated Excel file with multiple tabs directly in n8n. Two Code nodes generate datasets, each is converted into its own Excel worksheet, then combined into a single .xlsx and (optionally) appended to a Google Sheet for sharing—eliminating manual copy-paste and speeding up reporting.

Who’s it for

  • Teams that publish recurring reports as Excel with multiple tabs
  • Ops/Marketing/Data folks who want a no-code/low-code way to package JSON into Excel
  • n8n beginners learning the Code → Convert to File → Merge pattern

How it works

  1. Manual Trigger starts the run.
  2. Code nodes emit JSON rows for each table (e.g., People, Locations).
  3. Convert to File nodes turn each JSON list into an Excel binary, assigning Sheet1/Sheet2 (or your names).
  4. Merge combines both binaries into a single Excel workbook with multiple tabs.
  5. Google Sheets (optional) appends the JSON rows to a live spreadsheet for collaboration.

Setup (only 2 connections)

1️⃣ Connect Google Sheets (OAuth2)

  1. In n8n → Credentials → New → Google Sheets (OAuth2)
  2. Sign in with your Google account and grant access
  3. Copy the example sheet referenced in the Google Sheets node (open the node and duplicate the linked sheet), or select your own
  4. In the workflow’s Google Sheets node, select your Spreadsheet and Worksheet

https://docs.google.com/spreadsheets/d/1G6FSm3VdMZt6VubM6g8j0mFw59iEw9npJE0upxj3Y6k/edit?gid=1978181834#gid=1978181834

2️⃣ Connect Google Drive (OAuth2)

  1. In n8n → Credentials → New → Google Drive (OAuth2)
  2. Sign in with the Google account that will store your Excel outputs and allow access
  3. In your Drive-related nodes (if used), point to the folder where you want the .xlsx saved or retrieved

Customize the workflow

  • Replace the sample arrays in the Code nodes with your data (APIs, DBs, CSVs, etc.)
  • Rename sheetName in each Convert to File node to match your desired tab names
  • Keep the Merge node in Combine All mode to produce a single workbook
  • In Google Sheets, switch to Manual mapping for strict column order (optional)

Best practices (per template guidelines)

  • Rename nodes to clear, action-oriented names (e.g., “Build People Sheet”, “Build Locations Sheet”)
  • Add a yellow Sticky Note at the top with this description so users see setup in-workflow
  • Do not hardcode credentials inside HTTP nodes; always use n8n Credentials
  • Remove personal IDs/links before publishing

Sticky Note (copy-paste)

> Multi-Tab Excel Builder (Google Drive + Google Sheets)
> This workflow generates two datasets (Code → JSON), converts each to an Excel sheet, merges them into a single workbook with multiple tabs, and optionally appends rows to Google Sheets.
>
> Setup (2 connections):
> 1) Google Sheets (OAuth2): Create credentials → duplicate/select your target spreadsheet → set Spreadsheet + Worksheet in the node.
> 2) Google Drive (OAuth2): Create credentials → choose the folder for storing/retrieving the .xlsx.
>
> Customize: Edit the Code nodes’ arrays, rename tab names in Convert to File, and adjust the Sheets node mapping as needed.

Troubleshooting

  • Missing columns / wrong order: Use Manual mapping in the Google Sheets node
  • Binary not found: Ensure each Convert to File node’s binaryPropertyName matches what Merge expects
  • Permissions errors: Re-authorize Google credentials; confirm you have edit access to the target Sheet/Drive folder

📬 Contact

Need help customizing this (e.g., filtering by campaign, sending reports by email, or formatting your PDF)?

  • 📧 rbreen@ynteractive.com
  • 🔗 https://www.linkedin.com/in/robert-breen-29429625/
  • 🌐 https://ynteractive.com

n8n Workflow: Create Multi-Sheet Excel Workbooks by Merging Datasets with Google Drive & Sheets

This n8n workflow automates the process of combining data from multiple Google Sheets into a single Excel workbook, with each sheet becoming a separate tab in the final Excel file. The generated Excel file is then uploaded to Google Drive.

What it does

This workflow simplifies the creation of consolidated Excel reports from disparate Google Sheets data. Here's a step-by-step breakdown:

  1. Manual Trigger: The workflow starts manually, allowing you to initiate the process on demand.
  2. Google Sheets - Read Sheet 1: It reads data from the first specified Google Sheet.
  3. Google Sheets - Read Sheet 2: Simultaneously, it reads data from a second specified Google Sheet.
  4. Merge Data: The data from both Google Sheets is merged. This step is crucial for combining the different datasets that will form separate sheets in the final Excel file.
  5. Code - Prepare for Excel: A Code node processes the merged data, likely transforming it into a format suitable for Excel, potentially creating an array of objects where each object represents a sheet in the Excel workbook.
  6. Convert to File - Excel: The prepared data is then converted into an Excel (.xlsx) file. Each dataset from the original Google Sheets will become a separate tab within this Excel file.
  7. Google Drive - Upload File: Finally, the generated Excel workbook is uploaded to a specified folder in Google Drive.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: Access to the Google Sheets containing the data you wish to merge.
  • Google Drive Account: A Google Drive account where the final Excel file will be uploaded.
  • Google OAuth2 Credentials: Configured Google OAuth2 credentials in n8n for both Google Sheets and Google Drive nodes to access your accounts.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Google Sheets Nodes:
    • For "Google Sheets - Read Sheet 1" and "Google Sheets - Read Sheet 2", select your Google Sheets credential.
    • Specify the "Spreadsheet ID" and "Sheet Name" for each Google Sheet you want to read.
  3. Configure Google Drive Node:
    • For "Google Drive - Upload File", select your Google Drive credential.
    • Specify the "Folder ID" where you want to upload the Excel file.
    • You can customize the "File Name" for the output Excel workbook.
  4. Review Code Node (Optional): The "Code - Prepare for Excel" node contains custom JavaScript logic. While it's pre-configured for this use case, you might need to adjust it if your input data structure or desired Excel output requires specific transformations.
  5. Execute the Workflow: Click "Execute Workflow" on the "When clicking ‘Execute workflow’" node to run the automation.

The workflow will then read your specified Google Sheets, combine their data into a multi-sheet Excel file, and upload it to your Google Drive.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942