Browse 12,955 Workflows

By Tangma Craftsman

Quick overview This workflow runs manually to evaluate Google Sheets editorial prospects against regional WooCommerce product catalogs, fetches page metadata from each prospect URL, uses OpenAI to score editorial relevance, and upserts a single review-ready opportunity record per prospect into an Opportunities sheet. How it works Starts on a manual trigger. Loads published products from two WooCommerce stores (EU and NA) and reads prospect rows from the Google Sheets Pending_Leads tab. Validates each prospect (region, URL safety, required fields, and permission status) and picks the best matching product from the correct regional catalog. For valid prospects, fetches the prospect’s editorial page HTML and extracts the page `` and meta description. Sends the page metadata, prospect topic, and selected product details to OpenAI to return a JSON relevance score, rationale, pitch angle, and anchor suggestions. Combines quantitative prospect signals (domain rating and organic traffic) with the AI relevance score to set a status and review flags. Upserts the evaluated result into the Google Sheets Opportunities tab using opportunity_key, and writes invalid or unapproved prospects there with a “Needs input or permission review” status. Setup Configure WooCommerce credentials for both regional stores (EU and NA) and ensure the store domains match the host checks used for product permalinks. Configure a Google Sheets OAuth credential, replace REPLACE_WITH_SPREADSHEET_ID, and ensure the spreadsheet has Pending_Leads and Opportunities tabs. Add required columns to Pending_Leads (prospect_id, target_url, target_region, brand, model, part_category, permission_status) and optional scoring fields (domain_rating, organic_traffic, placement_type, link_attribute). Create an opportunity_key column in the Opportunities tab and keep it as the match column for append-or-update behavior. Add an OpenAI API key as an HTTP Bearer Auth credential and attach it to the OpenAI request node. An n8n automation workflow template by Tangma Craftsman.

By Muhammad Hammad

Quick overview This workflow turns new prospects in Google Sheets into Groq-written cold emails sent or drafted in Gmail, monitors Gmail for replies, then uses Groq to classify and draft responses while sending Telegram alerts and requiring a Telegram button approval before any reply draft is sent. How it works Triggers when a new row is added to a Google Sheets Prospects tab. Validates required prospect fields, generates a personalized cold email with Groq, and writes the subject/body back to Google Sheets. Sends the email via Gmail when the row’s Auto Send field is true, otherwise creates a Gmail draft, and updates the prospect’s status and timestamps in Google Sheets. Every 2 minutes, reads prospect rows marked Sent - Awaiting Reply from Google Sheets and searches Gmail for inbox replies matching the prospect via the REF- subject tag. For a new reply, Groq classifies it (interested, question, declined, unclear) and produces a reply draft when appropriate, then records the reply details in Google Sheets and notifies you in Telegram. Creates a Gmail draft reply in the original thread and stores the draft ID in Google Sheets, then posts the draft text to Telegram with an inline “Send reviewed draft” approval button. When you press the Telegram approval button, the workflow verifies the latest reply and sends the exact saved Gmail draft via the Gmail API, then updates Google Sheets and confirms the send in Telegram. Setup Create a Google Sheets spreadsheet with a Prospects tab and the required columns (including Prospect ID, Email, Service Offer, Auto Send, Status, Sent At, Draft Subject, Last Reply ID, and Reply Draft ID). Add credentials for Google Sheets (OAuth2), Gmail (OAuth2 with access to gmail.googleapis.com), Telegram (bot token), and Groq (HTTP Header Auth with Authorization: Bearer ). Select your spreadsheet and sheet in every Google Sheets node and ensure update operations match rows by Prospect ID. Replace YOUR_TELEGRAM_CHAT_ID in the Telegram trigger, message nodes, and the approval-check code so approvals only work from your chat. Update the Groq prompts and Gmail email template branding (for example, replace “Wiga Studio”) to match your organization before activating. An n8n automation workflow template by Muhammad Hammad.

By FLOW AI Automation

Quick overview This workflow runs daily to read leads from Google Sheets, research company websites, score and qualify them with OpenAI, and draft or send personalized initial and follow-up emails via Gmail while writing statuses, scores, drafts, and send results back to Google Sheets. How it works Runs every day on a schedule and loads configuration values (sheet, thresholds, limits, email copy, and dry-run mode). Reads lead rows from Google Sheets, normalizes emails, suppresses opt-outs/duplicates, and routes each row to either initial outreach or follow-up eligibility checks. For new leads, fetches the company website via HTTP, extracts usable text, and sends it to OpenAI to produce a grounded company analysis with a 0–100 fit score. Updates the lead row in Google Sheets with the analysis, evidence quotes, score breakdown, and a QUALIFIED/UNQUALIFIED (or error) status. For qualified new leads, asks OpenAI to draft a personalized first-contact email, validates it, and either saves an OUTREACH_PREVIEW (dry run) or reserves the row and sends the email through Gmail. Records Gmail message/thread IDs, timestamps, and follow-up due date in Google Sheets after a successful initial send (or flags SEND_REVIEW on uncertain outcomes). For contacted leads that are due, reads the original Gmail thread to detect replies, drafts a single follow-up with OpenAI when no reply is found, and either saves a FOLLOWUP_PREVIEW (dry run) or sends the follow-up via Gmail and updates Google Sheets with the result. Setup Create a Google Sheets spreadsheet with a tab named “Leads” and the expected columns (including lead_id, status, contact_allowed, do_not_contact, website, and the outreach/follow-up fields), ensuring each non-empty row has a unique lead_id. Add and select Google Sheets credentials and set the spreadsheet ID and sheet name in the configuration step. Add and select an OpenAI API credential for the OpenAI HTTP requests and choose the model name you want to use in the configuration. Add and select Gmail OAuth2 credentials, set sender_name and sender_email to match the connected Gmail account, and start with dry_run=true to review drafts before sending live. Set your timezone in the workflow settings and adjust the schedule time, qualification threshold, follow-up delay, and per-run limits to match your outreach process. An n8n automation workflow template by FLOW AI Automation.

By Zvid

Quick overview For podcasters and content teams: turn the newest RSS episode into captioned vertical audiogram clips using ElevenLabs transcription, OpenRouter highlight selection and Zvid rendering. How it works Run manually or daily to select the newest audio episode from your RSS feed. Download a bounded sample and check its actual size before transcription; the default sample is 4 MiB. ElevenLabs Scribe supplies word timestamps for accurate captions and clip boundaries. Upload the same audio to Zvid, then let OpenRouter select moments using transcript word positions. Build and validate each branded audiogram and obtain its render-credit quote. With dryRun=true, return editor drafts and quotes; AI and transcription charges may still apply. By default, render clips sequentially, retry explicit capacity rejections within a deadline, and return completed MP4s. Setup Install @zvid/n8n-nodes-zvid from Settings → Community nodes before configuring credentials. A workspace owner/admin may need to install it. Create a Zvid API credential at https://app.zvid.io/api-keys with Base URL https://api.zvid.io. Select it on every Zvid node and Upload episode audio. Connect ElevenLabs Header Auth named xi-api-key, with Speech to Text permission, to Transcribe (Scribe). Connect OpenRouter to Pick moments. Set feedUrl, showNameOverride, handle and branding in Config. Test manually. dryRun=false renders and spends Zvid credits. Keep maxAudioBytes within your plan and use media you have permission to repurpose. Requirements An n8n workspace supporting community nodes, Zvid render credits, ElevenLabs Speech to Text and OpenRouter access. Highlights are limited to the transcribed sample. Customization Adjust colors, fonts, clip count, clip duration and sample limits in Config. Additional info Open Watch video → Binary → data → View and select each clip. Social publishing is not included. Multipart audio upload uses HTTP Request because the published Zvid node lacks that operation. Setup guide: https://github.com/Zvid-io/zvid-n8n/blob/master/workflows/podcast-audiogram-clips.md. An n8n automation workflow template by Zvid.

By Nilyo

Quick overview This workflow triggers on new emails via Nilyo (Gmail, Outlook, or IMAP), uses OpenAI GPT to classify each message as urgent or not, and sends a WhatsApp alert through Nilyo only when the email needs a reply today. How it works Triggers when Nilyo receives an email.new event from a connected Gmail, Outlook, or IMAP mailbox. Sets the WhatsApp recipient name used for alerts. Sends the email sender, subject, snippet, and a cleaned body excerpt to OpenAI and asks for a strict JSON verdict with urgent and a short reason. Checks the model’s JSON response and stops the run if the email is not marked urgent. Sends an urgent-only WhatsApp message via Nilyo containing the subject, sender, and the model’s reason. Setup Install and enable the Nilyo community node (n8n-nodes-nilyo) in your n8n instance. Create a Nilyo personal token, add it as an n8n Nilyo API credential, and connect your mailbox provider(s) and WhatsApp in Nilyo. Add an OpenAI API credential in n8n and ensure the selected model (gpt-4.1-mini) is available to your account. Set the WhatsApp recipient name in the workflow’s Settings step (alert_recipient) to match a contact in Nilyo. Activate the workflow so Nilyo can register the email event subscription for the configured destination name. An n8n automation workflow template by Nilyo.

By Saeed

Quick overview This workflow runs on a schedule to pull your website inventory from Lindo, probe each public URL twice via HTTPS HEAD requests, and email a reviewer only when there are new incidents, recoveries, or a periodic portfolio digest. How it works Runs on a schedule (and can also be started manually for testing) and loads email and digest settings. Validates the sender/reviewer email addresses and the digest interval to ensure the report is configured. Calls the Lindo API to list all websites in the workspace and normalizes each entry into a valid public HTTPS URL. Checks each website’s reachability with an unauthenticated HTTPS HEAD request, waits 30 seconds, then runs a second confirmation HEAD check. Classifies each site as healthy, incident (two failures), or transient (only the confirmation fails) and compiles a full report with both samples. Compares current results to the last stored portfolio state in n8n static data to detect new incidents, recoveries, and whether a digest is due. Emails the incident update or digest via SMTP when needed, then commits the updated monitoring baseline for the next run. Setup Create HTTP Header Auth with header name Authorization and value Bearer YOUR_LINDO_API_KEY. Select it only in the Lindo inventory node; leave both public website probes unauthenticated. Add an SMTP email credential and set valid fromEmail and reviewerEmail values in the monitoring settings. Review and set digestDays (1–30), then activate the schedule interval you want (default is every 30 minutes). Requirements Lindo API access, SMTP and an n8n instance using built-in nodes. Keep executions sequential and verify two active scheduled executions; manual tests do not persist the monitoring baseline. Customization Adjust the schedule and digestDays (default seven days), or route reports to your incident-management service. Use a database or Data Table for concurrent workloads or portfolios above 1000 websites. Additional info Two failed samples open an incident; a healthy confirmation resolves a previous incident. A transient second-sample failure preserves prior state. Repeat incidents are suppressed, while the first active run and periodic digests include the portfolio. HEAD checks measure reachability, not page content or continuous uptime. Redirects are not followed; 403/405 may indicate HEAD restrictions. Removed inventory entries are not reported as recovered. Invalid domains or incomplete inventories stop execution; configure separate n8n execution-error notifications. State advances after successful delivery, so delivery failures may repeat notifications. An n8n automation workflow template by Saeed.

By Mohammad Abid

Quick overview This workflow provides backend webhooks for a Vapi hospital voice assistant to check appointment availability, book, reschedule, or cancel appointments in Google Sheets, and to request staff callbacks, sending notification emails via Gmail for each action. How it works Receives a POST request from Vapi to check availability, looks up existing entries in the Google Sheets “Appointments” tab, and returns whether the requested doctor/department/date/time slot is free. Receives a POST request from Vapi to book an appointment, validates required fields and caller confirmation, generates an appointment ID, appends the record to the Google Sheets “Appointments” tab, emails staff via Gmail, and returns a booking confirmation. Receives a POST request from Vapi to cancel or reschedule an appointment, validates caller confirmation, finds the matching active appointment in Google Sheets by appointment ID and phone number, and returns a not-found response if no match exists. If the request is a cancellation, updates the matching appointment’s status to “cancelled” in Google Sheets, emails staff via Gmail, and returns a cancellation confirmation to Vapi. If the request is a reschedule, updates the appointment date/time (and optionally doctor/department) in Google Sheets, emails staff via Gmail, and returns a reschedule confirmation to Vapi. Receives a POST request from Vapi to request a human callback, logs the request to the Google Sheets “Callbacks” tab, emails staff via Gmail, and returns a callback-requested message to Vapi. Setup Create a Google Sheet with “Appointments” and “Callbacks” tabs and the expected columns, then replace YOUR_GOOGLE_SHEET_ID in all Google Sheets nodes. Add Google Sheets OAuth2 credentials for the Google Sheets nodes and Gmail OAuth2 credentials for the Gmail nodes. Replace YOUR_STAFF_EMAIL@example.com in all Gmail nodes with the staff notification address. Activate the workflow and copy the four production webhook URLs, then configure them as POST tools in Vapi for availability, booking, manage (cancel/reschedule), and callback requests. Ensure your Vapi tool request bodies include the required fields and pass caller_confirmed=true for booking and appointment changes. An n8n automation workflow template by Mohammad Abid.

By Rahul Joshi

Quick overview This workflow runs monthly to extract GST purchase invoice details from Gmail PDF attachments using OpenAI, reconciles them against GSTR-2B data in Google Sheets, writes a reconciliation report, emails an ITC-at-risk summary to accounts, and creates vendor follow-up emails as Gmail drafts. How it works Runs at 10:00 AM on the 15th of each month and sets the company details, return period, tax tolerance, and Gmail search query. Searches Gmail for recent emails matching the query, downloads PDF attachments, and splits them so each invoice PDF is processed as a separate item with sender and thread context. Extracts text from each PDF and uses OpenAI to parse key invoice fields (GSTINs, invoice number/date, taxable value, and IGST/CGST/SGST), skipping non-tax invoices and duplicates. Reads the GSTR-2B tab from Google Sheets and reconciles each email invoice to GSTR-2B by supplier GSTIN and invoice number, falling back to a tax-amount match within the configured tolerance. Flags issues such as missing invoices in GSTR-2B, tax mismatches, invalid supplier GSTINs, or invoices billed to the wrong buyer GSTIN, and also notes GSTR-2B entries that have no matching invoice email. Appends or updates the results in a Google Sheets Reconciliation tab, then emails an HTML summary of counts and total ITC at risk to the accounts email address. Groups flagged items by vendor, uses OpenAI to draft a concise reminder per vendor, and saves each message as a Gmail draft (optionally in the original thread) for review before sending. Setup Connect Gmail OAuth2 credentials (to search emails, send the accounts summary, and create vendor drafts) and ensure the Gmail query in the rules matches how your invoices arrive. Connect Google Sheets OAuth2 credentials and replace YOUR_GOOGLE_SHEET_ID in both Google Sheets nodes, with a GSTR-2B tab containing the expected columns and a Reconciliation tab for output. Add an OpenAI API key credential for both extraction and reminder drafting, and confirm your data policy allows sending invoice text to OpenAI. Update companyName, companyGSTIN, accountsEmail, and (optionally) taxTolerance and return period logic in the rules so reconciliation and messages match your filing period and thresholds. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Quick overview This workflow runs every weekday morning to read invoices and payment history from Google Sheets, score each open invoice for late-payment risk, and use OpenAI plus Gmail to send friendly or firm reminders, or create a call task with a Slack alert, then log actions back to Google Sheets. How it works Runs at 9 AM on weekdays using a schedule trigger. Loads dunning thresholds and business settings, then reads open invoices and payment history from Google Sheets. Calculates a per-client payment profile and a 0–100 risk score for each unpaid invoice, selects a dunning tone (friendly, firm, or call), and enforces cooldown rules so reminders don’t repeat too frequently or soften. For friendly items, uses OpenAI (gpt-4o-mini) to draft a short pre-due or gentle overdue email and sends it via Gmail. For firm items, uses OpenAI (gpt-4o-mini) to draft a clear overdue notice and sends it via Gmail. For call items, appends a call task row to a Google Sheets “Call Tasks” tab and posts an escalation message to a Slack #collections channel. Updates the invoice row in Google Sheets with the latest reminder stage, reminder date, and risk score to track follow-ups. Setup Create a Google Sheets workbook with “Invoices”, “Payment History”, and “Call Tasks” tabs and include the columns referenced by the workflow (for example Invoice ID, Client Email, Due Date, Status, Last Reminder Stage/Date, and history Paid Date). Add Google Sheets credentials and replace YOUR_GOOGLE_SHEET_ID in all Google Sheets nodes with your spreadsheet ID. Add an OpenAI API key and a Gmail OAuth2 credential, and ensure the Gmail account is allowed to send reminders to your customers. Add a Slack OAuth2 credential and set the target channel (for example #collections) in the Slack message node. Update the dunning settings in “Set Dunning Rules” (company name, payment link, reply-to address, owner name, and thresholds like preDueNudgeDays and highRiskScore) to match your process. An n8n automation workflow template by Rahul Joshi.

By Thomas Abraham

Quick overview This workflow runs every 30 minutes (or manually) to find upcoming external Google Calendar meetings, pulls recent Gmail history with the primary external attendee, uses OpenAI to generate a concise meeting brief, emails it to you, and logs the event in Google Sheets to avoid duplicate briefs. How it works Runs every 30 minutes on a schedule or on demand via a manual trigger. Retrieves upcoming events from a specified Google Calendar and loads a “Briefed” log from Google Sheets. Filters meetings to those starting within the lead-time window and skips cancelled events, meetings you declined, internal-only meetings (based on domain), and events already logged as briefed. For each selected meeting, searches Gmail for recent messages to or from the primary external attendee and compiles snippets into a short history context. Uses an OpenAI chat model to write a four-section brief (WHO, WHERE WE LEFT OFF, OPEN THREADS, GO IN WITH) based on the invite details and email history. Emails the brief to your chosen address via Gmail and appends the meeting details to the Google Sheets log to prevent re-briefing. Setup Connect Google Calendar, Gmail, Google Sheets, and OpenAI credentials in n8n. Update the configuration values for CalendarId, SendBriefTo, InternalDomains, LeadTimeMinutes, and HistoryEmailCount. Create a Google Sheets spreadsheet with a “Briefed” tab containing the columns: Briefed At, Event ID, Meeting, Starts At, Attendees, History Found. Set the Google Sheets document ID (spreadsheet ID) in both Google Sheets steps to point to your log spreadsheet. An n8n automation workflow template by Thomas Abraham.

By Iago

Quick overview This workflow receives inbound WhatsApp messages via Wafly, uses OpenAI (GPT-4o-mini) with per-phone memory to classify each lead as hot/warm/cold, replies to the sender, and sends hot leads as a handoff message to a configured sales phone number. How it works Receives an inbound WhatsApp message through an n8n webhook configured for Wafly. Filters out non-customer traffic by ignoring echoes (fromMe), group chats, non-ReceivedCallback events, and empty messages. Sends the message text to OpenAI (GPT-4o-mini) with conversation memory keyed by the sender’s phone number to produce a JSON qualification (intent, budget/deadline flags, temperature, and a short reply). Parses the model output defensively and falls back to a safe “warm” classification and neutral reply if the JSON is malformed. Sends the generated reply back to the lead via Wafly WhatsApp messaging. If the lead is marked hot, sends a WhatsApp handoff message to the configured sales phone number with the lead details; otherwise it ends without escalation. Setup Self-host n8n and install the community node package n8n-nodes-wafly (this template does not run on n8n Cloud). Create and select Wafly API credentials and an OpenAI API credential for the OpenAI Chat Model node. Set the target salesPhone number (international format, digits only) in the Config step. Activate the workflow, copy the webhook Production URL, and register it in Wafly (or use the Wafly “Set Webhook” operation if available in your node version). Requirements Self-hosted n8n with the n8n-nodes-wafly community node, a Wafly instance with an inbound webhook, an OpenAI API key, and a WhatsApp number to receive sales handoffs. The workflow does not run on n8n Cloud. Customization Replace the placeholder salesPhone in Config. Edit the qualification prompt, temperature criteria, and reply text for your business. You can send hot-lead handoffs to a CRM instead of a phone. Test with your own number before activating the production webhook. Additional info Step-by-step setup (Portuguese): https://wafly.com.br/solucoes/qualificar-leads-whatsapp-ia-n8n/?utm_source=n8n&utm_medium=workflow_template&utm_campaign=lead_qualification&utm_content=creator_description . This community workflow uses Wafly’s QR-connected WhatsApp API, not Meta’s Official WhatsApp API. An n8n automation workflow template by Iago.

By SMS Vert Pro

Quick Overview This workflow manually sends an SMS via the SMS Vert Pro MCP server, waits 30 seconds, and then retrieves a delivery report for the SMS campaign using the returned campaign ID. How it works Runs when you start the workflow manually. Sends an SMS through the SMS Vert Pro MCP server using the send_sms tool with the configured recipient, message, and sender name. Waits 30 seconds to allow the SMS status to update. Requests the campaign delivery report from SMS Vert Pro using the get_delivery_report tool and the campaign ID from the send response. Setup Create an n8n Bearer Auth credential using your SMS Vert Pro API V2 token and select it in both SMS Vert Pro MCP client steps. Update the recipient phone number (international format without +), message text, and sender name (11 characters max) in the send request payload. Run the workflow manually, or replace the manual trigger with your preferred trigger and map the phone number/message fields accordingly. An n8n automation workflow template by SMS Vert Pro.