Gmail to Google Drive email export workflow
๐ฌ Gmail to Google Drive Email Export Workflow (n8n)
๐งฉ Overview
This n8n workflow automates the process of:
- Retrieving all emails from a specific sender using Gmail.
- Extracting essential fields like subject, message, and date.
- Formatting the email date to the desired time zone (e.g., IST).
- Exporting the parsed data as a CSV file.
- Uploading the file to a specified folder in Google Drive.
๐ Nodes Breakdown
1. Start Workflow (Manual Trigger)
- Type: Manual Trigger
- Purpose: Initiates the workflow manually.
2. Gmail Node (Get All Emails)
- Type: Gmail
- Operation:
getAll - Filters:
sender:akhilgadiraju@gmail.com
- Returns: All emails from the specified sender.
- Credentials:
Gmail OAuth2 - Akhil
3. Parse Data (Set Node)
- Purpose: Extracts key fields from the email JSON.
- Mapped Fields:
id: Email IDsubject: Email subjectmessage: Email texttime: Email date
4. Convert Time Field (Code Node)
- Purpose: Converts the email time (
ISO 8601) to a human-readable format. - Output Format:
- Local time using Asia/Kolkata timezone.
- Format:
"Month Day, Year, Hour:Minute AM/PM"
- Customizable: Change the timezone as needed:
timeZone: 'Asia/Kolkata'
5. Convert to File
- Type: Convert to File Node
- Purpose: Converts JSON data to a downloadable
.csvfile. - Output File: CSV containing
id,subject,message, andtime.
6. Google Drive
- Type: Google Drive
- Purpose: Uploads the generated CSV file to Google Drive.
- Drive: My Drive
- Folder: Root
- File Name: Current timestamp +
_n8n_export.csv
7. End Workflow (NoOp)
- Purpose: Final node to explicitly end the workflow.
โ Use Cases
- Personal Email Archiving: Back up or export emails from a specific sender (e.g., invoices, reports).
- Audit Logs: Save conversations for compliance.
- Team Reports: Aggregate project emails into a central file store.
๐ง Customization Guide
| Customization | How to Do It |
|---------------------------|------------------------------------------------------------|
| Change Sender Email | Update the sender field in the Gmail node. |
| Filter by Date/Subject | Add filters in the Gmail node settings. |
| Change Time Zone | Edit timeZone in the Code node. |
| Add More Email Fields | Modify the Set node to include more fields. |
| Change File Format | Use a different format in the Convert to File node. |
| Rename Output File | Adjust the name in the Google Drive node. |
| Change Upload Folder | Set a different folderId in the Google Drive node. |
๐ Deployment Tips
- Schedule the Workflow: Replace
Manual Triggerwith aCronnode. - Avoid Duplicates: Store email IDs and skip duplicates using conditional logic.
- Security: Use environment variables for sensitive credentials.
๐งช Testing Steps
- Manually trigger the workflow.
- Verify email data is parsed and formatted.
- Confirm CSV is generated correctly.
- Ensure the file is uploaded to Google Drive.
๐งฐ Requirements
- Connected Gmail and Google Drive OAuth2 credentials.
- n8n instance (self-hosted or cloud).
- Required nodes available in the n8n environment.
> ๐ก Need more features? You can add: > - Error handling > - Slack/Email notifications > - Conditional filters > - Google Sheets integration instead of Drive
Gmail to Google Drive Email Export Workflow
This n8n workflow automates the process of exporting emails from your Gmail account and saving them as files in your Google Drive. It allows you to manually trigger the export of specific emails, converting their content into a file format and storing them for archival or further processing.
What it does
This workflow streamlines the process of extracting email content and storing it in Google Drive with the following steps:
- Manual Trigger: The workflow is initiated manually, allowing you to control when emails are processed and exported.
- Gmail Email Retrieval: It connects to your Gmail account to retrieve specific email messages.
- Code Execution: A custom code block is executed, likely to extract relevant data from the email, such as the subject, sender, body, or attachments, and prepare it for file conversion.
- Edit Fields (Set): This node is used to manipulate or set specific fields from the extracted email data, ensuring the output is in the desired format for the next steps. This could involve renaming fields, combining data, or adding new properties.
- Convert to File: The processed email data is converted into a file format (e.g., PDF, TXT, HTML). This step takes the email content and transforms it into a storable document.
- Google Drive Upload: The converted file is then uploaded to your Google Drive, providing a centralized and accessible storage location.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Gmail Account: A Gmail account with appropriate permissions to read emails.
- Google Drive Account: A Google Drive account with permissions to create and upload files.
- n8n Credentials: Configured n8n credentials for both Gmail and Google Drive services.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Set up your Gmail OAuth2 credentials within n8n.
- Set up your Google Drive OAuth2 credentials within n8n.
- Customize Gmail Node:
- In the "Gmail" node, specify the criteria for the emails you want to retrieve (e.g., sender, subject, labels, or a specific email ID).
- Customize Code Node:
- Review and adjust the "Code" node if you need to extract specific parts of the email or format the data in a particular way before conversion.
- Customize Edit Fields Node:
- Modify the "Edit Fields" node to ensure the data is structured correctly for the "Convert to File" node and to set the desired file name or other metadata.
- Customize Convert to File Node:
- Select the desired output file format (e.g., PDF, HTML, TXT) and any other conversion options.
- Customize Google Drive Node:
- Specify the target folder in your Google Drive where the exported emails should be saved.
- Execute Workflow: Click "Execute Workflow" in the "Manual Trigger" node to run the workflow and export your emails.
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.
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
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.