Back to Catalog

Create & send client session summaries from Zoom meetings via Gmail and Airtable

LuisBetancourt.coLuisBetancourt.co
137 views
2/3/2026
Official Page

Description

Whenever a Zoom “Meeting assets” email arrives in your Gmail inbox, this workflow will:

  1. Trigger on new Gmail messages filtered by the subject “Meeting assets”.

  2. Extract from the email (HTML or plain text):

  3. Type of session (e.g. “1 hour”, “2 hours”, or “exploratory call”).

    • Client’s full name.
    • Session date & time (from the GMT… timestamp).
    • Duration (HH:MM:SS).
    • Recording link.
    • Quick summary.
    • Detailed summary.
    • List of next steps.
  4. Lookup the client in your Master Airtable base, table People, by full name.

  5. Send a personalized Gmail to the client with all extracted details.

  6. Create a new record in your Sessions table in Airtable, linking back to that client.

Quick Start

  1. Import this JSON into n8n as a new workflow.
  2. Connect your Gmail credentials (OAuth2).
  3. Connect your Airtable credentials (Personal Access Token).
  4. In the Search Records node:
  5. Base → your Master base ID.
  6. Table → “Your people table”.
  7. Filter By Formula → ={Full Name} = '{{ $json.clientName }}'.
  8. In the Create Record node: Table → “Sessions”.
  9. Map each field (dateTime, duration, summaries, next steps, client link).
  10. Activate the workflow.

Prerequisites

- n8n v1.50 or higher
- A Gmail account with OAuth2 credentials configured
- An Airtable base containing:
- Table People with a Full Name field (and email).
- Table Sessions with fields: DateTime, Duration, Quick Summary, Detailed Summary, Next Steps, and a Linked Record to People.
- An Airtable Personal Access Token with read/write access to that base.

Tips & Extensions

  • Timezone conversion: Use a Function node with moment-timezone to convert UTC if needed.

  • Error handling: Add a catch node to log or notify if any field fails to parse.

  • Alternate notifications: Swap the Gmail node for Slack, Microsoft Teams, or SMS integrations.

  • With this documentation, your team can import and deploy the workflow in minutes.

Enjoy!

n8n Workflow: Create and Send Client Session Summaries from Zoom Meetings via Gmail

This n8n workflow automates the process of generating and sending client session summaries after Zoom meetings, leveraging Gmail for communication. It's designed to streamline post-meeting follow-up, ensuring clients receive timely and relevant information.

What it does

This workflow simplifies the post-meeting follow-up by performing the following steps:

  1. Triggers on new Gmail messages: The workflow starts when a new email is received in a specified Gmail account. This acts as a trigger for processing potential meeting summary requests.
  2. Processes email content (Placeholder): A Function node is included, which typically would contain custom JavaScript logic to parse the incoming email, extract relevant meeting details (e.g., meeting ID, client name, summary content), or determine if a summary needs to be generated.
  3. Makes an HTTP Request (Placeholder): An HTTP Request node is present, which would usually be used to interact with an external API. In the context of creating session summaries, this could involve:
    • Fetching Zoom meeting recordings or transcripts.
    • Interacting with a Large Language Model (LLM) like OpenAI to generate a summary from a transcript.
    • Retrieving client information from a CRM or Airtable.
  4. Conditional Logic (Placeholder): An If node is included, allowing for conditional branching based on the data processed. This could be used to:
    • Check if all necessary information for a summary is available.
    • Determine if the email is indeed a summary request.
    • Decide whether to send the summary or handle an error.
  5. Sends Email via Gmail (Placeholder): A Gmail node is set up to send emails. In a complete workflow, this node would be responsible for sending the generated client session summary to the client, potentially including a link to the recording, key takeaways, and next steps.
  6. Sticky Note: A sticky note is included for documentation or temporary notes within the workflow.

Note: Based on the provided JSON, the Function, HTTP Request, and If nodes are present but do not contain specific configurations or code. They represent the intended logical flow and integration points within the workflow.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Gmail Account: Configured as a credential in n8n for both triggering on new emails and sending emails.
  • Zoom Account (Implied): If the goal is to summarize Zoom meetings, access to Zoom meeting data (recordings, transcripts) would be required, likely through an API.
  • Airtable Account (Implied by directory name): If client sessions are tracked in Airtable, an Airtable credential might be needed to update records or fetch client details.
  • OpenAI API Key or similar LLM (Implied): To generate summaries from meeting transcripts, an API key for a language model would be necessary.

Setup/Usage

  1. Import the workflow: Download the workflow JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up a Gmail OAuth2 credential for the Gmail Trigger node to listen for new emails.
    • Set up another Gmail OAuth2 credential for the Gmail node to send out the session summaries.
    • (If applicable) Configure credentials for any other services like Zoom, Airtable, or OpenAI if you implement those integrations within the placeholder nodes.
  3. Customize the Nodes:
    • Gmail Trigger: Configure the Gmail Trigger node to listen for specific emails (e.g., emails with a certain subject line or from a particular sender) that indicate a request for a session summary.
    • Function (Node 14): Add custom JavaScript code to this node to parse the incoming email, extract relevant meeting information, and prepare data for summary generation.
    • HTTP Request (Node 19): Configure this node to interact with external APIs. For example, to fetch Zoom meeting data, send transcripts to an LLM for summarization, or retrieve client data from Airtable.
    • If (Node 20): Define conditions in this node to control the workflow's flow based on the processed data (e.g., if (summaryGenerated === true)).
    • Gmail (Node 356): Customize the email content, recipient, and subject line to send the generated session summary. You will likely use expressions to dynamically insert information from previous nodes (e.g., client name, summary text).
  4. Activate the Workflow: Once configured, activate the workflow to start automatically processing new Gmail messages and generating/sending client session summaries.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942