Browse 12,955 Workflows

By SPIRIDON TSAKONAS

Quick overview Monitors Stripe payments in real time: logs every payment, failure, refund and dispute to an n8n Data Table, ignores duplicate webhooks, flags unusual amounts against your own 30-day baseline, detects failed-payment spikes, and emails instant alerts plus a daily health digest. How it works Stripe Trigger receives checkout.session.completed, charge.failed, charge.refunded and charge.dispute.created events. Normalize Event turns each one into a row with a fixed shape, using Stripe's own event time. Load History reads the stored events and Analyze Event skips any event ID that already exists, so Stripe webhook retries are never counted twice. For completed payments, Analyze Event compares the amount with your 30-day average for the same currency using a z-score. With fewer than 10 past payments it falls back to a fixed threshold. It raises a critical finding when 3 or more payments fail within 60 minutes (possible card testing), a warning when refunds spike, and a critical finding for every new dispute. New events are saved to the Data Table. Events with a warning or critical finding trigger Send Alert, an email stating the severity, the reason and the baseline used. Every 24 hours, Calculate Metrics compares the last day with the day before and the 7-day average (revenue, payments, failure rate, refund rate, disputes), and Send Daily Digest emails a HEALTHY or ATTENTION report. Setup Create a Data Table named stripe_events with string columns event_id, event_type, currency, customer_email, status and created_at, and a number column amount. Select it in Load History, Store Event and Load Events. Add your Stripe API credential to Stripe Trigger. n8n registers the webhook in Stripe automatically when you activate the workflow, so your n8n instance must be reachable from the internet. Add an SMTP credential to Send Alert and Send Daily Digest, and replace the example From Email and To Email addresses with your own. Test without real payments: open Stripe Trigger, set mock data with a sample Stripe event and click Execute workflow. Use a new event ID for each test, because repeated IDs are skipped as duplicates. Then activate the workflow. Requirements An n8n instance with Data Tables, a Stripe account (test mode works) and an SMTP email account. Customization All thresholds (baseline window, z-score limit, failed-payment and refund spike limits, fixed fallback threshold) are constants at the top of the Analyze Event code. Change the digest interval in Daily Digest Trigger. Additional info Built only from native n8n nodes: no external database, no community nodes. Tested end to end on n8n 2.40.7 with mock Stripe events: a large payment (warning alert), three failed payments within one hour (critical alert), a repeated event ID (skipped as duplicate) and the daily digest (ATTENTION status at a 75% failure rate). An n8n automation workflow template by SPIRIDON TSAKONAS.

By Friedrich Bremer

Quick overview This workflow checks your Google Sheets portfolio for large daily price moves using Yahoo Finance data, enriches movers with SEC EDGAR filings and Google News results via SerpAPI, has OpenAI generate an explanation, then sends a Telegram alert and logs a summary back to Google Sheets. How it works Runs on a weekday schedule at 10:00, 14:00, and 18:00 (Europe/Berlin), and can also be invoked on demand via an Execute Workflow trigger. Loads alert settings (chat ID and move threshold) and reads your holdings from a Google Sheets “portfolio” tab, resolving each holding to a Yahoo Finance symbol. Fetches recent quotes from Yahoo Finance in batches and pulls EUR FX rates from Frankfurter, then computes each holding’s 1-day move versus the previous close and de-duplicates repeat alerts within the same day. For holdings that breach the configured percentage threshold, looks up recent SEC EDGAR submission data (when a US CIK can be resolved) and fetches recent related news with SerpAPI Google News search. Combines the price move, SEC filings, and news context, then asks OpenAI (GPT-5) to produce a Telegram-ready HTML explanation grounded in the evidence. Sends the formatted alert to your Telegram chat and appends a log entry (timestamp, movers, and preview) to a Google Sheets “finance_alert” tab. Setup Create a Telegram bot, add Telegram credentials in n8n, and set your Telegram chat ID in the ⚙️ Config node. Create a Google Sheet with a “portfolio” tab (at minimum: ticker, name, market, and an optional yahoo column for exact Yahoo symbols) and a “finance_alert” tab for logging, then connect Google Sheets OAuth and set the spreadsheet URL/ID in both Google Sheets nodes. Add a SerpAPI credential (used for Google News results) and an OpenAI API credential (used by the GPT-5 chat model). Adjust the move thresholds and schedule times as needed in the ⚙️ Config node and the Schedule Trigger. An n8n automation workflow template by Friedrich Bremer.

By scrapio.dev

Quick Overview This workflow tracks daily Google search positions for a list of keyword/domain pairs using Scrapio, logs the results to Google Sheets with position change metrics, and sends Slack alerts for sharp ranking drops plus a weekly Slack digest summarizing gains and losses. How it works Runs every day on a schedule and loads the configured keyword/domain pairs to track. Reads the full ranking history from Google Sheets and attaches it to each keyword/domain pair for comparison. Uses Scrapio to run a Google search for each keyword and locates the tracked domain’s current position in the results. Calculates the previous position, position change, and whether the domain dropped out or fell by 3+ places. Appends each day’s ranking snapshot to Google Sheets and posts a Slack alert when a significant drop is detected. Runs every week on a schedule, reads the ranking log from Google Sheets, filters to the last 7 days, and posts a Slack digest with totals plus biggest gain and biggest drop. Setup Add a Scrapio API credential and ensure the Scrapio Search operation is available in your n8n instance. Create or select a Google Sheet for the ranking log, add Google Sheets credentials, and set the document ID and sheet name for all Google Sheets steps. Ensure the sheet has columns that match the appended fields: checked_at, keyword, domain, position, url_found, previous_position, and position_change. Add Slack credentials and set the channel IDs for the rank-drop alert and weekly digest messages. Update the keyword/domain pairs in the workflow to the terms and domains you want to track, and adjust the 3+ position drop threshold if needed. An n8n automation workflow template by scrapio.dev.

By Rahul Joshi

Quick overview This workflow monitors a Gmail inbox for new messages, uses OpenAI to decide whether a reply is needed, drafts grounded replies with a Cognee knowledge base, saves them as Gmail drafts, and requests human approval in Slack while logging approvals to Google Sheets. How it works Triggers every minute when a new email arrives in the Gmail INBOX. Filters out automated senders (for example no-reply and mailer-daemon addresses) to skip unnecessary processing. Uses OpenAI (gpt-4o-mini) to classify the email as needing a human reply or not. For emails that need a reply, uses an OpenAI agent (gpt-4o-mini) with Cognee search to retrieve relevant company context and draft a response. Creates a Gmail draft reply in the same thread and posts a preview to Slack for approve/reject decision. Logs the approval status, timestamp, sender, subject, and draft text to Google Sheets. If any step fails, formats the error details and sends an alert to Slack. Setup Connect Gmail OAuth2 credentials and choose the mailbox/label to monitor, then ensure draft creation has access to the same Gmail account. Add an OpenAI API credential for the classifier and drafting agent, and ensure the gpt-4o-mini model is available to your account. Add a Cognee API credential and set the Cognee dataset used for search (for example cognee_3rd_workflow_dataset). Connect Slack credentials and set the target Slack channel ID for approval requests and the channel for error alerts. Connect Google Sheets OAuth2 credentials, then set the spreadsheet/document ID and sheet name and ensure the sheet has columns for Timestamp, From, Subject, Draft, and Approval Status. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Quick overview This workflow listens for Telegram voice notes from real-estate agents, transcribes and extracts buyer intent with OpenAI, updates the buyer in GoHighLevel, matches similar available listings from Google Sheets, emails top matches via Gmail, creates interest-based follow-up tasks, and confirms actions back in Telegram. How it works Triggers when an agent sends a message to your Telegram bot and prompts for a voice note if the message is not audio. Downloads the Telegram voice note and uses OpenAI audio transcription to convert it to text. Uses OpenAI (GPT-4o-mini) to extract structured visit details (buyer contact info, preferences, budget, and interest level) and builds a CRM note plus a timed follow-up plan. If a phone number or email is present, upserts the buyer contact in GoHighLevel and adds the formatted site-visit note to the contact record. Reads available listings from Google Sheets, scores them against the buyer’s criteria, and selects the top three matches while excluding the visited property. If an email address exists and matches were found, sends the similar listings to the buyer via Gmail. Creates GoHighLevel follow-up tasks for each scheduled step and sends the agent a Telegram confirmation summarizing the CRM update, emailed matches, and task due dates. Setup Create and connect credentials for Telegram (bot token), OpenAI (API key), GoHighLevel (LeadConnector OAuth/API access for the Contacts and Tasks endpoints), Google Sheets (OAuth2), and Gmail (OAuth2). In Google Sheets, create a listings table with columns like listing_id, title, area, price, bedrooms, property_type, url, and status, then set the spreadsheet ID and sheet name in the Google Sheets node. In the workflow code settings, set your GoHighLevel location ID (and optionally an assigned user ID) and adjust the follow-up timing/titles to match your process. Enable the Telegram trigger and share the bot with your agents, instructing them to include the buyer’s name plus a phone number or email in each post-visit voice note. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Quick overview This workflow ingests supplier invoice images from Google Drive, uses OpenAI GPT-4o to extract normalized ingredient unit prices into Google Sheets, then runs a weekly margin check by combining ingredient price history, recipe costing, and POS sales to email menu price recommendations via Gmail. How it works Triggers when a new invoice file is created in a specified Google Drive folder. Downloads the invoice image and sends it to OpenAI GPT-4o Vision to extract supplier details, invoice metadata, and per-ingredient unit prices (kg/l/each). Parses the extracted JSON into one row per invoice line and appends the ingredient price records to an Ingredient Prices tab in Google Sheets. Every Monday at 8 AM, reads POS Sales, Recipe Costing, and Ingredient Prices from Google Sheets and calculates current vs 30-day-baseline plate costs and gross margin changes per dish. Flags dishes whose margin drops by at least 2 points, identifies the ingredient driving the increase, estimates the last-7-days profit leak, and generates a capped (+10%) rounded price suggestion. Logs each flagged dish to a Margin Alerts tab in Google Sheets and uses OpenAI (gpt-4o-mini) to draft a short owner-friendly summary. Sends the weekly pricing report email to the owner via Gmail. Setup Create credentials for Google Drive, Google Sheets, and Gmail (OAuth2) and an OpenAI API key credential. Create a Google Sheets spreadsheet with tabs and headers for Ingredient Prices, Recipe Costing, POS Sales, and Margin Alerts, and update each Google Sheets node to point to the correct document and sheet names. Set the Google Drive folder to watch in the trigger and ensure invoices are uploaded as images/scans that GPT-4o can read. Adjust the margin/lookback and pricing settings (lookback days, margin-drop threshold, max increase cap, rounding step) in the margin calculation code, and replace the owner email address in the Gmail send step. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Quick overview This workflow monitors new Google Business Profile reviews, uses OpenAI to draft replies and tag a single root-cause category, routes complaint replies to Slack for approval, logs every review to Google Sheets, and emails a weekly Gmail report summarizing the fixable issue that cost the most stars. How it works Polls Google Business Profile hourly for new reviews and ignores any reviews that already have an owner reply. Normalizes each review into consistent fields (ID, author name, date, star rating number, and review text). Uses OpenAI to generate a short draft reply plus sentiment, a single root-cause tag, optional staff name, and a brief complaint summary. Logs the enriched review (including fixable flag and reply status) to a Google Sheets review log. Automatically posts the reply back to Google Business Profile for 4–5 star reviews tagged as having no complaint, and sends all other drafted replies to Slack for approve/decline. Posts the approved reply to Google Business Profile when the owner approves it in Slack. Every Monday at 9 AM, reads the last 7 days of the Google Sheets log, calculates stars lost (5 minus rating) by fixable root-cause tag, uses OpenAI to write a short HTML insight, and emails it to the owner via Gmail. Setup Connect credentials for Google Business Profile (OAuth2), OpenAI (API key), Google Sheets (OAuth2), Slack (OAuth2), and Gmail (OAuth2). Select your Google Business Profile account and location in both the review trigger and the node that posts replies. Create a Google Sheet with the required headers (review_id, review_name, review_date, reviewer, star_rating, review_text, sentiment, root_cause, staff_mentioned, fixable, complaint_summary, draft_reply, reply_status) and select its document and sheet in both Google Sheets nodes. Update the OpenAI system prompt placeholders (for your business name and contact email), choose the Slack channel for approvals, and set the owner’s email address in the Gmail node. An n8n automation workflow template by Rahul Joshi.

By ryo

Quick Overview This workflow monitors Gmail for unread emails with the subject “Inquiry Received”, uses Google Gemini to classify and summarize each inquiry, calculates an SLA deadline, creates a Google Calendar follow-up event, logs the ticket in Google Sheets, drafts a Gmail reply, and posts a Discord alert for high-priority cases. How it works Triggers every minute when an unread Gmail message matching subject “Inquiry Received” is received. Sends the email sender, subject, and body to Google Gemini via an LLM chain to return structured JSON with category, priority, summary, and a reply draft. Calculates an SLA deadline based on priority (High: +4 hours, Medium: next day 18:00, Low: +3 days 18:00) and builds a task title and metadata. Creates a Google Calendar event from now until the calculated deadline with the ticket details in the description. Appends a row to Google Sheets with the received time, triage results, deadline, and the Google Calendar event link. Creates a Gmail draft reply in the original email thread using the AI-generated reply text. If the priority is High, sends an urgent notification to Discord with the deadline and inquiry summary. Setup Connect credentials for Gmail, Google Gemini (Google AI), Google Calendar, and Google Sheets in n8n. Update the Google Sheets document ID and sheet name in the Google Sheets append step, and ensure the sheet has columns: received_at, priority, category, sender, subject, summary, deadline, calendar_event_url. Configure a Discord webhook and select it in the Discord node used to send urgent alerts. Confirm the Gmail trigger filter (subject “Inquiry Received” and unread) matches your inbound support email pattern and adjust it if needed. An n8n automation workflow template by ryo.

By Intuz

Quick overview This workflow runs every weekday at 9 AM to collect the last 24 hours of Jira issue updates and GitHub pull request activity, uses OpenAI to summarize the results, posts a Block Kit digest to Slack, and optionally logs the digest outcome to Google Sheets. How it works Runs on a weekday 9:00 AM schedule trigger. Pulls Jira issues updated in the last 24 hours and finds “In Progress” Jira issues that have not been updated for the configured stale-day threshold. Splits the configured GitHub repository list and, for each repo, fetches recent pull requests and searches for open pull requests with no reviews. Normalizes and merges the Jira and GitHub results into a single digest payload. Sends the digest payload to OpenAI Chat Completions to generate a strict-JSON summary (what moved, what shipped, what’s blocked, needs review, and sprint health). Builds a Slack Block Kit message with ticket/PR links and optional @mentions based on a Jira/GitHub-to-Slack user map, then posts it to the configured Slack channel. If Google Sheets logging is enabled, appends a row with the posting result details to the configured spreadsheet tab. Setup Add credentials for Jira Software Cloud, GitHub, OpenAI, and Slack (and Google Sheets if you enable logging). Update the Config values for your Jira base URL and project key, GitHub repositories list, stale thresholds, Slack channel, and the OpenAI model. Invite the Slack app/bot to the target channel and ensure it has permission to post messages. If sheet logging is enabled, set the Google Sheets document and tab to use and ensure the sheet has columns that match the appended fields (ok, channel, message, message_timestamp). (Optional) Populate the user map in Config with Jira account IDs and GitHub logins mapped to Slack user IDs to enable @mentions in the digest. Requirements n8n credentials: Jira Cloud, GitHub, OpenAI, Slack; Google Sheets only if logging is on Access to the Jira project (e.g. PTN) and listed GitHub repos A Slack channel the bot can post in Fine-grained GitHub token needs repo + pull-request read (Search for review:none) Additional info Connect with us: Website: https://www.intuz.com/n8n-workflow-automation-templates/ Email: getstarted@intuz.com LinkedIn: https://www.linkedin.com/company/intuz For Custom Workflow Automation Get Started: https://n8n.partnerlinks.io/intuz. An n8n automation workflow template by Intuz.

By muhd dahlan

Quick overview Automates Shopee price monitoring for competitive analysis. You can set up alerts by submitting a Shopee product or search URL and your WhatsApp number. On your configured schedule, n8n scrapes the Shopee results, finds the 3 lowest-priced products, and sends a price report directly to WhatsApp using Kapso. How it works Submit a Shopee URL and WhatsApp number through the alert form. n8n stores the alert in an n8n Data Table and prevents duplicate alerts. The workflow runs automatically based on the configured schedule. n8n retrieves all saved Shopee alerts and processes them one by one. Each Shopee URL is scraped using Apify to collect product data. Products are sorted by price and the 3 lowest-priced products are selected. A price report containing the product name, Shopee URL, and price is sent to WhatsApp using Kapso. The process repeats automatically for all configured alerts. Setup Set up the n8n Data Table for storing Shopee alerts. Connect your Apify account for Shopee data scraping. Configure your Kapso API credentials. Configure the workflow schedule. Activate the workflow. Submit Shopee URLs and WhatsApp numbers through the provided alert form. The workflow will automatically send competitive price reports based on your schedule. Requirements n8n n8n Data Tables Apify account Kapso account WhatsApp number A Shopee URL to monitor. An n8n automation workflow template by muhd dahlan.

By Luca

Quick Overview This workflow audits inventory and open purchase orders in Google Sheets, calculates reorder quantities based on measured demand and lead times, and emails purchase orders via Gmail with optional buyer approval; it also uses OpenAI to extract supplier confirmations from Gmail replies and updates the order pipeline. How it works Runs every weekday morning on a schedule to start a replenishment run. Reads Products, Stockouts, Sales, Purchase orders, Suppliers, and Reorder log tabs from Google Sheets and audits them to flag late deliveries, short receipts, and stock records that don’t reconcile. Emails suppliers via Gmail to chase overdue/short deliveries and emails operations to investigate any stock discrepancies, while logging these actions back to the Reorder log in Google Sheets. Calculates demand (excluding stockout days and sales spikes), measures supplier lead times from receipt history (or uses quoted lead time when history is thin), and builds one proposed purchase order per supplier. Routes each proposed order to either send immediately, hold until a later run, or request buyer approval by email, and then logs the decision to the Reorder log. When an order is sent, emails the supplier the purchase order and writes each order line into the Purchase orders tab in Google Sheets for tracking. Polls Gmail for supplier replies, uses OpenAI to extract confirmed quantities/dates/prices from the new reply text only, reconciles the confirmation against the open order lines in Google Sheets, and either updates the order as confirmed or escalates at-risk changes to the buyer. Setup Add credentials for Google Sheets, Gmail, and OpenAI (for the confirmation extraction step). Create a Google Sheets file with tabs named Products, Sales, Stockouts, Purchase orders, Suppliers, and Reorder log, and ensure the columns used in the workflow (for example sku, supplier_name, on_hand, expected_on, ordered_on, received_on, unit_cost, and line_key) exist. Update the sheet ID and the buyer/operations email addresses in both configuration steps (the replenishment policy and the confirmation rules). Review and adjust replenishment thresholds (for example service level, cover targets, approval limit, late/price tolerances, and date format order) to match your inventory policy and locale. Ensure supplier contact emails and ordering constraints (for example pack size, MOQ, minimum order value, order days, and quoted lead time) are populated in the Suppliers/Products tabs so orders can be generated and sent. An n8n automation workflow template by Luca.

By FalconScrape

Quick overview This workflow runs a charge-capped Apify scraper for Pracuj.pl job listings based on a keyword and location, then writes and updates job observations, company-level counts, and a run ledger in Google Sheets with a locking mechanism to prevent overlapping imports. How it works Runs manually and reads the configured Pracuj.pl search parameters (keyword, location, max items, charge cap, and target Google Sheets spreadsheet ID). Validates the configuration, checks the destination Google Sheets file, creates the required tabs if missing, and applies a temporary lock sheet to prevent concurrent writes. Reads and validates existing rows in the Pracuj Jobs, Pracuj Companies, and Pracuj Runs tabs to ensure headers, limits, and search scope are consistent. Starts a new Apify Actor run for FalconScrape’s Pracuj.pl Job Offers Scraper (or loads an existing run when a resume run ID is provided) and records a PROCESSING checkpoint in the Pracuj Runs tab. Polls Apify until the run succeeds, then downloads the full dataset of scraped listings. Normalizes and deduplicates the job data and batch-updates Google Sheets by inserting new jobs or refreshing existing ones, appending per-company observation rows, and logging the run status. Removes the temporary lock sheet and outputs a run summary including counts and a link to the spreadsheet. Setup Add Apify API credentials in n8n and ensure the workflow can access the FalconScrape Pracuj.pl Job Offers Scraper Actor. Add a Google Sheets OAuth2 credential and create an empty Google Sheets spreadsheet you can edit. Paste the spreadsheet ID (not the full URL) into the workflow configuration, then set the keyword, location, maxItems, and maxChargeUsd values for your search. Use one keyword/location per spreadsheet to keep baseline and “newly observed” semantics consistent across runs. If recovering an interrupted execution, remove the _PRACUJ_WORKFLOW_LOCK sheet only after confirming no execution is active and set resumeRunId to the saved Apify run ID from the Pracuj Runs tab. Additional info The first successful import is a BASELINE. Later NEW jobs are newly observed in this spreadsheet, not necessarily newly published; missing listings are not assumed closed. Company counts describe jobs per displayed employer in this bounded search, not headcount growth or hiring urgency. Start manually with 20 jobs and a $0.06 Actor charge cap. The template is free, but Apify runs and n8n hosting may incur charges. An n8n automation workflow template by FalconScrape.