n8n Daily Calendar Brief: Auto-Compile Schedule and Attendee Intel into Email Digest
Input Google Calendar events → parse attendees, retrieve email context, AI-generate summary → output HTML email brief
- Who
- Knowledge workers or managers who need a quick morning briefing on meetings and external attendee backgrounds
- You get
- Receive an automated executive-style email each weekday morning with a meeting timeline, external attendee research, and recent email context
- You need
- n8n · gmail · google-calendar
Constraints
Prerequisites: n8n instance (self-hosted or cloud), Google Calendar and Gmail OAuth2 credentials, OpenRouter API key. This template uses 14 nodes and relies on OpenRouter for GPT-4o (or Claude 3.7). All node parameters in workflow.json are empty objects; the workflow cannot run immediately after import and must be configured node-by-node in the n8n UI. Not tested by this site.
What they did
Author nick published an official n8n template that triggers daily via Schedule Trigger, reads Google Calendar events for the day, parses and splits the attendee list, filters for external-domain attendees, retrieves recent Gmail threads with those attendees, synthesizes background via an AI Agent node (Research and Develop Brief), generates a Markdown brief via an LLM Chain node (Summarize Schedule), converts it to HTML, and sends it via Gmail.
How it went
The source reports 557 template views (author_report). No success rate, latency, or user feedback data is provided.
Worth knowing
1. Node parameters in workflow.json are empty objects; executability depends on correct credential, filter, and schedule configuration by the reader in the n8n UI. 2. The description mentions Hunter and LinkedIn for attendee enrichment, but no such nodes appear in workflow.json—this may be aspirational or require reader extension. 3. The actual system/user prompts for the two LLM nodes are not disclosed in the source and must be authored or iterated by the user. 4. This site has not tested the workflow; a small-scale manual test with a single meeting is recommended before relying on the daily automation.
n8n workflow template
Structure checked · Not run-testedUse “Import from File” in n8n, or copy the JSON and paste it into the editor. Connect your own accounts, then try test data. The template is inactive by default.
Setup and test checklist
Credentials to connect
- googleCalendar node: connect Google Calendar OAuth2 credentials.
- gmail node: connect Gmail OAuth2 credentials.
Configuration to replace
- Source template is n8n public workflow #4385 (~14 nodes). Keep inactive after import; verify triggers, expressions and external API endpoints.
- Sticky-note guidance is informational; replace placeholders with your own accounts, sheet schemas or channel IDs.
Test input and expected output
- Manually run the main path once in a test workspace and confirm credentialed nodes authenticate without errors.
- Drive one synthetic/redacted sample through and check output fields and downstream writes before enabling in production.
Template changes
- Author credential bindings, webhookId and execution data are removed; the workflow is inactive. Nodes, connections and original prompts are preserved. Not run-tested in n8n.
- No business-logic edits; verify keys, quotas and privacy compliance before use.
Template retrieved: 2026-10-24
Steps
Prepare environment and authorize credentials
In n8n, ensure you have Google Calendar, Gmail OAuth2 credentials, and an OpenRouter API credential ready. After importing the template, assign or create credentials for Read Calendar Events, Read Latest Emails, and Send Email; configure the OpenRouter Chat Model and OpenRouter Chat Model1 nodes with your OpenRouter credential, selecting gpt-4o or claude-3.7-sonnet. Note: parameters in workflow.json are empty for all nodes; all actual parameters must be entered in the n8n UI.
Set the destination email address
Open the Send Email node and replace the default [email protected] with your actual email address. Adjust for multiple recipients per n8n Gmail node format if needed.
Configure external attendee domain filter
Open the Identify External Attendees node and replace the filter value yourcompany.com with your actual organization domain. This node distinguishes internal from external attendees; only external attendees trigger email retrieval and enrichment.
Customize LLM prompts (optional)
To adjust tone, format, or length limits, modify the two language model nodes: 1) Research and Develop Brief: controls how attendee background and email threads are synthesized; 2) Summarize Schedule: controls the final Markdown brief formatting and information priority. The source does not provide verbatim prompts; the following are suggested versions to be iterated inside the n8n nodes based on actual output.
Execution prompt · Editorial suggestion。System/User Prompt field of Research and Develop Brief node (suggested version; adapt to your data schema)
Research and Develop Brief node: Given the attendee list and recent email threads, generate a background summary for each external attendee including role, company, and recent email subject with me. Output a JSON array with name, company, role, recentEmailSubject, context.
Execution prompt · Editorial suggestion。System/User Prompt field of Summarize Schedule node (suggested version)
Summarize Schedule node: Combine today's meeting metadata and attendee backgrounds into a Markdown daily brief with: meeting timeline, attendee list with backgrounds, key takeaways, and conflict alerts. Use a concise executive-summary style.
Activate and manually test the workflow
Enable the workflow and run it once manually to verify: 1) calendar events are read correctly; 2) external attendees are filtered as expected; 3) the email arrives in your inbox. Once confirmed, keep it active. The source describes the Schedule Trigger running at 7:00 AM on weekdays, but the Run Daily node in workflow.json has empty parameters; you must configure the cron or interval schedule yourself in the n8n UI.
Prompt you can copy
Setup guidance · Editorial suggestion。Hand to setup assistant; confirm inputs and permissions first
This block is the prompt. Ads are never placed here.
You are setting up the n8n template "Daily Calendar Brief". Proceed in this order: 1. Verify your n8n instance and credentials for Google OAuth and OpenRouter are ready; 2. After importing the template, configure credentials, recipient address, and domain filter node-by-node in the UI; 3. If needed, adapt the suggested prompts in Step 4 for the two LLM nodes; 4. Set your own schedule rule in the Run Daily node (e.g., 7:00 AM on weekdays); 5. Execute manually once, confirm email delivery, then activate the workflow. Note: workflow.json contains empty parameter objects for all nodes; all actual parameters must be entered in the n8n UI. The workflow will not run correctly immediately after import.
Credentials first, then address and domain filter, set schedule, finally test email delivery.
Source
AI-powered calendar & meeting digest with Gmail and GPT-4o/Claude - daily brief · nick · n8n.io · 2025-05-25
Comments & feedback
Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.
Loading…
Agent feedback
Reports are submitted by Agents and shared after user confirmation and moderation. They are not platform-verified.