🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Gmail + LinkedIn to WhatsApp, meeting briefs ready

Gmail + LinkedIn to WhatsApp, meeting briefs ready - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Gmail + LinkedIn to WhatsApp, meeting briefs ready - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

You show up to a call, and five minutes in you realize you’ve already asked the same question in the last email thread. Again. It’s not your fault. The context is scattered across Gmail, calendar invites, and a half-remembered LinkedIn post you skimmed on your phone.

This Gmail LinkedIn WhatsApp automation hits account managers and founders the hardest, honestly. But consultants doing back-to-back discovery calls feel it too. The win is simple: you walk into meetings with a short, private brief that reminds you who’s who and what’s changed since you last spoke.

Below, you’ll see exactly what this workflow does, what you need to run it, and how the moving parts fit together (without getting buried in technical details).

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Gmail + LinkedIn to WhatsApp, meeting briefs ready

Why This Matters: Walking Into Meetings Cold

Meeting prep sounds easy until you have more than a couple calls a week. The invite lands, you tell yourself you’ll review it “later,” and later turns into two minutes before the call. So you search Gmail, skim the last thread, miss the key detail buried three replies down, then open LinkedIn and get distracted by everyone else’s posts. It’s a mental tax. Worse, the cost shows up as awkward openers, repeated questions, and opportunities you could’ve spotted if you’d remembered what mattered.

It adds up fast. Here’s where it usually breaks down.

  • Finding the most relevant Gmail thread per attendee is slow, especially when names don’t match email addresses cleanly.
  • LinkedIn context is useful, but checking profiles manually before every call is the first thing to get skipped.
  • When prep lives in five tabs, you’ll forget details under pressure and default to generic small talk.
  • Doing this for a day with 4–6 meetings can burn about an hour you don’t really have.

What You’ll Build: WhatsApp Meeting Briefs from Gmail + LinkedIn

This workflow acts like a quiet meeting assistant that watches your calendar, gathers context, and sends you a simple brief where you’ll actually read it: WhatsApp. Every hour, it checks for upcoming meetings on your personal calendar. When it finds one, it looks at the invitees and uses an AI agent to figure out who’s relevant and what info it should collect. For each attendee, it pulls your latest Gmail correspondence and also fetches recent LinkedIn activity using a scrape step. Then another AI step summarizes everything into a short “here’s what you need to remember” prep note. Finally, it sends that note to your WhatsApp, giving you time to review before you join the call.

The workflow starts on a schedule, so you don’t need to remember to run anything. In the middle, it combines two streams of context (email history and LinkedIn updates) and turns them into something readable. At the end, you get one discreet message that’s easy to scan on your phone.

What You’re Building

Expected Results

Say you have 4 meetings tomorrow with 2 attendees each. Manually, you might spend about 10 minutes per attendee searching Gmail and another 5 minutes checking LinkedIn, which is roughly 2 hours total prep. With this workflow, the schedule trigger runs automatically, the AI summarization happens in the background, and you spend maybe 2 minutes per meeting reading the WhatsApp brief. That’s around 90 minutes back on a busy day, and your openers get noticeably sharper.

Before You Start

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Google Calendar for upcoming meetings and attendee emails.
  • Gmail to fetch recent email correspondence.
  • WhatsApp Business to receive private meeting briefs.
  • OpenAI API key (get it from your OpenAI dashboard).

Skill level: Intermediate. You’ll connect accounts, add API keys, and copy a LinkedIn cookie string (or ask a technical teammate to help).

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

Calendar check runs hourly. A scheduled trigger fires and looks up upcoming events in Google Calendar, focusing on personal meetings where prep actually matters.

Attendees get parsed and validated. An AI extractor pulls attendee details from the invite, then the workflow checks if each person has a usable email address and a LinkedIn URL (or at least enough info to search).

Email and LinkedIn context gets gathered in parallel. One subflow searches Gmail for the latest correspondence and condenses the thread. Another subflow uses an HTTP request scrape (via Apify) to pull profile sections and recent activity, then summarizes it. If a source fails, the workflow inserts a polite fallback note rather than crashing.

A meeting prep brief is generated and delivered. All attendee summaries are merged, an AI agent turns them into a short prep message, and WhatsApp sends it to you so it’s waiting before the meeting.

You can easily modify the schedule cadence to match your calendar habits, or switch the trigger to “on-demand” using a webhook. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

Set the automation cadence for pulling upcoming meetings and starting attendee processing.

  1. Add and open Scheduled Automation Trigger.
  2. Set the Rule to run every hour using the existing interval configuration.
  3. Confirm Scheduled Automation Trigger connects to Retrieve Upcoming Meetings.

Step 2: Connect Google Calendar and Parse Attendees

Pull the next meeting and extract attendee details for downstream routing and enrichment.

  1. Open Retrieve Upcoming Meetings and set Operation to getAll with Limit set to 1.
  2. Set Calendar to [YOUR_EMAIL] and keep the time window filters: Time Min {{$now.toUTC()}} and Time Max {{$now.toUTC().plus(1, 'hour')}}.
  3. Credential Required: Connect your googleCalendarOAuth2Api credentials in Retrieve Upcoming Meetings.
  4. Open Parse Attendee Details and confirm the Text field contains the structured meeting string with expressions like {{ $json.start.dateTime }} and {{ $json.attendees.filter(item => !item.organizer).map(item => item.email).join(',') }}.
  5. Ensure LLM Chat Engine A is connected as the language model for Parse Attendee Details and select openAiApi credentials on LLM Chat Engine A.

Step 3: Configure Attendee Routing and Sub-Workflows

Split attendees and branch to email and LinkedIn sub-workflows in parallel.

  1. In Expand Attendee List, set Field To Split Out to output.attendees.
  2. Expand Attendee List outputs to both Assign Email Route and Assign LinkedIn Route in parallel.
  3. In Assign Email Route, keep JSON Output as {{ Object.assign({ "route": "email" }, $json) }}.
  4. In Assign LinkedIn Route, keep JSON Output as {{ Object.assign({ "route": "linkedin" }, $json) }}.
  5. Open Run Sub-Workflow (Configure Req) and Run Sub-Workflow (Configure Req) 2 and select the appropriate sub-workflow IDs for each path.
  6. Verify both sub-workflows merge in Combine Streams with Mode set to combine and Combine By set to combineByPosition.

Step 4: Set Up Email Recap Processing

Fetch and summarize the latest email thread per attendee, with fallbacks for missing data.

  1. In Route by Condition, keep both rules that check {{ $json.route }} equals email and linkedin.
  2. In Validate Email Address, ensure the condition checks {{ $json.email }} exists.
  3. Open Fetch Latest Correspondence and set Sender to {{ $json.email }} with Limit 1.
  4. Credential Required: Connect your gmailOAuth2 credentials in Fetch Latest Correspondence and Fetch Email Content.
  5. In Fetch Email Content, set Message ID to {{ $json.id }} and Operation to get.
  6. In Condense Email Fields, keep assignments like from {{ $json.from.value[0].name }} ({{ $json.from.value[0].address }}) and to {{ $json.to.value[0].name }} ({{ $json.to.value[0].address }}).
  7. Open Email Recap Agent and keep the Text template that includes {{ $json.text }}, then confirm LLM Chat Engine B is connected as its language model with openAiApi credentials.
  8. Ensure fallback nodes Email Fallback Notice and Email Missing Notice remain connected for empty results.

Step 5: Configure LinkedIn Enrichment and Summary

Scrape LinkedIn, extract profile sections, and summarize activity for meeting prep.

  1. In Validate LinkedIn URL, confirm the condition checks {{ $json.linkedin_url }} exists.
  2. Set Set LinkedIn Session values: linkedin_profile_url to {{ $json.linkedin_url }} and linkedin_cookies to [CONFIGURE_YOUR_TOKEN].
  3. Open Apify Web Scrape Call and keep the URL as https://api.apify.com/v2/acts/apify~web-scraper/run-sync-get-dataset-items and the JSON body with expressions like {{ $json.linkedin_profile_url }} and {{ $json.linkedin_cookies.match(/li_at=([^;]+)/)[1] }}.
  4. Credential Required: Connect your httpQueryAuth credentials in Apify Web Scrape Call.
  5. In Check Scrape Success, keep the condition checking {{ $json.body }} exists and route failures to LinkedIn Fallback Notice.
  6. Configure the HTML extraction chain: Extract Profile Details → Split Sections List → Extract Section Blocks, then note Extract Section Blocks outputs to both Select About Section and Select Activity Section in parallel.
  7. Keep the section selectors in Select About Section and Select Activity Section as the provided expression blocks; they feed Extract About Content and Parse Activity Items respectively.
  8. Ensure the activity chain continues through Split Activities List → Extract Activity Details → Aggregate Activity List and merges with Extract About Content in Combine Profile Data.
  9. Open LinkedIn Summary Agent and verify its Text includes content from Extract Profile Details and activity items, then confirm LLM Chat Engine C is connected as its language model with openAiApi credentials.
  10. Finish with Provide LinkedIn Summary to set linkedin_summary to {{ $json.text }}.

If the LinkedIn scrape fails or returns empty HTML, check your linkedin_cookies value in Set LinkedIn Session and ensure the session token is valid.

Step 6: Aggregate Attendees and Generate Meeting Prep Summary

Merge email and LinkedIn outputs per attendee and generate a meeting prep message.

  1. In Combine Attendee Summaries, keep JSON Output as {{ Object.assign({}, $('Expand Attendee List').item.json, $json) }} to merge per-attendee results.
  2. Aggregate all attendees in Aggregate Attendee Data using Aggregate aggregateAllItemData and Destination Field Name attendees.
  3. Open Meeting Prep Agent and verify the Text template pulls meeting details from Retrieve Upcoming Meetings and includes attendee summaries.
  4. Ensure LLM Chat Engine D is connected as the language model for Meeting Prep Agent with openAiApi credentials.

Step 7: Configure the WhatsApp Notification Output

Send the final meeting prep summary to WhatsApp.

  1. Open Send WhatsApp Notification and set Text Body to {{ $json.text }}.
  2. Set Phone Number ID to [YOUR_ID] and Recipient Phone Number to [YOUR_PHONE].
  3. Credential Required: Connect your whatsAppApi credentials in Send WhatsApp Notification.

⚠️ Common Pitfall: If WhatsApp messages fail, verify the sender phone number ID is approved for your WhatsApp Business account and the recipient is allowed.

Step 8: Test and Activate Your Workflow

Run a manual test to confirm end-to-end outputs, then turn on the schedule for production use.

  1. Click Execute Workflow to trigger Scheduled Automation Trigger and verify Retrieve Upcoming Meetings returns a meeting.
  2. Confirm parallel routing from Expand Attendee List produces both email and LinkedIn branches and merges in Combine Streams.
  3. Validate successful outputs: Provide Email Summary and Provide LinkedIn Summary should populate summaries per attendee, and Meeting Prep Agent should produce a final message.
  4. Check that Send WhatsApp Notification sends the meeting prep summary to your phone.
  5. Turn on the workflow using the Active toggle once the test succeeds.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

  • Gmail credentials can expire or need specific permissions. If things break, check the connected Google account and OAuth scopes in n8n credentials 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.

Next Steps

If the same “walk in prepared” goal applies to internal calls too, Google Calendar + Slack: meeting briefs ready to use keeps prep visible to your team where they already chat.

For sales teams that live in email, Google Calendar to Gmail, sales meeting briefs ready is a cleaner fit when you want the brief delivered right into the thread you’ll follow up from.

When your WhatsApp number is already a lead intake channel, WhatsApp + Airtable: qualify leads and book consults pairs well because it turns “random inbound messages” into scheduled calls your assistant can prep for.

Need outreach plus meeting prep? Google Sheets to WhatsApp, personalized outreach at scale helps you message many contacts, then this workflow makes sure you remember the context when they reply and book time.

Finally, if you’re also using WhatsApp for customer conversations, WhatsApp + Google Sheets: support replies, logged gives you a searchable history that can feed into future meeting briefs.


Quick reference:

Quick Answers

What’s the setup time for this Gmail LinkedIn WhatsApp automation?

Plan for about 45 minutes if your accounts and API keys are ready.

Is coding required for this meeting brief automation?

No. You’ll connect accounts and paste in a few credentials. The “hard part” is mostly configuration, not programming.

Is n8n free to use for this Gmail LinkedIn WhatsApp workflow?

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 costs (often a few cents per brief, depending on prompt size and how many attendees you process).

Where can I host n8n to run this automation?

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.

Can I modify this Gmail LinkedIn WhatsApp workflow for different use cases?

Yes, and you probably should. You can replace the scheduled trigger with a Webhook + “Respond to Webhook” to make an on-demand brief, and you can swap the LinkedIn scrape step (the HTTP Request/Apify call) for a different data source. Common tweaks include sending the brief to Telegram instead of WhatsApp, adding company lookups, and changing the AI prompt to match your tone.

Why is my Gmail connection failing in this workflow?

Usually it’s expired OAuth permissions or the wrong Google account connected. Reconnect Gmail in n8n credentials, then verify the workflow is allowed to read the mailbox you expect. If it fails only for some attendees, it can also be because the workflow can’t confidently match a name to an email thread.

What volume can this Gmail LinkedIn WhatsApp workflow process?

If you self-host, there’s no hard execution limit; it mostly depends on your server and how fast LinkedIn scraping returns. On n8n Cloud, your plan sets monthly execution limits, and multi-attendee meetings can trigger several runs per event. Practically, most people run this for personal calendars and a handful of meetings per day, because the scrape and AI calls are the pacing factors.

Is this Gmail LinkedIn WhatsApp automation better than using Zapier or Make?

Often, yes. This workflow has branching, sub-workflows, fallback paths, and multi-step AI summarization, which is the kind of logic that gets awkward (and expensive) in simpler tools. n8n also gives you more control over how you merge attendee data, and you can self-host to avoid per-task pricing. Zapier or Make can still work if you only want a basic “calendar event → send reminder” flow, but this is more of a meeting assistant than a reminder. If you want help deciding, Talk to an automation expert.

You set it up once, and the workflow keeps you ready without extra tabs, extra notes, or extra effort. Walk into the call with context, then focus on the conversation.

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.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.