Email Sentiment Router for Event Sales Leads Who is this for? Event organizers, conference managers, and sales teams drowning in sponsor/exhibitor/partner emails who need zero-drop leads + real-time pipeline analytics. Key nodes: Gmail Trigger - Google Gemini (2x) - Data Table - Google Sheets - Send Email - Slack Category: Sales / AI / Event Management Level: Advanced Credits: Milo Bravo (BRaiA Labs) What problem is this workflow solving? Email overload kills event revenue: 200+ weekly sponsor/partner emails go unread No sentiment/intent analysis = missed hot leads Manual routing wastes 10+ hours/week Zero visibility into pipeline trends This workflow auto-classifies, routes, and analyzes every inbound lead. What this workflow does?
Tags
Related workflows
See all AI Automation→Detect revenue leakage with Salesforce, Google Sheets, Gemini, and Slack
Quick overview This workflow manually audits Closed Won Salesforce opportunities against billed amounts in Google Sheets, uses Google Gemini to analyze any revenue gap, then alerts a Slack user and writes an audit note back to the Salesforce opportunity. How it works Starts when you run the workflow manually. Fetches up to 20 Salesforce opportunities where the stage is "Closed Won" and processes them in batches with a short delay to reduce API pressure. Looks up matching billing rows in Google Sheets and totals the billed amount for the same Deal ID, then calculates the missing revenue versus the Salesforce Amount. For deals with a positive revenue gap, sends the discrepancy details to Google Gemini to classify severity and generate a root cause, recommendation, and Salesforce-ready audit note. Parses the Gemini JSON response and builds a formatted Slack message containing the deal, gap, severity, and recommended action. Sends the Slack alert and updates the Salesforce opportunity description with the audit note and the expected, billed, and missing amounts. Setup Add credentials for Salesforce OAuth2, Google Sheets OAuth2, Google Gemini (PaLM) API, and Slack OAuth2. In Salesforce,
Monitor ride surge events and analyze ride errors with Sheets, Slack and Gemini
Quick overview This workflow pulls ride events and error records from Google Sheets, detects surge pricing and long waits, and notifies via Slack. For error records, it uses Google Gemini with real-time traffic and weather API lookups to diagnose the issue and send recommended actions to Slack. How it works Runs manually and reads ride records from a Google Sheets spreadsheet. Processes the rows one by one with a short delay and routes each record based on whether its type is an event or an error. For event records, checks if the ride price is more than 1.5× the normal price and the wait time is over 10 minutes. If surge conditions are met, sends a surge and delay notification to Slack and records a surge-alert log entry. If surge conditions are not met, records a normal “no alert needed” log entry. For error records, structures the ride and error context and asks Google Gemini to generate an incident summary, probable cause, and recommended actions, calling traffic and weather APIs as needed. Parses the Gemini response into JSON and posts the formatted error report to Slack. Setup Connect Google Sheets OAuth credentials and set the correct spreadsheet and sheet tab in the Google S
AI: Summarize podcast episode and enhance using Wikipedia
The workflow automates the process of creating a summarized and enriched podcast digest, which is then sent via email. Note that to use this template, you need to be on n8n version 1.19.4 or later.