WhatsApp Support - Daily Summary

Workflow Preview

Description

⭐ **If this workflow helped you, please leave a review on n8n Basket!** --- # 📊 WhatsApp Support — Daily Summary Report ### AI-Generated Daily Business Intelligence for Your Customer Support **Workflow ID:** `xSHeYYNpaAVQWWMe` **Schedule:** Every day at 9:00 AM UTC **Total Nodes:** 10 (8 functional + 1 sticky note + 1 error handler) **AI Model:** Groq llama-3.3-70b-versatile **Status:** Production-Ready --- ## 📌 Overview This workflow is your **daily business intelligence assistant**. Every morning at 9:00 AM UTC, it automatically reads all customer support conversations and escalations from the past 24 hours (logged in Google Sheets by the main bot), sends that data to Groq AI to generate a professional summary report, and delivers it to you as a formatted Telegram message. You wake up, check your Telegram, and instantly know how your customer support performed yesterday — total messages handled, how many were auto-resolved vs escalated, what the top issues were, and whether any escalations are still unresolved. **This is a companion workflow to the [WhatsApp AI Customer Support Bot](#).** Both workflows must be active and using the same Google Sheet for this summary to work. The main bot logs the data — this workflow reads and summarizes it. **Who is this for?** - 📈 **Business owners** who want a daily pulse on customer support performance - 🧑‍💼 **Managers** who need to track resolution rates and identify recurring issues - 📊 **Anyone** running the WhatsApp AI Customer Support Bot who wants automated reporting --- ## ✨ Features - ⏰ **Automatic daily trigger** — runs every day at 9:00 AM UTC, no manual intervention needed - 📖 **Reads both data sources** — pulls from the **Conversations** tab (auto-handled messages) and the **Escalations** tab (human-needed messages) in Google Sheets - 🧠**Groq AI-generated business summary** — not just raw numbers, but an intelligent analysis with insights and recommendations written in natural language - 📊 **Key metrics included in every report:** - Total messages handled in the past 24 hours - Number of auto-resolved messages vs escalated messages - Auto-resolution rate (percentage) - Top issue categories ranked by frequency - Count of unresolved escalations still marked as "Open" - Reporting period (date range) - 📱 **Formatted Telegram delivery** — clean, readable message with Markdown formatting sent straight to your Telegram - ⚠️ **Built-in error handling** — if anything fails (Google Sheets unavailable, AI error, etc.), you get a Telegram error alert instead of silent failure - 🔄 **Graceful fallback** — if the AI summary generation fails, you still receive a basic stats report with the raw numbers --- ## 🛠️ Required Credentials This workflow uses **3 credentials** — all shared with the main WhatsApp AI Customer Support Bot workflow: | # | Credential Name | Service | Purpose | |---|----------------|---------|---------| | 1 | Groq_HTTP_Auth | Groq AI API | Generates the AI summary report | | 2 | Google_Sheets_OAuth | Google Sheets | Reads Conversations and Escalations tabs | | 3 | Telegram account | Telegram Bot API | Sends the daily summary message | > 💡 **If you already set up the main WhatsApp bot workflow, all credentials are already configured.** You don't need to create anything new — just select the same credentials when connecting the nodes. ### How to Get Each Credential For detailed step-by-step instructions on obtaining each credential, refer to the **"Required Credentials"** section in the main workflow's README. Here's a quick summary: **Groq API Key:** 1. Go to [https://console.groq.com](https://console.groq.com) → Sign up → API Keys → Create Key 2. In n8n, create a new **HTTP Header Auth** credential named `Groq_HTTP_Auth` 3. Set Header Name: `Authorization`, Header Value: `Bearer YOUR_GROQ_API_KEY` **Google Sheets OAuth:** 1. Google Cloud Console → Enable Google Sheets API → Create OAuth credentials 2. In n8n, create a **Google Sheets OAuth2** credential 3. Authorized redirect URI: `https://YOUR-N8N-INSTANCE/rest/oauth2-credential/callback` **Telegram Bot Token:** 1. Open Telegram → Search @BotFather → `/newbot` → Copy the token 2. In n8n, create a **Telegram** credential and paste the token 3. **You still need to set the Chat ID** in the Telegram send nodes (see below) --- ## ⏰ Schedule Configuration ### Current Schedule The workflow runs on a **cron expression**: `0 9 * * *` This means: **every day at 9:00 AM UTC**. ### How to Change the Schedule Time 1. Open the workflow in n8n 2. Double-click the **"Daily 9AM Trigger"** node 3. You'll see the **Cron Expression** field: `0 9 * * *` 4. Change it to your preferred time: | Time (UTC) | Cron Expression | Description | |------------|----------------|-------------| | 6:00 AM UTC | `0 6 * * *` | Early morning report | | 9:00 AM UTC | `0 9 * * *` | Default — standard morning report | | 12:00 PM UTC | `0 12 * * *` | Midday report | | 6:00 PM UTC | `0 18 * * *` | End of business day report | | 9:00 PM UTC | `0 21 * * *` | Evening report | | Twice daily (9AM & 6PM) | `0 9,18 * * *` | Morning + evening reports | | Every Monday at 9AM | `0 9 * * 1` | Weekly report (Mondays only) | ### How to Convert UTC to Your Local Timezone The cron schedule runs in **UTC**. To figure out what time that is for you: | Your Timezone | UTC Offset | 9:00 AM UTC = Your Time | |---------------|-----------|------------------------| | 🇵🇰 Pakistan (PKT) | UTC+5 | **2:00 PM PKT** | | 🇮🇳 India (IST) | UTC+5:30 | **2:30 PM IST** | | 🇦🇪 Dubai (GST) | UTC+4 | **1:00 PM GST** | | 🇸🇦 Saudi Arabia (AST) | UTC+3 | **12:00 PM AST** | | 🇬🇧 UK (GMT/BST) | UTC+0/+1 | **9:00 AM GMT / 10:00 AM BST** | | 🇺🇸 US Eastern (EST/EDT) | UTC-5/-4 | **4:00 AM EST / 5:00 AM EDT** | | 🇺🇸 US Pacific (PST/PDT) | UTC-8/-7 | **1:00 AM PST / 2:00 AM PDT** | **Example:** If you're in Pakistan and want the report at 9:00 AM PKT (your morning), set the cron to `0 4 * * *` (because 9:00 AM PKT = 4:00 AM UTC). **Formula:** Your desired local hour − your UTC offset = UTC hour for the cron. --- ## 📊 Sample Daily Report Here's exactly what the Telegram message looks like when it arrives. This is a real example with sample data: ``` 📊 Daily Support Report 📋 Daily Customer Support Summary ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📅 Reporting Period: 2026-03-07 to 2026-03-08 📈 Key Metrics: • Total Messages Handled: 47 • Auto-Resolved: 38 (80.9%) • Escalated to Human: 9 (19.1%) • Auto-Resolution Rate: 80.9% 🏷️ Top Issue Categories: 1. GENERAL_FAQ — 18 messages (38.3%) 2. ORDER_INQUIRY — 12 messages (25.5%) 3. PRICE_QUESTION — 8 messages (17.0%) 4. BOOKING_REQUEST — 5 messages (10.6%) 5. COMPLAINT — 3 messages (6.4%) 6. HUMAN_NEEDED — 1 message (2.1%) ⚠️ Unresolved Escalations: 3 These require immediate attention — check the Escalations tab and Notion Support Tasks database. 💡 Recommendations: • FAQ coverage is strong — 80.9% resolution rate is above the 75% industry benchmark • Consider adding more FAQ entries about orders (25.5% of all messages) to reduce escalations • 3 unresolved escalations need follow-up today ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🤖 Generated by WhatsApp AI Support Bot ``` > 💡 **Note:** The exact format and recommendations will vary each day because the AI generates them dynamically based on your actual data. ### What You See on a Day With No Messages ``` 📊 Daily Support Report 📋 Daily Customer Support Summary ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📅 Reporting Period: 2026-03-07 to 2026-03-08 📈 Key Metrics: • Total Messages Handled: 0 • No customer interactions recorded in the past 24 hours. 💡 This could mean: • It was a quiet day (weekends/holidays) • The webhook may not be receiving messages — check that the main workflow is active ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ``` --- ## 🔄 Workflow Architecture Diagram ``` ┌──────────────────┐ │ Daily 9AM Cron │ │ Trigger │ └────────┬─────────┘ │ ┌──────┴──────┐ ▼ ▼ ┌──────────────┐ ┌──────────────┐ │ Read │ │ Read │ │Conversations │ │ Escalations │ │(Google Sheet)│ │(Google Sheet)│ └──────┬───────┘ └──────┬───────┘ │ │ └────────┬───────┘ ▼ ┌────────────────────┐ │ Filter & Aggregate │ │ (last 24h only) │ │ Count categories │ │ Calc resolution % │ └────────┬───────────┘ ▼ ┌────────────────────┐ │ Generate Summary │ │ (Groq AI) │ └────────┬───────────┘ ▼ ┌────────────────────┐ │ Parse Summary │ └────────┬───────────┘ ▼ ┌────────────────────┐ │ Send Daily Summary │ │ (Telegram) │ └────────────────────┘ Error Handler: ┌──────────┐ ┌──────────────┐ │ On Error │───→│ Error Alert │ │ │ │ (Telegram) │ └──────────┘ └──────────────┘ ``` --- ## ▶️ How to Import & Activate ### Import the JSON File: 1. Open your n8n instance in a browser 2. Click **"Add workflow"** (the "+" button, or go to **Workflows → New**) 3. In the new workflow editor, click the **"..."** menu (top-right corner) 4. Click **"Import from File..."** 5. Select the downloaded `.json` file for the daily summary workflow 6. The workflow will appear on the canvas with all 10 nodes ### Connect Your Credentials: 1. Double-click each node that shows a ⚠️ warning icon 2. Select the matching credential for each: | Node | Credential to Select | |------|---------------------| | Read Conversations | Google_Sheets_OAuth | | Read Escalations | Google_Sheets_OAuth | | Generate Summary | Groq_HTTP_Auth | | Send Daily Summary | Telegram account | | Error Alert | Telegram account | 3. For the **Google Sheets nodes**: also select your spreadsheet and verify the sheet tab names (`Conversations` and `Escalations`) 4. For the **Telegram nodes**: enter your **Chat ID** (see the main workflow README for how to find it) ### Activate the Workflow: 1. Click the **toggle switch** in the top-right corner (it says "Inactive") 2. It should turn green and say **"Active"** 3. The workflow will now run automatically every day at 9:00 AM UTC ### Test It Immediately (Without Waiting Until 9 AM): 1. Open the workflow in the n8n editor 2. Click the **"Test Workflow"** button (or press Ctrl+Enter) 3. You should receive a Telegram message within 10–15 seconds --- ## ❓ Troubleshooting ### Problem 1: Summary Not Being Sent **Symptoms:** It's past 9:00 AM UTC and you didn't receive a Telegram message. **Fixes:** - ✅ Make sure the workflow is **Active** (green toggle in top-right of editor) - ✅ Check the workflow **Executions** tab — do you see any executions for today? - ✅ Verify the **Telegram Chat ID** is set correctly in the "Send Daily Summary" node - ✅ Make sure you've **started a conversation** with your Telegram bot (send `/start` to the bot) - ✅ Try a **manual test**: open the workflow editor → click "Test Workflow" ### Problem 2: Empty Report (No Data in Sheets) **Symptoms:** The report arrives but says "0 messages handled." **Fixes:** - ✅ Open your Google Sheet and check the **Conversations** tab — are there rows with data? - ✅ Check the **Timestamp** column format — the filter expects ISO format timestamps (e.g., `2026-03-07T14:30:00.000Z`) - ✅ Make sure both Google Sheets nodes are connected to the **correct spreadsheet** and correct sheet tabs - ✅ Re-authorize the Google Sheets OAuth credential if it has expired ### Problem 3: Wrong Timezone in Report **Explanation:** The workflow runs in UTC. Adjust the cron schedule to match your local business day end time. **Fix:** If your business day ends at 6:00 PM PKT, run summary at 6:00 PM PKT = 1:00 PM UTC → cron: `0 13 * * *` ### Problem 4: Groq AI Summary Generation Failed **Symptoms:** You receive a basic report with just numbers instead of AI-generated summary. **Fixes:** - ✅ Check your Groq API usage at [https://console.groq.com/usage](https://console.groq.com/usage) - ✅ Verify the API key in the **Groq_HTTP_Auth** credential is valid ### Problem 5: Getting Duplicate Reports **Fixes:** - ✅ Check that you don't have **multiple copies** of this workflow active - ✅ Deactivate duplicates if found --- ## 💡 Customization Tips ### Change the Report Frequency | Frequency | Cron Expression | |-----------|----------------| | Every day at 9 AM | `0 9 * * *` (default) | | Twice daily (9 AM and 6 PM) | `0 9,18 * * *` | | Every Monday at 9 AM (weekly) | `0 9 * * 1` | | First day of each month | `0 9 1 * *` | | Every 6 hours | `0 */6 * * *` | ### Customize the AI Summary Style Edit the system prompt in the **"Generate Summary"** node to change tone or add KPIs: - **CEO briefing style:** *"Write it as if briefing a CEO. Use bullet points and bold numbers."* - **Add action items:** *"End every report with 3 specific action items for today."* ### Send to Multiple Recipients Duplicate the **"Send Daily Summary"** node, set a different Chat ID in each copy, and connect both to "Parse Summary" output. Or use a Telegram Group Chat ID. --- ## 📋 Node Reference Table | # | Node Name | Type | Purpose | |---|-----------|------|---------| | 1 | Daily 9AM Trigger | Schedule Trigger | Fires every day at 9:00 AM UTC | | 2 | Read Conversations | Google Sheets Read | Reads all rows from "Conversations" tab | | 3 | Read Escalations | Google Sheets Read | Reads all rows from "Escalations" tab | | 4 | Filter & Aggregate | Code | Filters to last 24h, counts categories, calculates resolution rate | | 5 | Generate Summary | HTTP Request (Groq) | AI generates natural-language business summary | | 6 | Parse Summary | Code | Extracts summary text from AI response | | 7 | Send Daily Summary | Telegram Send | Delivers formatted report to your Telegram | | 8 | On Error | Error Trigger | Catches any node failure | | 9 | Error Alert | Telegram Send | Sends error notification to owner | Plus **1 Sticky Note** explaining the workflow purpose on the canvas. --- ## 🔗 Related Workflows | Workflow | Purpose | Required? | |----------|---------|-----------| | **WhatsApp AI Customer Support Bot** | Main bot — handles customer messages, logs data | ✅ Yes | | **WhatsApp Support — Daily Summary** *(this workflow)* | Reads logs and generates daily report | Optional but recommended | > ⚠️ **Important:** This workflow depends on the main WhatsApp AI Customer Support Bot to log conversations to Google Sheets. Without the main workflow running, this summary will have nothing to report. --- 📩 **Need help setting this up? Contact the seller via n8n Basket messaging.**

What's Included