WhatsApp to Google Drive, daily chat recaps
Your WhatsApp groups move fast. One minute you’re skimming “quick updates,” and the next you’ve missed the decision, the link, and the one task that was actually assigned to you. Finding it later is the worst part.
This WhatsApp recap automation hits project leads first, but operations managers and agency owners feel it too. Instead of rereading 200 messages, you get a clean daily summary saved to Google Drive, with the raw messages stored safely in Google Sheets.
Below you’ll see how the workflow works, what it fixes, and what you need to run it reliably with n8n, Evolution API, Google, and GPT-4o.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: WhatsApp to Google Drive, daily chat recaps
flowchart LR
subgraph sg0["Starts at 11pm Flow"]
direction LR
n1@{ icon: "mdi:cog", form: "rounded", label: "Agregar", pos: "b", h: 48 }
n2@{ icon: "mdi:cog", form: "rounded", label: "Google Drive", pos: "b", h: 48 }
n3@{ icon: "mdi:play-circle", form: "rounded", label: "Starts at 11pm", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "Define group", pos: "b", h: 48 }
n5@{ icon: "mdi:database", form: "rounded", label: "View conversations + filter", pos: "b", h: 48 }
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Single Text"]
n7@{ icon: "mdi:brain", form: "rounded", label: "ChatModel", pos: "b", h: 48 }
n8@{ icon: "mdi:robot", form: "rounded", label: "Summary", pos: "b", h: 48 }
n9@{ icon: "mdi:swap-vertical", form: "rounded", label: "Text", pos: "b", h: 48 }
n9 --> n2
n1 --> n6
n8 --> n9
n7 -.-> n8
n6 --> n8
n4 --> n5
n3 --> n4
n5 --> n1
end
subgraph sg1["Flow 2"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Webhook"]
n11@{ icon: "mdi:swap-vertical", form: "rounded", label: "Organize", pos: "b", h: 48 }
n12@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Validate Group", pos: "b", h: 48 }
n13@{ icon: "mdi:database", form: "rounded", label: "Save Conversations", pos: "b", h: 48 }
n0 --> n11
n11 --> n12
n12 --> n13
end
subgraph sg2["Flow 3"]
direction LR
n10["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Evolution Groups Search"]
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n3 trigger
class n8 ai
class n7 aiModel
class n12 decision
class n5,n13 database
class n0,n10 api
class n6 code
classDef customIcon fill:none,stroke:none
class n6,n0,n10 customIcon
The Challenge: Turning Chat Noise Into Decisions You Can Find
WhatsApp is great for speed and terrible for recall. Important details show up once, between memes and “👍”, then disappear under the next 50 messages. When you’re trying to run a project, a community, a class, or even a busy internal team, that becomes real work: scrolling, searching, asking people to repeat themselves, and guessing what was “final.” Honestly, the mental load is what gets you. You can’t relax because you’re always worried you missed something that mattered.
It adds up fast. Here’s where it breaks down in day-to-day use.
- Someone posts the key link once, and later nobody can find it without rereading half the day.
- Tasks get assigned in casual language, so ownership is unclear when you check in the next morning.
- You end up duplicating notes in another tool, and that copy-paste habit introduces mistakes.
- When a new person joins, you waste time summarizing history instead of moving forward.
The Fix: Automatically Log WhatsApp, Then Write a Daily Recap
This workflow collects WhatsApp group messages throughout the day via the Evolution API, then stores them in a Google Sheets log organized by date. At a scheduled time (typically at the end of the day), it pulls that day’s messages, merges them into a single readable feed, and sends the content to GPT-4o to generate a structured summary. Finally, it saves that summary as a document in Google Drive, so it’s easy to read, share, or archive. The result feels like someone on your team took clean meeting notes, except it happens automatically. And you still keep the full transcript in Sheets in case you ever need to verify context.
The workflow starts on a nightly schedule trigger. It validates the group, retrieves and aggregates the day’s chat from Google Sheets, and uses an AI summarization chain to turn the mess into a recap. Then Google Drive stores the summary doc, and the conversations are archived so tomorrow starts clean.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say you manage one active WhatsApp group that drops about 250 messages a day. If you spend even 10 seconds per message to skim for decisions, links, and tasks, that’s roughly 40 minutes daily, plus the time to write a recap. With this workflow, you do almost nothing: messages get logged in Google Sheets automatically, and the nightly run produces a Google Drive doc while you’re offline. Realistically, you spend maybe 5 minutes glancing at the recap and forwarding it where it needs to go.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Evolution API to access your WhatsApp group messages.
- Google Sheets for a dated message log and archive.
- Google Drive to store the daily recap document.
- OpenAI API key (get it from the OpenAI dashboard).
Skill level: Intermediate. You’ll connect accounts, add credentials, and paste a group ID into a few fields.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
A nightly run kicks things off. The schedule trigger starts the workflow at the time you choose, usually after your group quiets down for the day.
Your group is identified and validated. The workflow sets group details, optionally checks them against Evolution API (via HTTP request), and stops safely if the group doesn’t match what you expect.
Messages are pulled, cleaned, and combined. Google Sheets provides the day’s chat records, they’re aggregated, then turned into a single “message stream” that an AI model can summarize without losing the thread.
AI writes the recap, then Drive stores it. GPT-4o generates a structured summary (decisions, links, tasks, highlights), and Google Drive saves it as a document you can file by date or project.
You can easily modify the summary format to match your team’s style based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Webhook Trigger
This workflow accepts inbound requests to validate groups and archive conversations before the scheduled summarization runs.
- Add and open Incoming Webhook Trigger.
- Set the webhook path and method according to your WhatsApp or backend sender configuration.
- Connect Incoming Webhook Trigger to Arrange Payload to match the execution flow.
Step 2: Configure the Schedule Trigger and Group Inputs
The nightly run assembles group details, fetches chats, and prepares the summary pipeline.
- Add and configure Nightly Schedule Trigger with the desired recurrence.
- Open Assign Group Details and define the fields that identify the WhatsApp group (IDs, names, or metadata).
- Confirm the connection path Nightly Schedule Trigger → Assign Group Details → Retrieve Chats & Filter.
Step 3: Connect Google Sheets for Chat Retrieval and Archiving
Two Google Sheets nodes are used: one to retrieve recent chats and another to archive or log validated conversations.
- Open Retrieve Chats & Filter and connect the spreadsheet that stores incoming chat messages.
- Open Archive Conversations and select the sheet where validated conversations should be written.
- Ensure Group Validation Check routes to Archive Conversations as shown in the execution flow.
Step 4: Set Up Aggregation, Message Building, and AI Summarization
This section compiles messages, generates a single message body, and uses an AI model to summarize content.
- Verify Retrieve Chats & Filter outputs to Aggregate Records, then to Build Single Message.
- Review Build Single Message to ensure it concatenates messages in the format needed by your summary.
- Open Generate Summary and confirm it uses AI Chat Model as its language model connection.
Step 5: Configure Payload Assembly and Storage Outputs
The summarized output is formatted for storage and moved to Google Drive for record-keeping.
- Open Prepare Text Payload and map the summary text fields needed by your Drive storage or downstream use.
- Confirm the connection Generate Summary → Prepare Text Payload → Drive File Store.
- Configure Drive File Store to save the generated summary file to the desired folder.
Step 6: Validate Incoming Webhook Payloads and Optional Group Search
Inbound payloads are arranged and validated before conversations are archived. A utility HTTP node exists for optional group search.
- Open Arrange Payload and map webhook fields to the structure expected by Group Validation Check.
- Configure Group Validation Check conditions to filter valid group payloads before writing to Archive Conversations.
- Review Utility: Group Search API if you plan to use external validation; it includes retry behavior and continueErrorOutput to prevent workflow failure.
Step 7: Test & Activate Your Workflow
Run controlled tests for both the webhook path and the scheduled summary path before enabling the workflow in production.
- Click Test workflow and send a sample request to Incoming Webhook Trigger.
- Manually execute Nightly Schedule Trigger to verify Retrieve Chats & Filter → Aggregate Records → Build Single Message → Generate Summary completes.
- Confirm successful runs create a summary file in Drive File Store and archive valid entries in Archive Conversations.
- When ready, switch the workflow to Active for scheduled production use.
Watch Out For
- Google Sheets credentials can expire or need specific permissions. If things break, check the n8n Credentials panel and your Google account access to the target spreadsheet first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Common Questions
Usually about 30 minutes once your accounts and group ID are ready.
Yes. There’s no coding required, but you will need to paste IDs/keys and connect Google + Evolution API credentials in n8n.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API usage (often just a few dollars a month for one active group, depending on message volume).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
You can change the recap style by editing the prompt used in the summarization step (the “Generate Summary” AI chain). Many teams add sections like “Open questions,” “Decisions,” and “Owners + due dates,” so the output is instantly actionable. If you prefer a different storage location, swap the Google Drive step to a different folder or naming pattern. You can also adjust the Google Sheets retrieval to summarize only messages tagged to a specific project or keyword.
Usually it’s expired Google credentials or the wrong spreadsheet permissions. Reconnect Google Sheets in n8n, confirm the exact spreadsheet is shared with the connected Google account, and make sure the template tabs still exist. If it fails only on busy days, you may be pulling too many rows at once; filtering by date earlier in the workflow helps.
On a typical n8n Cloud plan, it’s fine for one to a handful of active groups running daily recaps.
Often, yes, because this kind of workflow benefits from multi-step logic: validating a group, aggregating rows, merging message text, then running an AI summarization chain and saving a Drive document. n8n also gives you a self-hosting path if you want more control and fewer execution limits. Zapier or Make can still work, but AI + aggregation flows tend to get expensive or awkward once you move beyond a simple “new message → summarize” idea. If you need approvals, archiving, and a reliable daily run, n8n is usually the cleaner fit. Talk to an automation expert if you want help choosing.
Once this is running, your WhatsApp chatter stops being a liability and starts becoming an asset. The workflow captures the details, writes the recap, and puts it somewhere you can actually use tomorrow.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
