9 templates found
Category:
Author:
Sort:

Automated meeting recording & AI summaries with Google Calendar, Vexa & Llama 3.2

Transform your meetings into actionable insights automatically! This workflow captures meeting audio, transcribes conversations, generates AI summaries, and emails the results to participants—all without manual intervention. What's the Goal? Auto-record meetings when they start and stop when they end Transcribe audio to text using Vexa Bot integration Generate intelligent summaries with AI-powered analysis Email summaries to meeting participants automatically Eliminate manual note-taking and post-meeting admin work Never miss important discussions or action items again Why Does It Matter? Save 90% of Post-Meeting Time: No more manual transcription or summary writing Never Lose Key Information: Automatic capture ensures nothing falls through cracks Improve Team Productivity: Focus on discussions, not note-taking Perfect Meeting Records: Searchable transcripts and summaries for future reference Instant Distribution: Summaries reach all participants immediately after meetings How It Works Step 1: Meeting Detection & Recording Start Meeting Trigger: Detects when meeting begins via Google Meet webhook Launch Vexa Bot: Automatically joins meeting and starts recording End Meeting Trigger: Detects meeting end and stops recording Step 2: Audio Processing & Transcription Stop Vexa Bot: Ends recording and retrieves audio file Fetch Meeting Audio: Downloads recorded audio from Vexa Bot Transcribe Audio: Converts speech to text using AI transcription Step 3: AI Summary Generation Prepare Transcript: Formats transcribed text for AI processing Generate Summary: AI model creates concise meeting summary with: Key discussion points Decisions made Action items assigned Next steps identified Step 4: Distribution Send Email: Automatically emails summary to all meeting participants Setup Requirements Google Meet Integration: Configure Google Meet webhook and API credentials Set up meeting detection triggers Test with sample meeting Vexa Bot Configuration: Add Vexa Bot API credentials for recording Configure audio file retrieval settings Set recording quality and format preferences AI Model Setup: Configure AI transcription service (e.g., OpenAI Whisper, Google Speech-to-Text) Set up AI summary generation with custom prompts Define summary format and length preferences Email Configuration: Set up SMTP credentials for email distribution Create email templates for meeting summaries Configure participant list extraction from meeting metadata Import Instructions Get Workflow JSON: Copy the workflow JSON code Open n8n Editor: Navigate to your n8n dashboard Import Workflow: Click menu (⋯) → "Import from Clipboard" → Paste JSON → Import Configure Credentials: Add API keys for Google Meet, Vexa Bot, AI services, and SMTP Test Workflow: Run a test meeting to verify end-to-end functionality Your meetings will now automatically transform into actionable summaries delivered to your inbox!

Oneclick AI SquadBy Oneclick AI Squad
3918

Summarize SERPBear data with AI (via Openrouter) and save it to Baserow

Who's this for? If you own a website and need to analyze your keyword rankings If you need to create a keyword report on your rankings If you want to grow your keyword positions SerpBear is an opensourced SEO tool specifically for keyword analytics. Click here to watch youtube tutorial Example output of A.I. Key Observations about Ranking Performance: The top-performing keyword is “Openrouter N8N” with a current position of 7 and an improving trend. Two keywords, “Best Docker Synology” and “Bitwarden Synology”, are not ranking in the top 100 and have a stable trend. Three keywords, “Obsidian Second Brain”, “AI Generated Reference Letter”, and “Actual Budget Synology”, and “N8N Workflow Generator” are not ranking well and have a declining trend. Keywords showing the most improvement: “Openrouter N8N” has an improving trend and a relatively high ranking of 7. Keywords needing attention: “Obsidian Second Brain” has a declining trend and a low ranking of 69. “AI Generated Reference Letter” has a declining trend and a low ranking of 84. “Actual Budget Synology”, “N8N Workflow Generator”, “Best Docker Synology”, and “Bitwarden Synology” are not ranking in the top 100. Use case Instead of hiring an SEO expert, I run this report weekly. It checks the keyword rankings of the past week and gives me recommendations on what to improve. How it works The workflow gathers SerpBear analytics for the past 7 days. It passes the data to openrouter.ai for A.I. analysis. Finally it saves to baserow. How to use this Input your SerpBearcredentials Enter your domain name Input your Openrouter.ai credentials Input your baserow credentials You will need to create a baserow database with columns: Date, Note, Blog Created by Rumjahn

Keith RumjahnBy Keith Rumjahn
861

Generate customizable random strings with interactive forms

contract input: length of the strings and number of copies output: random strings as specified. randomness determined by Crypto node (generate/base64) How to run the workflow Import the workflow into your n8n project Click the Form Trigger to specify the length of the strings and how many copies to generate The workflow runs then displays the generated random strings How to set up No additional set up is necessary to execute the workflow manually. integration Patterns of interests formTrigger node to submit a form, then use form (end) node to display results at the end of the triggered workflow. set(dup)-summarize(concatenate) to run a part of the workflow multiple times then merge the results to one piece of data

Ger LongstacksBy Ger Longstacks
454

Generate exam question papers with GPT-4 and email delivery

Who Is This For? This workflow is designed for educators, universities, examination departments, and EdTech institutions that need a faster, smarter, and standardized way to prepare exam question papers. What Problem Does This Solve? Creating balanced, outcome-based question papers can take hours or even days of manual effort. Faculty often struggle to: Ensure syllabus coverage across units Maintain Bloom’s Taxonomy alignment Keep a consistent difficulty balance Format papers in institution-specific templates How it works This workflow automatically generates an exam question paper based on syllabus topics submitted via a form and sends it to the entered email address. Here’s the flow in simple steps: Form Submission – A student or faculty fills out a form with subject code, syllabus topics, and their email. AI Question Generation – The workflow passes the syllabus to AI agents (Part A with 2 Marks, Part B with 13 Marks, and Part C with 14 Marks) to create question sets. The marks and the no. of question generated can be customized according to the convenience. Merging Questions – All AI-generated questions are combined into a single structured document. Format into HTML – The questions are formatted into a clean HTML exam paper (can also be extended to PDF). Send by Email– The formatted exam paper is sent to the user’s email (with option to CC/BCC). Set up steps Connect Accounts Connect your OpenAI (or LLM) credentials for AI-powered question generation. Connect your Gmail (or preferred email service) to send emails. Prepare Form Create an n8n form trigger with required fields: Subject with Code Syllabus for Unit 1, 2, 3… Email to receive the paper Customize Question Generation Modify the AI prompts for Parts A, B, and C to fit your syllabus style (e.g., 2-mark, 13-mark, 14-mark). Format the Exam Paper Adjust the HTML template to match your institution’s exam paper layout. Test & Deploy Submit a test form entry. Check the received email to ensure formatting looks good. Deploy the workflow to production for real usage. Need help customizing? <p> <a href="mailto:jgracewell02@gmail.com"> ✉️ Contact Me </a> <a href="https://www.linkedin.com/in/jeffin-gracewell-0634007b/" target="_blank"> 💼 LinkedIn </a> </p>

GracewellBy Gracewell
410

AI chatbot call center: Taxi service (Production-ready, part 3)

Workflow Name: 🛎️ Taxi Service Template was created in n8n v1.90.2 Skill Level: High Categories: n8n, Chatbot Stacks Execute Sub-workflow Trigger node Chat Trigger node Redis node Postgres node AI Agent node If node, Switch node, Code node, Edit Fields (Set) Prerequisite Execute Sub-workflow Trigger: Taxi Service Workflow (or your own node) Sub-workflow: Taxi Service Provider (or your own node) Sub-workflow: Demo Call Back (or your own node) Production Features Scaling Design for n8n Queue mode in production environment Service Data from external Database with Caching Mechanism Optional Long Terms Memory design Find Route Distance using Google Map API Optional Multi-Language Wait Output example Error Management What this workflow does? This is a n8n Taxi Service Workflow demo. It is the core node for Taxi Service. It will receive message from the Call Center Workflow, handling the QA from the caller, and pass to each of the Taxi Service Provider Workflow to process the estimation. How it works The Flow Trigger node will wait for the message from Call Center or other Sub-workflow. When message is received, it will first check for the matching Service from the PostgreSQL database. If no service or service is inactive, output Error. Next, always reset the Session Data in Cache, with channel_no set to taxi Next, delete the previous Route Data in Cache Trigger a AI Agent to process the fare estimation question to create the Route Data Use the Google Map Route API to calculate the distance. Repeat until created the route data, then pass to all the Taxi Service Provider for an estimation. Set up instructions Pull and Set up the required SQL from our Github repository. Create you Redis credentials, refer to n8n integration documentation for more information. Select your Credentials in Service Cache, Save Service Cache, Reset Session, Delete Route Data, Route Data, Update User Session and Create Route Data. Create you Postgres credentials, refer to n8n integration documentation for more information. Select your Credentials in Load Service Data, Postgres Chat Memory, Load User Memory and Save User Memory. Modify the AI Agent prompt to fit your need Set you Google Map API key in Find Route Distance How to adjust it to your needs By default, this template will use the sys_service table provider information, you could change it for your own design. You can use any AI Model for the AI Agent node Learn we use the prompt for the Load/Save User Memory on demand. Include is our prompt for the taxi service. It is a flexible design which use the data from the Service node to customize the prompt, so you could duplicate this workflow as another service. Create difference Taxi Providers to process the and feedback the estimate.

ChatPayLabsBy ChatPayLabs
398

Generate UTM-tagged Bitly links from Slack with GPT-4o-mini and Google Sheets logging

🔗 Slack + Bitly UTM Generator — Powered by OpenAI Description: This no-code n8n workflow transforms how marketing teams generate Bitly links with UTM parameters — directly from Slack. Powered by AI and fully automated, this system extracts relevant campaign data from a Slack message, creates a clean Bitly shortlink with UTM tags, and logs everything to a Google Sheet for tracking and reporting. Perfect for growth marketers, content teams, and anyone tired of manually building UTM-tagged links. If you like to follow step-by-step build of workflows like these, check out: https://www.youtube.com/@Automatewithmarc ⚙️ How It Works 🟢 Slack Trigger The workflow starts when a user mentions the bot in a Slack channel (e.g., @BitlyBot link this for IG campaign). 🧠 AI Agent (LangChain) Uses GPT-4o-mini to infer UTM values (e.g., utmsource, utmmedium, utm_campaign) Normalizes short forms like "IG" to "instagram" Follows UTM naming conventions (e.g., lowercase, underscore-separated) 🔍 Information Extractor Pulls cleanly structured UTM data from the AI response to prep for Bitly. 🔗 Bitly Tool Node Generates a short link using the inferred target URL + UTM values. 📋 Google Sheets Logger Automatically appends the full details (Bitly link, UTM parameters, campaign owner) to a Google Sheet for easy access. 📢 Slack Response Replies in-thread with the new Bitly link and campaign details, formatted clearly for the user. 🛑 Error Handling If Bitly link generation fails, the workflow gracefully stops with an error message. 🔧 Tools & Services Used Slack (Trigger + Response) LangChain AI Agent (with GPT-4o-mini) Bitly (via Bitly Tool Node) Google Sheets (auto-log generated links) OpenAI GPT-4o-mini (Language model for prompt understanding) 💡 Use Cases 🔗 Instantly create UTM-tagged links for campaigns 📊 Maintain a central Bitly + UTM link database in Google Sheets 🧠 Use AI to reduce manual tagging and formatting errors 🤝 Empower your team to request links via Slack, no forms needed ✅ Setup Instructions Slack: Set up a Slack bot and connect it using Slack Trigger and Slack response nodes. Bitly API: Generate a Bitly access token and set up credentials in the Bitly node. OpenAI / LangChain: Connect your GPT-4o or GPT-4 API key to the OpenAI Chat Model nodes. Google Sheets: Use OAuth2 credentials to connect to your Google Sheet. Make sure the sheet has matching columns for UTM parameters (sample headers included in the node schema).

Automate With MarcBy Automate With Marc
228

Generate professional invoices with Jotform, Xero, and GPT-powered emails

Generate Invoices for Customers with Jotform, Xero and Gmail This workflow automates the entire process of receiving a product/service order, checking or creating a customer in Xero, generating an invoice, and emailing it — all triggered by a form submission (via Jotform). How It Works Receive Submission Triggered when a user submits a form. Collects data like customer details, selected product/service, etc. Create/Update The Customer Creates/Updates the customer. Create The Invoice Generates a new invoice for the customer using the item selected. Send The Invoice Automatically sends the invoice via email to the customer. Who Can Benefit from This Workflow? Freelancers Service Providers Consultants & Coaches Small Businesses E-commerce or Custom Product Sellers Requirements Jotform webhook setup, more info here Xero credentials, more info here Make sure that products/services values in Jotform are exactly the same as your item Code in your Xero account Email setup, update email node (Send email), more info about Gmail setup here LLM model credentials

AppUnits AIBy AppUnits AI
168

Automate Gmail responses with GPT and human-in-the-loop verification

Try It Out! This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email. How it works Gmail Trigger monitors your inbox for new emails AI Analysis determines if a response is needed based on your criteria Draft Generation creates contextually appropriate replies using your business information Human Approval sends you the draft for review before sending Auto-Send replies automatically once approved Setup Connect your Gmail account to the Gmail Trigger node Update the "Your Information" node with: Entity name and description Approval email address Resource guide (FAQs, policies, key info) Response guidelines (tone, style, formatting preferences) Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials Test with a sample email Requirements n8n instance (self-hosted or cloud) Gmail account with API access LLM provider API key Need Help? Email Nick @ nick@tropicflare.com

Nick CanfieldBy Nick Canfield
88

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31
All templates loaded