Restaurant daily insights with Gemini AI - sales, waste & feedback email summary
In this guide, we’ll walk you through setting up an AI-driven workflow that automatically fetches daily sales, food waste, and customer feedback data from Google Sheets, generates actionable insights using AI, merges them into a comprehensive report, and sends it as an email draft. Ready to automate your restaurant’s daily insights? Let’s dive in!
What’s the Goal?
- Automatically retrieve daily sales data, food waste records, and customer feedback from Google Sheets.
- Use AI to analyze data and generate insights, including top performers, waste reduction recommendations, and feedback summaries.
- Merge the insights into a structured daily report.
- Send the report as an AI-generated email draft for review or sending.
- Enable scheduled automation for daily insights delivery.
By the end, you’ll have a self-running system that delivers daily restaurant insights effortlessly.
Why Does It Matter?
Manual data analysis and reporting are time-consuming and error-prone. Here’s why this workflow is a game-changer:
- Zero Human Error: AI ensures accurate and consistent insights.
- Time-Saving Automation: Instantly process data and draft reports, boosting efficiency.
- Scheduled Delivery: Receive insights daily without manual effort.
- Actionable Insights: Empower your team with data-driven decisions. Think of it as your tireless data analyst that keeps your restaurant informed.
How It Works
Here’s the step-by-step magic behind the automation:
Step 1: Trigger the Workflow
- Initiate the workflow daily using the Daily Report Scheduler node (e.g., every day at a set time).
Step 2: Fetch Daily Sales Data
- Retrieve sales data from the Google Sheet using the Fetch Daily Sales Data node.
Step 3: Fetch Daily Food Waste Records
- Retrieve food waste data from the Google Sheet using the Fetch Daily Food Waste Records node.
Step 4: Fetch Customer Feedback
- Retrieve customer feedback from the Google Sheet using the Fetch Customer Feedback node.
Step 5: Normalize Sales Records
- Process and standardize sales data for AI analysis.
Step 6: Normalize Waste Data
- Process and standardize food waste data for AI analysis.
Step 7: Normalize Feedback Data
- Process and standardize customer feedback data for AI analysis.
Step 8: AI Sales Insights Generator
- Use AI (e.g., Google Chat Model) to analyze sales data, identify top performers, and provide recommendations.
Step 9: AI Waste Reduction Insights Generator
- Use AI to analyze waste data and suggest reduction strategies.
Step 10: AI Feedback Summary
- Use AI to summarize customer feedback and identify common themes.
Step 11: Format Sales Output
- Structure the sales insights into a readable format.
Step 12: Format Waste Output
- Structure the waste reduction insights into a readable format.
Step 13: Format Feedback AI Output
- Structure the feedback summary into a readable format.
Step 14: Merge & Create Email
- Combine all formatted insights into a single daily report email draft.
Step 15: Prepare Email Content
- Finalize the email content for sending.
Step 16: Send Daily Report
- Send the AI-generated daily summary email via Gmail.
How to Use the Workflow?
Importing a workflow in n8n is a straightforward process that allows you to use pre-built workflows to save time. Below is a step-by-step guide to importing the Restaurant Daily Insights Automation workflow in n8n.
Steps to Import a Workflow in n8n
-
Obtain the Workflow JSON
- Source the Workflow: Workflows are shared as JSON files or code snippets, e.g., from the n8n community, a colleague, or exported from another n8n instance.
- Format: Ensure you have the workflow in JSON format, either as a file (e.g., workflow.json) or copied text.
-
Access the n8n Workflow Editor
- Log in to n8n (via n8n Cloud or self-hosted instance).
- Navigate to the Workflows tab in the n8n dashboard.
- Click Add Workflow to create a blank workflow.
-
Import the Workflow
- Option 1: Import via JSON Code (Clipboard):
- Click the three dots (⋯) in the top-right corner to open the menu.
- Select Import from Clipboard.
- Paste the JSON code into the text box.
- Click Import to load the workflow.
- Option 2: Import via JSON File:
- Click the three dots (⋯) in the top-right corner.
- Select Import from File.
- Choose the .json file from your computer.
- Click Open to import.
- Option 1: Import via JSON Code (Clipboard):
Setup Notes
- Google Sheet Columns:
- Sales Data Sheet:
Date,Item Name,Quantity Sold,Revenue,Cost,Profit. - Food Waste Records Sheet:
Date,Item Name,Waste Quantity,Reason,Timestamp. - Customer Feedback Sheet:
Date,Customer Name,Feedback Text,Rating,Timestamp.
- Sales Data Sheet:
- Google Sheets Credentials: Configure OAuth2 settings in the fetch nodes with your Google Sheet ID and credentials.
- AI Models: Set up the AI nodes (e.g., Google Chat Model) with appropriate API credentials.
- Gmail Integration: Authorize the Send Daily Report node with Gmail API credentials to send emails.
- Scheduling: Adjust the Daily Report Scheduler node to your preferred time (e.g., daily at 9 AM).
Restaurant Daily Insights with Gemini AI: Sales, Waste, and Feedback Email Summary
This n8n workflow leverages Google Gemini AI to generate daily insights for a restaurant based on sales, waste, and feedback data, then compiles these insights into a summary email. It automates the process of data analysis and reporting, providing actionable summaries to key stakeholders.
What it does
This workflow performs the following key steps:
- Triggers Daily: Initiates the workflow on a scheduled basis (e.g., daily).
- Retrieves Sales Data: Fetches the latest sales data from a Google Sheet.
- Retrieves Waste Data: Fetches the latest waste data from a separate Google Sheet.
- Retrieves Feedback Data: Fetches customer feedback data from another Google Sheet.
- Merges Data: Combines the retrieved sales, waste, and feedback data into a single dataset for AI processing.
- Prepares Data for AI: Uses a Code node to format the merged data into a prompt suitable for the AI agent.
- Generates AI Insights: Utilizes a Google Gemini Chat Model within an AI Agent to analyze the combined data and generate insights regarding sales performance, waste reduction opportunities, and customer feedback trends.
- Thinks and Refines: Employs a "Think" tool (likely part of the AI Agent) to process and refine the AI-generated insights.
- Sends Summary Email: Compiles the AI-generated insights into a comprehensive email and sends it via Gmail.
- Waits (Optional): Includes a Wait node, which could be used for rate limiting or to introduce a delay before a subsequent action (though no subsequent action is connected in this definition).
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Google Sheets Account: Access to Google Sheets containing your restaurant's sales, waste, and customer feedback data.
- Ensure your Google Sheets are correctly structured and accessible by the n8n Google Sheets node.
- Google API Credentials: Configured Google OAuth 2.0 credentials in n8n for Google Sheets and Gmail.
- Google Gemini API Key: An API key for the Google Gemini Chat Model, configured as a credential in n8n.
- Gmail Account: A Gmail account to send the summary emails.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up your Google Sheets credentials (OAuth 2.0) for accessing your sales, waste, and feedback spreadsheets.
- Set up your Gmail credentials (OAuth 2.0) for sending emails.
- Configure your Google Gemini Chat Model credentials with your API key.
- Update Google Sheets Nodes:
- For each "Google Sheets" node (Sales, Waste, Feedback), configure the Spreadsheet ID and Sheet Name to point to your actual data.
- Configure Code Node: Review and adjust the "Code" node to ensure it correctly formats your specific Google Sheets data into the desired prompt for the AI Agent.
- Configure AI Agent:
- Ensure the "AI Agent" node is correctly configured to use the "Google Gemini Chat Model" and the "Think" tool.
- Adjust the prompt within the AI Agent to guide Gemini AI in generating the specific types of insights you need (e.g., "Summarize daily sales trends, identify top waste items, and extract key themes from customer feedback.").
- Configure Gmail Node:
- Set the recipient email address(es) for the daily summary.
- Customize the email subject and body using expressions to include the AI-generated insights.
- Activate the Workflow: Enable the workflow. The "Schedule Trigger" node will automatically run it at the configured interval (e.g., daily).
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.