by isaWOW
Fill in a simple form with your event name, session recording URLs, and attendee emails — the workflow handles everything else. It sends each session video to WayinVideo AI, which generates a written summary and key highlights for each one. OpenAI then uses those summaries to write a professional HTML digest email, which Gmail sends to every attendee automatically. Built for event organisers, marketing teams, and agencies who want to follow up with attendees after a webinar, summit, or conference without writing a single word manually. What This Workflow Does Parallel session summarisation** — Submits all three session recordings to WayinVideo at the same time, so you don't wait for each one to finish before the next starts AI-written digest email** — Passes all three session summaries to OpenAI GPT-4o-mini, which writes a complete, formatted HTML email with key takeaways and recording links for each session Automatic attendee delivery** — Sends the finished digest email to every email address you entered in the form — no copy-paste, no manual sending Structured HTML output** — The email arrives with proper formatting, session headers, bullet points, and "Watch Recording" buttons — ready to read in any email client Form-based job submission** — Anyone on your team can trigger the workflow using a web form — no access to n8n required Three sessions in one run** — Handles up to three recording URLs per event in a single workflow execution Custom sender name** — The email is sent with the sender name you provide in the form, so it arrives looking like it came from your team Setup Requirements Tools you'll need: Active n8n instance (self-hosted or n8n Cloud) WayinVideo account + API key OpenAI account + API key Google account connected to n8n via Gmail OAuth2 Estimated Setup Time: 15–20 minutes Step-by-Step Setup Get your WayinVideo API key Log in at WayinVideo, go to your account settings or developer section, and copy your API key. Paste the API key into node "2. WayinVideo — Submit Session " Open this node, find the Authorization header, and replace YOUR_WAYINVIDEO_API_KEY with your actual key. Paste the API key into node "3. WayinVideo — Submit Session " Open this node, find the same Authorization header, and replace YOUR_WAYINVIDEO_API_KEY. Paste the API key into node "4. WayinVideo — Submit Session " Open this node and replace YOUR_WAYINVIDEO_API_KEY in the Authorization header. Paste the API key into node "6. WayinVideo — Get Session 1 Summary" Open this node and replace YOUR_WAYINVIDEO_API_KEY. Paste the API key into node "7. WayinVideo — Get Session 2 Summary" Open this node and replace YOUR_WAYINVIDEO_API_KEY. Paste the API key into node "8. WayinVideo — Get Session 3 Summary" Open this node and replace YOUR_WAYINVIDEO_API_KEY. > ⚠️ This key appears in 6 nodes — you must replace it in all of: "2. WayinVideo — Submit Session ", "3. WayinVideo — Submit Session ", "4. WayinVideo — Submit Session ", "6. WayinVideo — Get Session 1 Summary", "7. WayinVideo — Get Session 2 Summary", and "8. WayinVideo — Get Session 3 Summary". Missing even one will cause the workflow to fail. Connect your OpenAI account Open node "11. OpenAI — GPT-4o-mini Model". Click the credential field and connect your OpenAI account. You will need an active OpenAI API key from platform.openai.com. Connect your Gmail account Open node "13. Gmail — Send Digest Email". Click the credential field and connect your Google account via OAuth2. Follow the on-screen prompts to authorise n8n to send emails on your behalf. Activate the workflow Toggle the workflow to Active. Open the form URL generated by node "1. Form — Event Details + Session URLs1" and submit a test event with one real recording URL to confirm the full workflow runs end to end. How It Works (Step by Step) Step 1 — Form Trigger (Web Form) The workflow starts when someone fills in the web form. You enter the event name, up to three session recording URLs and their titles, a comma-separated list of attendee email addresses, and the sender name. All fields for Session 2 and Session 3 are optional — but note that leaving them blank may cause errors (see Troubleshooting). The form is hosted by n8n and can be shared with anyone on your team. Step 2, 3, 4 — Submit Sessions to WayinVideo (Three parallel submissions) As soon as the form is submitted, the workflow sends all three session recording URLs to WayinVideo simultaneously — one request per session. Each request goes to the WayinVideo Summaries API, asking it to analyse the video and generate a written summary in English. WayinVideo returns a unique task ID for each session, which the workflow uses later to retrieve the results. Step 5 — Wait 90 Seconds The workflow pauses for 90 seconds to give WayinVideo time to process all three videos before it tries to fetch the results. This is a fixed wait — there is no retry loop in this workflow. If your session recordings are very long and take more than 90 seconds to process, some summaries may come back empty (see Troubleshooting for the fix). Steps 6, 7, 8 — Fetch All Three Summaries (Three parallel fetches) After the wait, the workflow calls the WayinVideo results endpoint for each session using the task IDs from Steps 2–4. Each call returns the session summary text, a list of highlight descriptions, tags, and other metadata. All three fetches run at the same time. Step 9 — Merge All 3 Summaries The three separate results are combined into a single data package. This step ensures that the AI email writer in the next step has access to all three summaries at once to write a unified, coherent digest email. Step 10 — AI Agent Writes the Digest Email (OpenAI GPT-4o-mini) The merged summaries, session titles, recording URLs, event name, and sender name are passed to an OpenAI GPT-4o-mini agent. The agent is given a detailed prompt and an exact HTML email template to follow. It fills in all the session details — key takeaways, bullet points from highlights, and recording links — and returns the finished HTML email as a structured JSON object. Step 11 — OpenAI Language Model This is the GPT-4o-mini model that powers the AI agent in Step 10. It processes the prompt and generates the email content. Step 12 — Output Parser This step ensures the AI's response is returned as a clean, structured JSON object with a single key called html_email. It prevents formatting errors before the email is sent. Step 13 — Gmail Sends the Digest Email The finished HTML email is sent via Gmail to every address you entered in the form. The email subject line uses the event name you provided, and the sender name matches what you typed in the form. Every attendee receives the same formatted digest with all three session summaries, takeaways, and recording links. The final result is a professional post-event digest email delivered to all attendees — written and sent entirely without manual effort. Key Features ✅ Three sessions in one run — Submit up to three recording URLs and get all three summarised and emailed in a single workflow execution ✅ Parallel processing — All three WayinVideo submissions and all three result fetches run at the same time, cutting total wait time significantly ✅ GPT-4o-mini email writing — OpenAI writes the complete HTML email body from the summaries — you never touch a keyboard after submitting the form ✅ Pre-formatted HTML email — The email arrives with a dark header, session blocks, bullet points, and "Watch Full Recording" buttons — no design work needed ✅ Custom sender name — The email is sent under your brand name or team name, not a generic n8n address ✅ Recording links included — Each session block in the email includes a direct link back to the original recording URL ✅ Team-friendly form — Any team member can trigger the workflow without needing access to n8n or knowing how automation works ✅ Structured output guaranteed — The Output Parser ensures the AI always returns clean HTML — no broken email formatting Customisation Options Upgrade to GPT-4o for better email quality In node "11. OpenAI — GPT-4o-mini Model", change the model value from gpt-4o-mini to gpt-4o for richer, more detailed email copy — useful for high-value client events. Add a BCC to copy your internal team In node "13. Gmail — Send Digest Email", open the options and add a BCC field with your team's internal email address — so your team always gets a copy of every digest sent. Log all digests to Google Sheets After node "13. Gmail — Send Digest Email", add a Google Sheets "Append Row" step to record the event name, session titles, send date, and recipient count — useful for tracking what was sent and when. Support a fourth session Duplicate node "4. WayinVideo — Submit Session " and node "8. WayinVideo — Get Session 3 Summary", connect them in the same pattern, add a Session 4 URL field to the form, and change the Merge step to accept 4 inputs instead of 3. Send in a language other than English In nodes "2. WayinVideo — Submit Session ", "3. WayinVideo — Submit Session ", and "4. WayinVideo — Submit Session ", change "target_lang": "en" to any supported language code (e.g. "hi" for Hindi, "es" for Spanish) to receive summaries in another language. Add a Slack notification after sending Insert a Slack node after "13. Gmail — Send Digest Email" to post a message in your team channel confirming the digest was sent, including the event name and number of recipients. Troubleshooting WayinVideo API key not working: Check that you replaced YOUR_WAYINVIDEO_API_KEY in all six nodes: "2. WayinVideo — Submit Session ", "3. WayinVideo — Submit Session ", "4. WayinVideo — Submit Session ", "6. WayinVideo — Get Session 1 Summary", "7. WayinVideo — Get Session 2 Summary", and "8. WayinVideo — Get Session 3 Summary" Confirm your WayinVideo account is active and the key has not expired Make sure there are no extra spaces before or after the key when pasting Email sent with blank session content: This happens when WayinVideo has not finished processing within 90 seconds — long recordings take more time Open the output of any "Get Summary" step and check if data.summary is empty Fix: Increase the wait time in "5. Wait — 90 Seconds" to 120 or 180 seconds for longer videos Workflow fails when Session 2 or Session 3 URL is left blank: Nodes "3. WayinVideo — Submit Session " and "4. WayinVideo — Submit Session " always run, even if the URL field is empty A blank URL will cause WayinVideo to return an error and stop the workflow Fix: Only use this workflow when you have all three session URLs ready, or add an IF check before each optional session submission step Gmail not sending: Make sure the Gmail OAuth2 credential in "13. Gmail — Send Digest Email" is connected and not expired — reconnect it in n8n credentials if needed Check that the attendee email addresses in the form are comma-separated and correctly formatted (e.g. one@email.com, two@email.com) Confirm your Gmail account has not hit its daily sending limit OpenAI step returning an error: Check that the OpenAI credential in "11. OpenAI — GPT-4o-mini Model" is connected and your API key is valid at platform.openai.com Make sure your OpenAI account has available credits — a depleted account will cause the AI step to fail silently If the structured output fails to parse, the html_email key may be missing — check the raw output of "10. AI Agent — Build Digest Email1" for error messages Support Need help setting this up or want a custom version built for your team or agency? 📧 Email:info@isawow.com 🌐 Website:https://isawow.com
by Rahul Joshi
Description Streamline IT and operations change management by automating approval routing, Jira issue creation, audit logging, and real-time Slack alerts. This workflow ensures faster reviews, traceable approvals, and transparent communication across systems. 🚀 What This Template Does Step 1: Triggers automatically every weekday at 3:00 AM to fetch new or updated change requests from Monday.com. ⏰ Step 2: Extracts key fields (request name, component, risk level, approvers, and description) for structured processing. 🧩 Step 3: Routes each request based on its current status — Pending, Approved, or Rejected. 🔀 Step 4: Sends Slack alerts for pending approvals with detailed context for quick action. 💬 Step 5: Creates Jira tickets for approved requests, ensuring smooth implementation tracking. 🎫 Step 6: Logs all approved requests to Google Sheets for compliance and audit purposes. 📊 Step 7: Sends confirmation emails to requesters with Jira ticket details via Gmail. 📧 Step 8: Automatically creates resubmission items in Monday.com for rejected requests. 🔁 Key Benefits ✅ Eliminates manual approval routing between tools ✅ Centralizes audit trails and implementation data ✅ Accelerates change management turnaround ✅ Provides real-time alerts to approvers and teams ✅ Ensures compliance with automated record-keeping Features Automated daily trigger (Mon–Fri, 3 AM) Monday.com integration for request intake Conditional branching by status (Pending, Approved, Rejected) Jira issue creation for approved requests Slack notifications for pending and approved updates Google Sheets logging for audit tracking Gmail email confirmations for requesters Automatic resubmission handling for rejected requests Requirements Monday.com API credentials with board access Jira API credentials with project permissions Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Gmail OAuth2 credentials for email automation Target Audience IT & DevOps teams managing structured change approvals Project management teams tracking implementation requests Organizations seeking automated risk-based change routing Managers needing centralized logs and instant Slack alerts Step-by-Step Setup Instructions Connect your Monday.com account and replace YOUR_BOARD_ID and groupId. Configure Jira credentials and set the target project for new tickets. Link your Google Sheets document and replace YOUR_SHEET_ID and YOUR_SHEET_GID. Add Slack credentials and update YOUR_CHANNEL_ID for notifications. Set up Gmail OAuth2 for sending confirmation emails. Adjust the cron expression (0 3 * * 1-5) if needed to match your timezone. Run the workflow manually once to test end-to-end connectivity. Enable for scheduled automation and enjoy a fully managed approval process.
by Mark Hansen
This n8n template demonstrates how to automate the followup when your customer completes a checkout in Stripe by emailing a receipt, logging the transaction, and sending an internal notification. See the video. Who it's for This workflow is for small to medium sized organizations using Stripe for payment processing and looking for a simple way to automate communication and logging that needs to happen post-checkout. How it works The workflow is triggered when a Stripe checkout is completed and again when Stripe creates an invoice. Checkout and invoice details are logged to a Google Sheet. A Slack message is sent to a channel where RevOps receive notifications about new sales. Lastly, a personalized email is sent to the customer with a link for downloading their receipt. How to set up Edit the two Stripe trigger nodes to enter your credentials. Create a Google Sheet named Payments with two tabs: transactions and invoices and the columns as shown in this example. Edit the three Google Sheets nodes to enter your credentials. The Gmail node also needs the credentials of the account that you want emails to come from. Lastly, enter credentials into the Slack node for the user that you want to be shown as posting Stripe transaction notifications. The Slack node is configured to send notifications to the revops channel, but you can change that to be whatever channel you want to use. Use your Stripe sandbox to test the workflow. In your sandbox, create a payment link that you can use to create the checkouts that will trigger the workflow. Make sure that your payment link has the option checked to create a post-payment invoice PDF. This will trigger the Invoice Created node. Requirements Stripe Account Google Workspace Account (Sheets, Mail) Slack Account
by WeblineIndia
Android Feature Flag Cleanup Automation This workflow automatically scans an Android GitHub repository, detects feature flags used in the codebase, compares them with Firebase Remote Config flags, identifies unused flags and sends a weekly cleanup report to Slack. This workflow runs every week and checks Android source files (.kt / .java) inside your GitHub repository. It finds possible feature flags used in code, compares them with Firebase Remote Config flags and highlights flags that may no longer be used. It then builds a clean summary report and sends the result to Slack for team review. You receive: Weekly automated Android flag audit** Unused Firebase flag detection** Slack summary report for cleanup review** Better visibility of active vs stale flags** Ideal for Android teams who want cleaner Firebase Remote Config management. Quick Start – Implementation Steps Login to your n8n account. Add your GitHub credential in n8n. Update repository owner, repo name and branch. Add Slack credentials and choose a channel. Add Firebase Remote Config API later (currently test data supported). Activate workflow for weekly automation. What It Does This workflow automates Android feature flag cleanup: Runs automatically every week. Connects to GitHub repository. Fetches all Android .kt and .java files. Reads source code files. Detects possible feature flags inside code. Loads Firebase Remote Config flags. Compares code flags vs Firebase flags. Finds unused Firebase flags. Creates final summary report. Sends report to Slack. This helps teams remove stale flags and maintain clean configuration. Who It's For This workflow is ideal for: Android development teams Tech leads QA teams DevOps / Release teams Firebase Remote Config users Teams maintaining multiple feature flags Requirements to Use This Workflow To run this workflow, you need: n8n account (cloud or self-hosted) GitHub repository access** Slack workspace** Firebase Remote Config project** (optional initially) Basic understanding of Android source files How It Works Weekly Trigger – Workflow starts automatically every week. Load Settings – Reads repository and workflow settings. Connect GitHub – Fetches project files. Filter Android Files – Only .kt and .java files selected. Read Code – Downloads and decodes file content. Detect Flags – Finds feature flags from source code. Load Firebase Flags – Uses Firebase Remote Config flags. Compare Flags – Finds used and unused flags. Create Report – Builds totals and cleanup summary. Send Slack Alert – Posts report to team channel. Setup Steps Import the workflow JSON into n8n. Open Workflow Settings node. Enter: GitHub Owner GitHub Repo Branch Name Connect GitHub credentials. Connect Slack credentials. Select Slack channel. Replace mock Firebase flags with real Firebase API later. Activate workflow. How To Customize Nodes Customize Scan Schedule Change Cron node: Weekly Daily Monthly Customize File Types Change file filter: .kt .java .xml .gradle Customize Flag Detection Improve regex to detect: BuildConfig.FEATURE_* RemoteConfig.getString() Custom wrappers Customize Slack Alerts You may add: Emojis Mentions Team tags Priority warnings Add-Ons (Optional Enhancements) You can extend this workflow to: Create Jira cleanup tickets Update Google Sheets catalog Create GitHub PR with markdown report Track first seen / last seen flags Team ownership by prefix Strict aging rules (30+ days unused) Multi-repository scanning Use Case Examples 1. Firebase Cleanup Remove old Remote Config flags not used in app code. 2. Weekly Engineering Report Send flag health report to Slack. 3. Release Readiness Check unused experiments before release. 4. Tech Debt Reduction Keep feature flag system clean and manageable. 5. Multi-Team Visibility Know which flags are active or stale. Troubleshooting Guide | Issue | Possible Cause | Solution | |------|----------------|----------| | No files found | Wrong repo/branch | Check settings | | Slack message failed | Wrong credentials | Reconnect Slack | | No flags detected | Regex too strict | Improve detection logic | | Too many files | Large repo | Reduce scan scope | | Firebase data empty | API not connected | Use mock data or fix API | | Workflow not running | Disabled trigger | Enable Cron node | Need Help? If you need help customizing this workflow by adding Jira, Google Sheets, GitHub PR creation, real Firebase API integration or scaling for enterprise use then our n8n workflow developers at WeblineIndia can help build an advanced production-ready version.
by George Dan
How it works Gmail is monitored every minute for new incoming emails Automated and irrelevant emails are filtered out (newsletters, noreply senders, out-of-office replies, bounce notifications) AI reads the email and drafts a reply based on your company documentation - embedded directly in the system prompt, no vector database needed The original email and the draft reply are logged to a Google Sheet for human review Type "send" in the Send column to approve a reply - the workflow detects it and sends it via Gmail The row is updated to "Replied" to prevent duplicate sends Set up steps Connect your Gmail, OpenRouter, and Google Sheets credentials (~5 min) Create a Google Sheet with columns: Message ID, From, Subject, Body, Reply, Send In the Draft AI Reply node, replace the sample company documentation in the system prompt with your own In the Filter Unwanted Emails node, update the first condition with your own email address Activate the workflow
by WeblineIndia
Post-Delivery CSAT Automation System > n8n + Gmail + Google Sheets + Typeform This n8n workflow automates the entire post-delivery customer feedback loop. It sends a survey email after delivery, logs it in Google Sheets, captures CSAT responses, updates records and alerts your team instantly for low ratings. Quick Implementation Steps Login to your n8n account. Import the workflow JSON into n8n Configure Webhook URLs (Delivery + CSAT response) Connect Google Sheets OAuth and set correct sheet Configure Gmail credentials for sending emails Replace the Typeform placeholder link with your real survey URL Activate workflow and test with sample data What It Does This workflow builds a complete post-delivery customer experience system using two connected pipelines. The first pipeline starts when a delivery webhook receives a “delivered” status. It validates the event, extracts customer details, prevents duplicate survey sends, waits for a defined delay and sends a personalized CSAT survey email. Every sent survey is logged into Google Sheets for tracking and analytics. The second pipeline handles incoming CSAT responses. It validates the data, maps it to the correct order, updates the sheet and classifies customer satisfaction into Low, Neutral or High categories. If a customer gives a low rating, the system instantly triggers an internal alert via Gmail, enabling quick action. Who It's For eCommerce businesses handling deliveries Customer Experience (CX) teams Operations and support teams Startups wanting automated feedback loops Agencies building automation systems for clients Requirements Before using this workflow, ensure you have: n8n account (self-hosted or cloud) Google Sheets account with a structured sheet: order_id, email, sent_at, survey_link, csat_score, feedback Gmail account with OAuth configured in n8n Webhook source (delivery system / backend / logistics tool) Typeform (or any survey tool) with a working form URL Basic understanding of n8n nodes and credentials How It Works & Set Up Workflow Breakdown This system consists of two workflows combined into one automation pipeline: 1. Delivery → Survey Workflow Webhook receives delivery event Filters only “delivered” + valid email Extracts order details Checks Google Sheets for duplicate survey If not sent: Waits 4 hours Sends survey email Logs the event in Google Sheets 2. CSAT Response Workflow Webhook receives survey response Validates required fields Finds matching order in Google Sheets Updates CSAT score + feedback Classifies response: Low (≤2) → Sends alert email Neutral (3) → Stored only High (≥4) → Stored only Setup Instructions Step 1: Configure Webhooks Delivery Webhook: /delivery-webhook CSAT Webhook: /csat-response Connect these to your backend or survey tool Step 2: Google Sheets Setup Create a sheet with columns: order_id | email | sent_at | survey_link | csat_score | feedback Connect via OAuth in n8n Step 3: Gmail Configuration Add Gmail OAuth credentials Use for: Survey email sending Low CSAT alerts Step 4: Replace Typeform Link Update this placeholder with your real survey URL: https://form.typeform.com/to/abc123?order_id= Step 5: Test Workflow Send sample delivery webhook Submit sample CSAT response Verify: Email delivery Sheet updates Alert trigger Step 6: Activate Workflow Turn on workflow in n8n Monitor executions How To Customize Nodes Delay Node** Adjust wait time (currently 4 hours) Email Content Node** Modify subject, tone, branding (Webline India) CSAT Classification Engine** Change scoring logic (e.g., NPS style) Google Sheets Node** Add more columns like product, region, etc. Alert Node (Gmail)** Replace with Slack, WhatsApp or CRM integrations Add-ons (Extend Functionality) You can enhance this workflow with: Slack alerts for low CSAT WhatsApp notifications for instant escalation Dashboard (Google Data Studio / Power BI) Auto-ticket creation in Zendesk/Freshdesk High CSAT → send thank-you or referral email AI sentiment analysis on feedback Use Case Examples Post-delivery feedback automation for eCommerce Logistics experience tracking SaaS onboarding feedback collection Customer satisfaction monitoring system Service-based business feedback loop And many more variations depending on your business model Troubleshooting Guide | Issue | Possible Cause | Solution | |------|--------------|---------| | Survey email not sent | Condition failed (not delivered) | Check webhook payload status | | Duplicate surveys sent | Sheet lookup failed | Verify order_id mapping | | CSAT not updating | Sheet match not found | Ensure order exists before response | | Gmail not sending | OAuth issue | Reconnect Gmail credentials | | No alert for low CSAT | Switch condition mismatch | Verify classification logic | | Webhook not triggering | Incorrect URL | Recheck webhook path | Need Help? If you need help setting up this workflow, customizing it or adding advanced features like Slack alerts, dashboards or AI-powered insights then our n8n workflow developers at WeblineIndia can assist you. We specialize in building scalable automation systems, workflow optimization and custom integrations tailored to your business. Reach out to get: Custom workflow development Advanced automation consulting End-to-end system integration
by The O Suite
Driver-Clear — Pre-Trip Vehicle Inspection System A self-hosted FMCSA-aligned pre-trip inspection system for commercial truck fleets. Drivers complete a federally required vehicle inspection checklist before every dispatch — the workflow scores the results using local AI, triggers hard stops automatically, and alerts dispatch instantly when action is needed. What It Does Digitizes the FMCSA-required pre-trip inspection (49 CFR Parts 396.11 & 396.13) Collects truck number, odometer, fuel level, and a full 20-point vehicle systems checklist Detects hard stop conditions — alcohol disclosure, substance use, hazmat without endorsement, unsecured cargo, missing DVIR review, and HOS violations Scores each inspection based on defect count, hours of service, and cargo compliance Uses local AI to summarize defects and generate a plain-English alert for dispatch Sends instant push notifications and email alerts when a vehicle or driver is flagged Logs every inspection to an encrypted local database with a dispatcher dashboard Tracks odometer readings per unit for fleet maintenance visibility Built for Compliance Every submission captures the five federal driver certifications required under 49 CFR 392.3, 382.201, 392.4, 395.8, and 383 — creating a digital audit trail that supports DOT compliance documentation. Setup Time 30–60 minutes What You Need Before Starting A PC or server running Windows or Linux (8GB RAM minimum, 16GB recommended) Docker Desktop, Python 3.9+, and ngrok A Gmail account with App Password enabled and the free ntfy app An Ollama-compatible machine for local AI analysis (no data leaves your network) Privacy First Fully self-hosted — driver records, vehicle data, and inspection history never leave your facility's network. No cloud dependency, no subscription, no third party ever sees your data. Encrypted local storage included. What's Included Full setup instructions are inside the workflow. The DriverClear web application (app.py, templates, and dashboard) is provided separately and completes the system. Visit driver-clear.com for details. Trial Copy, will be updated.
by Nikan Noorafkan
🛍️ Google Shopping Feed Optimization with Channable + Relevance AI + Google Merchant API 🚀 Automate, Optimize & Sync Your Product Feeds at Scale 🧩 Overview This workflow automates Google Shopping Feed Optimization using Channable, Relevance AI, and the Google Merchant API. It runs daily, enhancing product titles and descriptions, validating feed quality, assigning custom campaign labels, and syncing the optimized feed with Google Merchant Center. The system ensures every product listing meets Google’s content standards, is SEO-friendly, and ready for high-performance Shopping campaigns. 🧠 Key Benefits ✅ Automated daily product feed optimization ✅ AI-enhanced titles and descriptions (via Relevance AI) ✅ Google Merchant API integration (latest version) ✅ Quality scoring and error detection before sync ✅ Custom campaign labels for segmented bidding ✅ Slack alerts for issues and daily summaries ✅ 100% no-code deployment with scalable batch processing ⚙️ System Architecture | Component | Purpose | | ----------------------------- | -------------------------------------------------------- | | n8n | Workflow automation and orchestration | | Channable | Product feed source (can replace with any eCommerce API) | | Relevance AI | AI title and description optimization | | Google Merchant API (NEW) | Product publishing and validation | | Slack | Alerts and reporting | | Cron Trigger | Daily schedule (6 AM sync) | 🧭 Workflow Logic (Visual Summary) Daily Trigger (06:00 AM) ⬇️ 1️⃣ Get Product Feed (Channable) Fetches product data for optimization. ⬇️ 2️⃣ Data Quality Checks Validates titles, GTINs, pricing, categories, and descriptions. Assigns quality scores. ⬇️ 3️⃣ Split Products Breaks the all_products array into single items for AI processing. ⬇️ 4️⃣ Optimize Title (Relevance AI Tool) Enhances product titles for SEO, clarity, and Google compliance. ⬇️ 5️⃣ Generate Description (Relevance AI Tool) Creates 300–400 character, benefit-focused product descriptions. ⬇️ 6️⃣ Assign Custom Labels Adds five segmentation labels: margin, performance, seasonality, stock level, and category. ⬇️ 7️⃣ Aggregate Products Combines optimized items into one unified dataset. ⬇️ 8️⃣ Upload to Merchant Center (NEW Merchant API) Publishes products via Google’s latest /products endpoint. ⬇️ 9️⃣ Check Product Status Verifies successful uploads and identifies disapprovals. ⬇️ 🔍 Analyze Product Issues Summarizes errors and warnings from Merchant API results. ⬇️ ⚖️ IF Disapprovals Found → 🚨 Send Slack alert for issues → ✅ Otherwise, post success summary 🧩 Environment Variables Set these under n8n → Settings → Variables → Add Variable | Variable | Example | Purpose | | ----------------------------------- | -------------------------------------------------- | -------------------------------- | | CHANNABLE_API_URL | https://api.channable.com/v1 | Channable API base | | CHANNABLE_COMPANY_ID | 12345 | Company ID in Channable | | CHANNABLE_PROJECT_ID | abcd | Project ID | | FEED_ID | shopping-feed | Feed endpoint | | RELEVANCE_AI_API_URL | https://api-f1db6c.stack.tryrelevance.com/latest | Relevance AI API base | | RELEVANCE_TOOL_TITLE_OPTIMIZER_ID | tQy48Ld8n0zp | Relevance AI Title Tool ID | | RELEVANCE_TOOL_DESCRIPTION_ID | hJ9bT01r8Lqf | Relevance AI Description Tool ID | | MERCHANT_API_URL | https://merchantapi.googleapis.com/content/v2.1 | Google Merchant API base | | MERCHANT_ACCOUNT_ID | 123456789 | Merchant Center account ID | | SLACK_CHANNEL | #shopping-feed-automation | Slack channel for reports | 🔑 Credential Setup | Service | Type | Setup | | ------------------- | ---------------- | -------------------------------------------------------------- | | Relevance AI | HTTP Header Auth | Header → Authorization: Bearer {{$env.RELEVANCE_AI_API_KEY}} | | Channable | HTTP Header Auth | Header → Authorization: Bearer {{$env.CHANNABLE_API_TOKEN}} | | Google Merchant | Google OAuth2 | Scopes: • https://www.googleapis.com/auth/content | | Slack | Slack API | Add chat:write Bot Token Scope | 🧱 Node-by-Node Breakdown | Node | Description | Key Action | | ----------------------------- | ---------------------------------------- | ----------------------------------------------------------- | | Daily Trigger (6 AM) | Starts workflow every morning | cron: 0 6 * * * | | Get Product Feed | Fetches products from Channable | GET {{$env.CHANNABLE_API_URL}}/.../feeds/{{$env.FEED_ID}} | | Data Quality Checks | Validates GTINs, titles, pricing, images | Returns quality_score + all_products | | Split Products | Splits array into individual products | Operation: splitOut, Field: all_products | | Optimize Title | Calls Relevance AI title tool | /tools/{{$env.RELEVANCE_TOOL_TITLE_OPTIMIZER_ID}}/trigger | | Generate Description | Calls Relevance AI description tool | /tools/{{$env.RELEVANCE_TOOL_DESCRIPTION_ID}}/trigger | | Assign Custom Labels | Adds 5 Smart Bidding Labels | Margin, performance, seasonality, stock, category | | Aggregate Products | Combines optimized product data | For batch upload | | Upload to Merchant Center | Posts via NEW Merchant API | /accounts/{id}/products | | Check Product Status | Retrieves upload results | Lists disapproved or pending items | | Analyze Product Issues | Summarizes product disapprovals | Returns disapproval_count and warnings | | IF Disapprovals Found | Conditional routing | Sends alert or success message | | Slack - Alert | Sends error summary to Slack | Includes product name and issue detail | | Slack - Success Summary | Posts daily completion message | Includes counts and optimizations applied | 🧰 Testing Procedure 1️⃣ Temporarily disable the cron schedule 2️⃣ Run manually using “Execute Workflow” 3️⃣ Start with 3–5 products 4️⃣ Check: Slack → Success message Google Merchant → Updated products n8n Execution logs → No failed nodes Once validated → Re-enable the 6 AM trigger 🧾 Example Output Slack Success Message ✅ Shopping Feed Optimization Complete 📊 Summary: • Total Products Processed: 135 • Products with Quality Issues: 12 • Disapprovals: 0 • Warnings: 3 🎯 Optimizations Applied: • Titles optimized for SEO • Descriptions enhanced • Custom labels added API: NEW Merchant API (merchantapi.googleapis.com) Next Run: Tomorrow 6 AM Timestamp: 2025-10-22T06:00:00Z Slack Alert Message 🚨 Merchant Center Disapprovals Alert Total Disapprovals: 5 Total Warnings: 2 Critical Issues: • Product: Wireless Headphones (ID: 4829) Issue: Missing GTIN • Product: Yoga Mat Eco (ID: 7350) Issue: Invalid price Action Required: Review disapproved products in Merchant Center. Timestamp: 2025-10-22T06:00:00Z 📊 Success Metrics | Metric | Goal | | ---------------------------- | ------------------- | | Feed approval rate | ≥ 90% | | AI optimization success rate | ≥ 95% | | Manual review reduction | 80% | | Daily automation uptime | 99.9% | | Scalable throughput | 5,000+ products/day | 🧩 Maintenance Schedule | Frequency | Task | | ------------- | ------------------------------ | | Daily | Monitor Slack alerts | | Weekly | Check disapproval logs | | Monthly | Refresh API tokens | | Quarterly | Tune AI prompts and thresholds | 🪜 Next Steps ✅ Deploy workflow in production 📈 Connect to your performance dashboard 🌍 Extend to multi-language feeds (Relevance AI translations) 💡 Add conversion optimization loop in Google Ads 🔗 References n8n Documentation Relevance AI Documentation Google Merchant API Docs Channable Help Center 🎉 Conclusion You now have a production-grade, AI-driven Shopping Feed Optimization workflow built on: Channable** for structured data ingestion Relevance AI** for content intelligence Google Merchant API** for publishing n8n** as the automation engine 💡 Result: A fully autonomous product feed system that self-improves daily, keeping your listings compliant, optimized, and performing at scale.
by Jitesh Dugar
Startup Pitch Deck Submission Validator & Auto-Processor Overview A comprehensive n8n workflow template that completely automates the startup pitch deck submission process for accelerators, incubators, VC firms, and startup competitions. This workflow validates founder emails, stores pitch decks securely, generates professional PDF summaries, and sends notifications to both your team and the founders—all in under 30 seconds per submission. Key Features Email Verification & Spam Protection Real-time email validation** using VerifiEmail API Checks for RFC compliance, MX records, disposable emails, and spoofed addresses Automatically rejects invalid submissions before file storage Prevents spam, fake entries, and temporary email addresses Automated File Management Downloads pitch deck PDFs from provided URLs Uploads to organized Google Drive folders with automatic naming Creates two permanent archives: Original pitch decks in /PitchDecks/ Generated summaries in /Submission Summaries/ Maintains clean folder structure with timestamp-based filenames Professional PDF Reports Generates beautiful, branded PDF summary reports Includes company info, founder details, email verification status Professional gradient design with interactive elements Links to Google Drive documents for easy access Smart Email Notifications Admin Team Notification**: Comprehensive email with all details and clickable document links Founder Confirmation**: Professional thank-you email with next steps and timeline Invalid Submission Alerts**: Immediate notification for failed verifications with detailed reasons Intelligent Routing Conditional logic based on email validation results Valid submissions proceed through full workflow Invalid submissions trigger admin alerts and stop processing No wasted resources on fake submissions Error Handling Comprehensive error detection at every step Admin alerts for failed email verifications Graceful handling of file download failures Detailed logging for troubleshooting Perfect For Startup Accelerators** (Y Combinator, Techstars, 500 Startups style programs) Incubators & Innovation Hubs** Venture Capital Firms** (deal flow management) Pitch Competitions** (local, national, international events) Investment Rounds** (seed, Series A applications) Government Innovation Programs** Corporate Accelerators** University Entrepreneurship Programs** Workflow Statistics Total Nodes**: 11 Complexity**: ⭐⭐⭐ Medium Processing Time**: 15-30 seconds per submission Setup Time**: 15-20 minutes Code Required**: None (no-code solution) Maintenance**: Minimal (set and forget) Requirements Required Services & APIs VerifiEmail API Purpose: Email verification Sign up: https://verifi.email Google Drive Purpose: File storage Setup: Enable Drive API in Google Cloud Console Gmail Purpose: Email notifications Setup: Enable Gmail API in Google Cloud Console HTML to PDF API (pdfmunk.com) Purpose: PDF generation Sign up: https://pdfmunk.com Optional Integrations Typeform** - For frontend submission forms Google Forms** - Alternative form solution Webflow** - For custom landing pages Airtable** - For additional database logging Slack** - For team notifications What Gets Created Folder Structure in Google Drive My Drive/ ├── PitchDecks/ │ ├── TechVenture_JohnDoe_PitchDeck.pdf │ ├── AIStartup_JaneSmith_PitchDeck.pdf │ └── GreenTech_MikeJones_PitchDeck.pdf │ └── Submission Summaries/ ├── TechVenture_Summary_20251012_143025.pdf ├── AIStartup_Summary_20251012_145532.pdf └── GreenTech_Summary_20251012_151147.pdf Email Notifications Admin Team Email (to: accelerator@yourdomain.com) All startup details Founder information with verified email badge Clickable buttons to view pitch deck and summary Email verification breakdown (RFC, MX, disposable check) Google Drive folder structure overview Document IDs for reference Founder Confirmation (to: founder's email) Personalized thank you message Submission confirmation checklist Detailed submission summary table Clear next steps with timeline (5-7 day review) PDF summary attached for records Contact information for questions Invalid Email Alert (to: admin@yourdomain.com) Failed submission details Email verification failure reasons Timestamp for tracking Option for manual review Quick Start Guide 1. Import Template Download the JSON file In n8n: Workflows → Import from File Select: startup-pitch-deck-validator-template.json 2. Configure Credentials (15 minutes) A. VerifiEmail API Sign up at https://verifi.email Get API key from dashboard In n8n: Credentials → VerifiEmail API → Paste key B. Google Drive OAuth2 Go to https://console.cloud.google.com Create project → Enable Drive API Create OAuth 2.0 credentials In n8n: Credentials → Google Drive OAuth2 → Follow flow C. Gmail OAuth2 Same Google Cloud project Enable Gmail API In n8n: Credentials → Gmail OAuth2 → Authorize D. HTML to PDF API Sign up at https://pdfmunk.com Get API key In n8n: Credentials → HTML to PDF API → Paste key 3. Create Google Drive Folders Create these folders in your Google Drive: /PitchDecks/ (for original pitch decks) /Submission Summaries/ (for generated reports) Then select them in the workflow nodes. 4. Update Email Addresses Replace placeholder emails in these nodes: Notify Accelerator Team**: Change accelerator@yourdomain.com Alert Admin - Invalid Email**: Change admin@yourdomain.com Founder confirmation template**: Update support@youraccelerator.com 5. Test the Workflow Send a test webhook: curl -X POST https://your-n8n.com/webhook/startup-submission -H "Content-Type: application/json" -d '{ "name": "Jane Smith", "email": "jane@example.com", "startup_name": "TechVenture AI", "website": "https://techventure.io", "industry": "Artificial Intelligence", "pitch_deck_file_url": "https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf" }' 6. Activate Workflow Click the toggle in top-right corner to activate! Detailed Setup Instructions Step 1: VerifiEmail Configuration Visit https://verifi.email and create account Navigate to API section in dashboard Copy your API key In n8n workflow, click "Verifi Email" node Create new credential → Paste API key Test credential to ensure it works Step 2: Google Cloud Project Setup Create Google Cloud Project Go to https://console.cloud.google.com Click "New Project" Name it: "n8n Startup Workflow" Click "Create" Enable Required APIs Go to "APIs & Services" → "Library" Search and enable: "Google Drive API" Search and enable: "Gmail API" Create OAuth Credentials Go to "APIs & Services" → "Credentials" Click "Create Credentials" → "OAuth 2.0 Client ID" Application type: "Web application" Add authorized redirect URI from n8n Download credentials JSON Configure in n8n In workflow, click any Google Drive node Create new credential → Google Drive OAuth2 Upload credentials JSON or paste values Complete OAuth flow and authorize Repeat for Gmail nodes using same project Step 3: Folder Setup Open Google Drive in browser Create folder: "PitchDecks" (note the folder ID from URL) Create folder: "Submission Summaries" In workflow, select these folders in the respective nodes: "Upload Pitch Deck to Drive" → PitchDecks folder "Save Summary PDF to Drive" → Submission Summaries folder Step 4: PDF API Setup Sign up at https://pdfmunk.com Get API key from account dashboard In "HTML to PDF" node, create new credential Paste API key Test with sample execution Step 5: Email Customization In "Notify Accelerator Team" node: Line 7: Change recipient email Update company name in footer (optional) In "Send Founder Confirmation" node: Line 69-70: Update support email Line 72: Update company name and year In "Alert Admin - Invalid Email" node: Line 3: Change recipient email Step 6: Test & Validate Test with Valid Email: Use your own email address Valid pitch deck URL Verify you receive confirmation email Check Google Drive for files Test with Invalid Email: Use temporary email service Verify admin receives alert Confirm no files are stored Test Error Handling: Use invalid file URL Check error messages Verify graceful failure Workflow DiagramStart → Webhook Trigger ↓ Email Verification (VerifiEmail API) ↓ Conditional Check (Valid?) ↙️ ↘️ TRUE FALSE ↓ ↓ Download PDF Alert Admin ↓ (end) Upload to Drive ↓ Generate Summary PDF ↓ Download Summary ↓ Save to Drive ↓ Notify Admin Team ↓ Confirm to Founder ↓ Done! ✅ Processing Flow Details For Valid Submissions (TRUE Branch): Webhook receives data → ~0s Email verification → ~2-3s Download pitch deck → ~3-5s Upload to Google Drive → ~2-3s Generate PDF summary → ~5-8s Download PDF → ~1-2s Save PDF to Drive → ~2-3s Send admin notification → ~2-3s Send founder confirmation → ~2-3s Total: 15-30 seconds For Invalid Submissions (FALSE Branch): Webhook receives data → ~0s Email verification → ~2-3s Send admin alert → ~2-3s Total: 4-6 seconds (saves resources!) Customization Options Easy Customizations Email Templates Modify HTML in Gmail nodes Add your logo Change colors and branding Adjust text and messaging PDF Template Edit HTML in "HTML to PDF" node Add custom styling Include additional fields Add company logo/branding Folder Structure Create subfolders by industry Add year-based organization Implement custom naming conventions Notification Preferences Add Slack notifications Set up SMS alerts Create calendar events Log to Airtable/database Advanced Customizations Add Duplicate Detection Check if email already submitted Prevent multiple submissions Create whitelist/blacklist Implement Scoring System Add rating fields to PDF Create evaluation criteria Automate preliminary screening Multi-Stage Workflow Add approval process Create interview scheduling Implement status updates Analytics & Reporting Track submission metrics Generate monthly reports Monitor email verification rates Analyze industry trends Troubleshooting Common Issues & Solutions 1. Email Verification Fails Problem**: All emails marked as invalid Solution**: Check VerifiEmail API key and quota 2. Google Drive Upload Error Problem**: "Insufficient permissions" error Solution**: Re-authorize OAuth, ensure Drive API enabled Check**: Folder exists and is accessible 3. PDF Generation Fails Problem**: PDF not generated or broken Solution**: Check HTML to PDF API key and quota Verify**: HTML template syntax is valid 4. Emails Not Sending Problem**: Gmail node fails Solution**: Re-authorize Gmail OAuth, check API quota Check**: Email addresses are valid format 5. File Download Fails Problem**: "Cannot fetch file from URL" Solution**: Verify URL is publicly accessible Check**: File exists and is not behind authentication 6. Webhook Not Triggering Problem**: No workflow execution Solution**: Check webhook URL is correct Verify**: Workflow is activated (toggle ON) Performance & Scalability Current Capacity Concurrent Submissions**: Up to 10-20 simultaneously Daily Volume**: ~500-1000 submissions (depends on API quotas) File Size Limit**: Up to 100MB per pitch deck Storage**: Unlimited (within Google Drive quota) Scaling Considerations For High Volume (1000+ submissions/day): Upgrade to paid API tiers Use queue system for processing Add database for tracking Implement rate limiting For Large Files (>100MB): Use direct file upload to Drive Skip PDF generation for large files Add file size validation Security & Privacy Data Protection Email verification via secure API Encrypted file transfer (HTTPS) OAuth2 authentication for Google services No data stored in n8n beyond execution logs Compliance GDPR compliant (data minimization) No sensitive data retention Secure credential storage Audit trail via execution logs Community Support n8n Forum: https://community.n8n.io Discord: https://discord.gg/n8n GitHub Issues: https://github.com/n8n-io/n8n 📄 License This template is provided as-is for commercial and personal use.
by Rahul Joshi
Description This workflow automates the tracking and follow-up process for pending payments. It pulls lead payment data from Google Sheets, checks whether the status is “Open,” and then routes actions accordingly. For open payment cases, it creates a dedicated ClickUp task and sends an email confirmation to stakeholders. For non-open cases, it notifies the team via Slack. This ensures payment verifications are never missed, while keeping all updates transparent and centralized. What This Template Does (Step-by-Step) 📊 Fetch Lead Data from Google Sheets Retrieves lead records including: Lead Name Company Name Payment Verification Status Status (Open/Closed) ⚖️ Check if Status = Open ✅ TRUE (Open): Creates a ClickUp task and sends an email confirmation. ❌ FALSE (Not Open): Sends a Slack notification only. 🗂 Create ClickUp Task for Payment Verification: Adds a task with lead and company details for pending payment follow-up in the specified list. ✉️ Send Email Confirmation: Notifies the assigned watcher (via Gmail) with task details (name, ID, and link). 💬 Send Slack Notification: Alerts the Slack workspace if a lead’s status is not “Open,” providing visibility on non-actionable cases. Prerequisites Google Sheet with lead/payment data ClickUp account & API credentials Gmail API credentials Slack API credentials n8n instance (cloud or self-hosted) Step-by-Step Setup Connect Google Sheets → Fetch payment verification data. Apply Status Filter (If Node) → Route based on “Open” status. Open Status → Create ClickUp Task → Send Email confirmation. Not Open Status → Send Slack notification. Customization Ideas 🎯 Add additional filtering (e.g., only create tasks if payment verification = “Pending”). 📢 Send Slack alerts for all new leads, not just closed ones. 📚 Log completed payment verifications into Airtable or Notion for reporting. 💡 Include payment due dates or invoice numbers in ClickUp task details. Key Benefits ✅ Automates payment follow-up process ✅ Keeps stakeholders informed via email ✅ Provides real-time Slack alerts for non-actionable cases ✅ Centralizes pending payment tasks in ClickUp ✅ Reduces manual monitoring and ensures no pending case is missed Perfect For 👥 Finance teams handling multiple payment verifications 🏢 Companies wanting a transparent and automated payment tracking process 🎯 Teams already using ClickUp for task management 📊 Managers who need visibility into pending vs. closed payment statuses
by Calistus Christian
How it works Checks if a website is up, sends the HTTP result to an AI model (ChatGPT) for analysis, and emails a clear success or failure message. Great for a quick “is this site up?” check you can trigger from any system via HTTP. Webhook — Receives a POST with the target URL. HTTP Request — Attempts to fetch the URL. Message a model — Uses ChatGPT to explain the status and cause of any error. IF — Checks if the HTTP status code equals 200. Gmail Success — Sends a success email with AI explanation. Gmail Error — Sends an error email with AI explanation and next steps. Set up steps Estimated setup: 5–10 minutes. Beginner friendly — no advanced config required. Add your Webhook URL where needed and connect your Gmail account. Keep detailed instructions and configuration notes inside Sticky Notes in your workflow. Inputs Send a POST request to your Webhook with: { "url": "https://example.com" }
by Nitesh
🧠 How It Works This AI Agent automatically qualifies property buyer leads from form submissions and sends them directly to your CRM. 🔄 Workflow Steps Form Submission Trigger When a user submits their details via a property inquiry form, the workflow is activated. AI Lead Classification The buyer’s input (budget, location, timeline, etc.) is analyzed by OpenAI. Structured data is extracted, and a lead score (0–100) is generated. Lead Qualification Logic Leads with a score ≥ 70 are marked as qualified. Leads with a lower score can be ignored or stored separately for later review. Follow-Up Actions (for Qualified Leads) An email notification is sent to the real estate agent. A record is created in Airtable to act as a lightweight CRM. ⚙️ How to Set Up 1. Form Setup Replace the default trigger with your preferred source: Typeform, Google Forms, Webflow form, etc. Ensure your form collects the following fields: Name, Email, Budget, Location, Timeline, Property Type 2. Connect Your Credentials Add your OpenAI API key for the LLM node Connect your Gmail account for notifications Link your Airtable base & table to store qualified leads 3. Customize Scoring Logic (Optional) Edit the Information Extractor prompt to tweak how scoring is calculated Example: prioritize budget fit, location, or timeline 4. Test the Workflow Submit a test entry via the form Confirm: You receive the notification email A new lead record appears in Airtable 5. Activate & Go Live Turn on the workflow Start qualifying real buyer leads in real-time 🎯 🚀 Use Cases Realtors → Filter out unqualified leads automatically Agencies → Save time by only engaging with high-quality inquiries Teams → Centralize qualified leads in Airtable for instant collaboration