Send weekly KPI executive summaries from Google Sheets via Gemini, Gmail and Slack
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Google Sheets
n8n-nodes-base.googleSheets - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - Google Gemini
@n8n/n8n-nodes-langchain.googleGemini - Gmail
n8n-nodes-base.gmail - Slack
n8n-nodes-base.slack
What it does
Quick overview This workflow runs weekly to read KPI rows from Google Sheets, merge them with benchmark KPI data from an HTTP API, calculate week-over-week trends, generate an executive summary with Google Gemini, then send the result via Gmail and Slack and log it back to Google Sheets. How it works 1. Runs on a weekly schedule to start the reporting cycle. 2. Reads weekly KPI data from a Google Sheets spreadsheet and fetches benchmark KPI data from an HTTP endpoint. 3. Normalizes both data sources into a consistent KPI structure and merges them into a single list. 4. Calculates KPI movement metrics such as absolute change, percentage change, trend direction, and whether each metric is above or below target. 5. Sends the consolidated KPI results to Google Gemini to generate a concise executive-style weekly summary. 6. Formats the AI summary for distribution, then sends it via Gmail and Slack and appends a copy to a Google Sheets log. Setup 1. Configure the Schedule Trigger to run on your preferred weekly day and time. 2. Add Google Sheets credentials and set the document and sheet for both the KPI input spreadsheet and the KPI log spreadsheet. 3. Ensure your KPI input sheet includes columns like weekstart, channel, metricname, currentvalue, previousvalue, targetvalue, and notes. 4. Add a Google Gemini (PaLM) API credential and select the model you want to use for summary generation. 5. Add Gmail credentials and set the recipient email address, and add Slack credentials and choose the target channel for the weekly post. 6. Replace or remove the benchmark HTTP endpoint (jsonplaceholder) if you do not want demo benchmark data mixed into your report. Additional info How To Customize Nodes This workflow is easy to adapt without changing the full structure. Weekly KPI Schedule Trigger Adjust the run day and time to match your reporting cycle. Set Weekly Report Context Change the report title, date label format, or add extra fields such as business unit or reporting owner. Read Weekly KPI Data Switch the spreadsheet, use another tab, or filter source rows before normalization. Fetch Benchmark KPI Data Replace the placeholder API with a live benchmark source such as an analytics API, CRM endpoint, ad platform API, or internal reporting service. Normalize Sheet KPI Data Add more fields from your spreadsheet, such as region, campaign, product line, or owner. Normalize Benchmark KPI Data Change how external metrics are mapped so they match the same schema as your main KPI data. Calculate Weekly KPI Trends Extend the logic to calculate rolling averages, status colors, weighted scoring, or alert thresholds. Build Executive Summary Prompt Refine the prompt for a different writing tone, longer narrative summaries, or department specific outputs. Generate Weekly KPI Summary Switch model versions or tune generation settings if your summaries need more detail or tighter control. Format Email and Slack Message Create separate message structures for leadership, sales, marketing, or clients. Send Weekly Summary Email Send to multiple recipients, use a group mailbox, or route through a different email provider. Send Weekly Summary to Slack Post into multiple channels, threads, or team specific destinations. Log Weekly Summary to Google Sheets Add more columns such as workflow status, report owner, channel count, or execution ID. Add ons You can extend this workflow with additional features such as: - Error handling branches for failed API, Slack, Gmail, or Sheets steps - Conditional routing so only failed or below target KPIs are escalated - Multi team summaries for different departments from the same source file - HTML email formatting for richer presentation - PDF report generation before email delivery - Dashboard sync to a data warehouse or BI tool - Approval flow before sending the summary externally - Separate prompts for leadership and operational teams Use Case Examples This workflow supports several practical business scenarios, including