This article provides a complete, practical walkthrough of the Splitout Googlecalendar Automate Webhook n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Advanced setup in 1-2 hours. One‑time purchase: €69.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:
   Build an AI Meeting Assistant with n8n: Pre-Meeting WhatsApp Notifications Using Gmail, Google Calendar, LinkedIn & GPT-4
   
   Meta Description:
   Learn how to build an AI-powered meeting assistant in n8n that checks your calendar, summarizes recent emails and LinkedIn activity, and sends personalized WhatsApp notifications before each meeting using GPT-4.
   
   Keywords:
   n8n workflow, AI meeting assistant, Gmail automation, Google Calendar reminders, GPT-4, LinkedIn scraping, Apify, WhatsApp notifications, pre-meeting summary, email summarization, LinkedIn profile scraping, workflow automation, meeting productivity
   
   Third-Party APIs Used:
   1. Gmail API – for reading and analyzing last email correspondence with meeting attendees.
   2. Google Calendar API – to fetch upcoming meetings and their details.
   3. OpenAI GPT-4 API – used multiple times for summarizing emails, LinkedIn activity, and generating the final WhatsApp message.
   4. Apify API – for scraping LinkedIn profiles (About and Activity sections) with a headless browser.
   5. WhatsApp Business Cloud API – for sending the final message to users via WhatsApp.
   
   Short Article:
   
   ---
   
   Meet Your New AI Meeting Assistant: n8n Workflow for Smarter Pre-Meeting Notifications
   
   In the digital workplace, staying on top of meetings and being prepared can dramatically improve productivity, foster better relationships, and reduce stress. But when your schedule is packed with back-to-back calls, reviewing emails or stalking LinkedIn profiles for talking points can feel impossible.
   
   Enter: your AI Meeting Assistant, powered by n8n.
   
   This no-code/low-code automation workflow uses n8n and several third-party services to build a smart assistant that preps you for your next meeting, sending personalized and information-rich summaries via WhatsApp—just in time.
   
   Let’s break down how the workflow works, what tools are involved, and why it just might become your favorite productivity hack.
   
   The Workflow Overview
   
   This AI Assistant executes several core tasks seamlessly, all triggered hourly:
   
   1. 🗓️ Check Your Upcoming Meetings  
   A Schedule Trigger kicks off the workflow every hour. It checks your Google Calendar for any upcoming meetings within the next hour using the Google Calendar API. If a meeting is found, the workflow dives into deeper preparation tasks.
   
   2. 👥 Extract Attendee Information  
   The workflow extracts vital attendee details such as emails, names, and LinkedIn URLs from the meeting invitation using n8n’s LangChain Information Extractor node, powered by OpenAI’s GPT-4.
   
   3. 📧 Summarize Recent Email Correspondence  
   The Assistant uses the Gmail API to pull the latest email thread with each attendee. It then employs GPT-4 to condense the email into a smart summary—highlighting any agreed-upon tasks or important talking points.
   
   4. 💼 Scrape and Summarize LinkedIn Activity  
   This is where Apify comes in. Using their Web Scraper API, the workflow impersonates your LinkedIn login (authenticated via cookie input) to scrape an attendee’s profile, focusing on the “About” section and recent posts. Again, GPT-4 analyzes this content to extract noteworthy achievements, updates, or conversation starters.
   
   5. 🔗 Aggregate & Merge Contextual Data  
   Once the email and LinkedIn summaries are ready, they are merged with each attendee’s data to form a complete snapshot. Multiple flows ensure modularity, and the subworkflow pattern helps manage complexity.
   
   6. 💬 Generate a Smart Meeting Summary  
   Using all available data, the workflow triggers GPT-4 one more time to act as your personal assistant, generating a short and engaging summary of the meeting, who’s attending, what you’ve discussed with them recently, and what they’ve been up to online.
   
   7. 📲 Send a WhatsApp Notification  
   Finally, the generated summary is sent to your WhatsApp using the WhatsApp Business Cloud API. The message is formatted to be easy to skim, informative, and casually written—like a smart assistant dropping you a helpful text before your call.
   
   Why This Workflow Rocks
   
   - ✨ AI-Enhanced Context: Combines personal correspondence and public LinkedIn activity for hyper-relevant insights.
   - 🧠 GPT-4 Powered: Smart, readable summaries powered by the industry's leading LLM without writing code.
   - 📱 WhatsApp Notifications: Perfect for professionals on the go—get all the prep you need in a simple message.
   - 🔁 Repeatable & Scalable: Checks every hour and scales to as many meetings or attendees as needed.
   
   Privacy Note:
   This workflow uses LinkedIn cookies to scrape profiles, which may violate LinkedIn’s terms of service. Proceed mindfully in development or consider alternatives for production environments.
   
   Who Is This For?
   
   - Executives and professionals in fast-paced environments
   - SDRs and account executives preparing for client calls
   - Founders fundraising or networking via recurring meetings
   - Anyone who wants to automate meeting prep with AI 💼🤖
   
   Conclusion:
   With a little automation magic and the power of GPT-4, your n8n AI assistant becomes the ultimate sidekick—always vigilant, always prepared, and always texting you right before every meeting.
   
   —
   
   Ready to build your own AI meeting assistant?
   
   Check out n8n.io and explore the documentation, community forum, and Discord to start customizing this workflow for your needs.
   
   Happy automating! 💡⚙️📆

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.