Browse 12,955 Workflows

By Jitterflow

Quick Overview This workflow lets a Slack slash command trigger an n8n webhook that lists unresolved Jitterflow dead-letter queue (DLQ) entries, responds to Slack immediately with the count, and then replays each failed delivery via the Jitterflow API. How it works Receives a POST request from a Slack slash command via an n8n webhook. Calls the Jitterflow API to list unresolved DLQ entries (up to 100 items). Responds to Slack within the 3-second timeout with a message indicating how many failed deliveries will be replayed (or that none exist). Filters out any DLQ items that do not contain a job ID. Replays each remaining DLQ job through the Jitterflow API, continuing even if replay errors occur. Setup Install the verified community node n8n-nodes-jitterflow (on self-hosted n8n, install it from Settings → Community Nodes). Create a Jitterflow API credential in n8n and select it in both Jitterflow steps (list DLQ and replay). Activate the workflow, copy the production webhook URL, and configure your Slack app’s slash command to send POST requests to it. An n8n automation workflow template by Jitterflow.

By Abdullah al MaHI

Quick overview This workflow receives invoice PDFs or images via a webhook, extracts text using OCR.space, parses key invoice fields and line items with deterministic rules, and then saves the results as a CSV file and optionally appends them to Google Sheets before returning the extracted data as JSON. How it works Receives an HTTP POST webhook request containing an uploaded invoice file (PDF/image) in a binary field. Sends the uploaded file to the OCR.space API to convert the document into extracted text. Checks whether OCR.space processed the file successfully and returns a 422 JSON error response if OCR fails. Parses the OCR text to extract vendor, invoice number, invoice date, subtotal, tax, total, and line items, and generates flags for any missing fields or line-item calculation mismatches. Converts the extracted fields into a CSV file and writes it to disk. Optionally appends the extracted record to a Google Sheets worksheet. Returns the extracted invoice data (including flags and raw OCR text) as the webhook response. Setup Create an OCR.space API key and add it to an n8n Header Auth credential (header name "apikey") used by the OCR request. Send invoices to the webhook endpoint by copying the production webhook URL from the "Invoice Upload" trigger and posting a file in the binary field named "invoice". Ensure n8n has write access to the configured output path (default: ./output/) or update the CSV file path to match your environment. (Optional) Add a Google Sheets OAuth credential, set the target Spreadsheet ID and sheet name, and ensure the header row matches the workflow’s output fields before enabling the Google Sheets append step. An n8n automation workflow template by Abdullah al MaHI.

By Dmitrii Suchilin

Quick overview This workflow turns an article URL sent via Telegram into a rendered vertical video with AI-generated voiceover and karaoke-style subtitles, uploads it to Google Drive, and optionally publishes it to TikTok via the pm3k API. How it works Triggers when a specified Telegram user sends a message containing an article URL and replies to confirm processing has started. Downloads the article content as Markdown (with image summaries) using the Jina AI reader endpoint. Uses OpenAI to extract the main article, generate a TikTok video plan (title, caption, script, scenes, motions, and article image URLs), and then generates a voiceover audio file. Sends the voiceover to OpenAI Whisper to get word-level timestamps and prepares scene timing plus subtitle chunks aligned to the script. Runs a local Node.js/FFmpeg render that downloads the scene images, applies pan/zoom motion, burns in karaoke subtitles, and outputs a final MP4. Uploads the rendered video to Google Drive, shares it publicly, and prompts the user in Telegram to publish, re-render, or cancel. If publishing is approved, fetches TikTok accounts from pm3k, lets the user pick an account in Telegram, creates a TikTok post batch via pm3k, and polls until it succeeds or fails before notifying the user. Setup Connect a Telegram Bot API credential, set the allowed Telegram user ID, and start the workflow so you can send article URLs to the trigger. Add an OpenAI API credential with access to chat models, TTS (tts-1-hd), and Whisper (whisper-1) for planning, voiceover generation, and transcription. Ensure the n8n host can run node and ffmpeg and can write to /home/node/.n8n-files/work (or update the paths in the command and file nodes). Connect a Google Drive OAuth2 credential and set the target Drive/folder ID where rendered videos should be uploaded. Add an HTTP Bearer Auth credential for the pm3k API (pm3k.org) so the workflow can list TikTok accounts and publish videos. An n8n automation workflow template by Dmitrii Suchilin.

By Vlotstroom

Quick overview This workflow runs every 6 hours to read upcoming appointments (demo data or Google Sheets), generate WhatsApp- or email-ready reminder messages based on how soon the appointment starts, and route same-day reminders to a priority dispatch lane. How it works Runs every 6 hours on a schedule. Loads appointment rows from the built-in demo data (or from Google Sheets when enabled). Filters to appointments starting within the next 48 hours and generates a reminder message, choosing a shorter template for appointments within 3 hours. Uses each record’s channel preference to target WhatsApp (phone number) or email (email address). Splits same-day reminders from upcoming reminders to handle urgent messages separately. Labels each reminder with a dispatch queue and timestamp so you can connect WhatsApp and email sending steps. Setup If using Google Sheets, enable the Google Sheets node, add Google Sheets credentials, set your spreadsheet ID and sheet name, and ensure columns exist for appointment_id, customer_name, phone, email, starts_at (ISO), practitioner, treatment, and channel_preference. Add your sending integrations after both dispatch branches (for example, WhatsApp Business Cloud for WhatsApp and Gmail/SMTP for email) and configure the recipient field to use the workflow’s prepared “to” value. Adjust the reminder windows and message text in the message-building step (48-hour inclusion window and 3-hour same-day threshold) to match your reminder policy. Requirements n8n (any plan). For production: a Google Sheets credential and a WhatsApp Business Cloud or email sending credential. Customization Reminder window (48h) and same-day threshold (3h) are plain constants in the message-builder node; message texts are editable strings. An n8n automation workflow template by Vlotstroom.

By Marek Stokowski

Quick overview This weekly workflow pulls page-and-query performance from Google Search Console, identifies URLs with high impressions but near-zero clicks, classifies the likely cause based on average position and CTR, and emails a prioritized report via Gmail (with an optional OpenAI summary). How it works Runs every Monday morning on a schedule. Requests the last N days of Google Search Console Search Analytics data by page and query. Merges URL variants (removing query strings/fragments), filters out operator-style queries, and keeps pages that exceed the impression threshold while staying under the max-click threshold. Calculates average position and CTR, labels each page as TITLE_META, INTENT_MISMATCH, POSITION_TOO_LOW, or SERP_FEATURE, and estimates potential clicks. Keeps the top 25 opportunities by impressions and stops if there is nothing to report. Aggregates the results into a single report, optionally generates per-page recommendations with OpenAI, and sends the report by Gmail. Setup Connect a Google Search Console OAuth2 credential with access to your property. In the Config values, set your siteUrl (for example sc-domain:example.com), plus days, minImpressions, and maxClicks thresholds. Set the recipient email address in the Gmail node and connect your Gmail credential. (Optional) Enable the OpenAI step, add an OpenAI credential, and choose the model you want to use for the plain-language recommendations. An n8n automation workflow template by Marek Stokowski.

By Khairul Muhtadin

Dental lab cases that keep clinics in the loop without anyone chasing updates. This workflow takes new case submissions from an n8n Form, has gpt-6-luna check that the case is complete and draft the clinic acknowledgment, tracks every stage in Google Sheets, and sends the right email or alert the moment a case moves. Last updated: September 2026. Quick Overview This workflow captures dental lab case submissions via an n8n form, uses gpt-6-luna to assess completeness and draft an acknowledgment email, logs and tracks cases in Google Sheets, and sends status and daily production updates via Gmail, Discord, and Telegram. How it works Receives a new case submission through an n8n Form and normalizes the clinic and case details while generating a unique case ID and timestamps. Validates required fields (clinic email, product type, due date) and, if missing, logs the error to Google Sheets, posts a Discord alert, and emails an invalid-submission notice. Builds a case summary prompt and uses gpt-6-luna to assess completeness, identify missing items, set priority guidance, and draft a clinic acknowledgment email. Assigns the case to a technician category, calculates urgency from the due date and rush flag, and appends the case (including AI outputs) to the Google Sheets “Cases” tab. Emails the clinic the acknowledgment, posts the new case to Discord, and if the case is rush/urgent or incomplete, emails the lab manager and sends a Telegram alert. Accepts status updates via a webhook, validates the case ID and stage, updates the matching row in Google Sheets, and appends an entry to the “Status Log” tab. Notifies clinics by email when a case becomes ready or delivered, and sends a Telegram alert (plus a clinic email) when a case is flagged for remake. Runs daily at 08:00, analyzes the Google Sheets case board for overdue/due-soon/stuck items, uses gpt-6-luna to write a morning brief, posts it to Discord, emails it to the lab manager, and sends a Telegram alert if any cases are overdue. Setup Create a Google Sheets file with three tabs named “Cases”, “Status Log”, and “Errors”, and ensure the columns match those appended/updated by the workflow. Add credentials for Google Sheets OAuth2, OpenAI, Gmail OAuth2, Discord Bot, and Telegram, and select the correct accounts in the respective nodes. Update recipient details such as the lab manager email address, Discord server/channel, and Telegram chat ID used for alerts. Publish the intake form and share its URL with clinics, and copy the status webhook endpoint (/dental-case-status) into whatever system will post lab stage updates. Confirm the daily schedule time (08:00) matches your desired timezone and adjust the cron expression if needed. Quick Answers How does a new case get into the lab? The clinic submits it on the form, the workflow normalizes the clinic and case details and generates a unique case ID, then checks that clinic email, product type, and due date are present. Anything missing is logged to Google Sheets, posted to Discord, and answered with an invalid-submission notice. What does gpt-6-luna actually do? It assesses the case for completeness, lists missing items, sets priority guidance, and drafts the clinic acknowledgment email. A second AI step writes the morning production brief. How do clinics hear about progress? Stage updates sent to the status webhook are validated and used to update the matching row in the Cases tab and append to the Status Log. Ready and delivered cases trigger clinic emails, and a remake flags the lab manager on Telegram and notifies the clinic by email. What happens in the daily 08:00 run? The whole case board is analyzed for overdue, due-soon, and stuck items, gpt-6-luna writes the morning brief, and it is posted to Discord and emailed to the lab manager, with a Telegram alert when any case is overdue. Additional info Built with n8n. Need an assessment on your business? Feel free to reach out at https://khmuhtadin.com/consultation/. An n8n automation workflow template by Khairul Muhtadin.

By WeblineIndia

Quick Overview This workflow answers RFx sourcing questions from a chat widget by combining Google Sheets event/FAQ data with Google Gemini, then scores each response for confidence and logs usage or escalations back to Google Sheets. How it works Receives a message from an n8n chat trigger and captures the question, timestamp, and session ID. Classifies the requester (supplier vs internal), detects the RFx stage and question category, and extracts any referenced RFx event ID from the text. Pulls RFx event details from Google Sheets and builds a context summary, prioritizing active events and the referenced event when provided. Pulls FAQ rules from Google Sheets, selects the most relevant entries, and builds a role-specific prompt that includes event data, FAQ guidance, and response instructions. Sends the prompt to Google Gemini to generate a concise, audience-adapted answer. Scores the answer for uncertainty and sensitive topics, then appends the interaction to a Google Sheets usage log or creates a pending escalation record in a Google Sheets escalation log. Setup Add Google Sheets OAuth2 credentials in n8n and ensure the workflow’s Google Sheets nodes point to your spreadsheet document ID. Create and populate a Google Sheets workbook with the required tabs: RFx_Events, FAQ_Rules, FAQ_Usage_Log, and Escalation_Log, using columns that match the fields the workflow appends. Add a Google Gemini (Google PaLM / Gemini) API credential in n8n and assign it to the Gemini Chat Model node. Enable and configure the n8n Chat trigger (webhook) and connect its chat/web widget to the generated endpoint so messages reach the workflow. An n8n automation workflow template by WeblineIndia.

By James Mundy

Quick overview This workflow checks a web page on a schedule, uses Gaffa to extract the listed articles in a browser, filters out URLs it has already seen, and emails you an HTML digest of newly found articles via SMTP. How it works Runs every hour on a scheduled trigger. Sets the target page URL and the CSS selector that contains the article list. Uses Gaffa to load the page in a real browser and extract article title, URL, and date/age from the selected element. Splits the extracted article list into individual items. Filters out articles whose URLs were already processed using workflow static data. Builds a single HTML digest and sends it by email via SMTP. Setup Install the Gaffa community node (@gaffa-dev/n8n-nodes-gaffa) and add a Gaffa API key credential from gaffa.dev. Add an SMTP email credential and set the From and To email addresses in the email step. Update the page URL and CSS selector values to match the page you want to monitor. Adjust the schedule interval to how often you want the page checked, then activate the workflow. An n8n automation workflow template by James Mundy.

By Lorenz Wieseke

Quick overview This workflow checks a list of HTTP endpoints every 5 minutes, retries once on failure, and posts Slack alerts only when an endpoint goes down or recovers, with optional escalation and Google Sheets logging plus a daily Slack digest of any endpoints still down. How it works Runs every 5 minutes (or manually) and loads a predefined list of endpoints with a name, URL, and optional expected health field. Requests each endpoint over HTTP with a 15-second timeout and captures the full response without failing the workflow on errors. Evaluates health based on the HTTP status code and, when configured, verifies a specific field in the response body matches the expected healthy value. If an endpoint looks unhealthy, waits 30 seconds and retries once to confirm the outage before continuing. Stores the last-known state per endpoint and only proceeds when the state changes to down or recovered, tracking how long it has been down and how many consecutive failures occurred. Sends a Slack alert when an endpoint goes down (and optionally appends the event to Google Sheets) and sends another Slack alert when it recovers. Escalates to Slack after 6 consecutive failed checks for an endpoint, and every day at 08:00 sends a Slack digest only if any endpoints are currently down. Setup Update the endpoint list (name, URL, and optional expected field) in the endpoints configuration step. Add Slack credentials and configure the target channel(s) for the down, recovered, escalation, and daily digest Slack messages. (Optional) Add Google Sheets credentials and configure the spreadsheet and sheet for outage logging. Adjust the check interval, retry delay, escalation threshold (6 failures), and the daily digest time (08:00) to match your monitoring needs. An n8n automation workflow template by Lorenz Wieseke.

By Incrementors

Quick overview This workflow collects prospect details via an n8n form, uses OpenAI (ChatGPT) to generate a personalized cold email and subject line, sends the email through Gmail, and logs the outreach to Google Sheets for tracking. How it works Receives prospect and company details from an n8n Form trigger submission. Validates required fields, checks the email format, and compiles the provided details into a structured context block. Sends the context to an OpenAI ChatGPT model to generate a JSON response containing a short subject line and an HTML cold email. Parses and validates the AI output, falling back to a default subject and email draft if the JSON cannot be parsed. Sends the generated email to the prospect using Gmail. Appends the lead details, subject line, sent flag, and date to a Google Sheets “Leads” worksheet. Setup Add an OpenAI API credential and select a model in the OpenAI Chat Model step used by the AI agent. Update the AI agent system prompt to replace placeholders like AGENCY_NAME and adjust the service description to match your offering. Connect a Gmail OAuth2 account that is allowed to send outbound emails. Connect a Google Sheets OAuth2 account, set the spreadsheet ID, and ensure a “Leads” sheet exists with matching columns (Company Name, Contact Name, Contact Email, Website, Industry, Subject, Email Sent, Date). Activate the workflow and use the generated form URL (path: cold-email-generator) wherever you collect prospect inputs. An n8n automation workflow template by Incrementors.

By Apify

Quick overview This workflow takes a city and search query, scrapes matching Google Maps places using Apify’s Google Maps Scraper, and writes the results (name, rating, reviews, category, address, website, and link) into a newly created Google Sheets spreadsheet. How it works Starts when you manually execute the workflow. Sets the search parameters (city, query, and maximum number of places to collect). Creates a new Google Sheets spreadsheet with a “Places” tab named after the search. Runs the Apify Google Maps Scraper actor to collect places matching the query in the specified city. Appends one row per place to Google Sheets with key details including rating, reviews, address, website, category, and Google Maps URL. Setup Open Scrape Google Maps with Apify and connect your Apify account with OAuth2. A free Apify account is enough to run the Google Maps Scraper Actor (compass/crawler-google-places). Open Create the spreadsheet and sign in with Google. Add places to the sheet reuses the same Google Sheets credential. In Search settings, set city, query, and maxPlaces. Click Execute workflow, then open spreadsheetUrl in the output of Create the spreadsheet to see your results. Requirements An Apify account (the free plan works). A Google account with access to Google Sheets. Customization Raise maxPlaces for longer lists. Add a Schedule Trigger to refresh the sheet every week. Swap in any other Actor from Apify Store. An n8n automation workflow template by Apify.

By Vinh Le

FAQ chatbot that grows its own answers — with owner approval Who it's for: site owners and support leads who want a public chat that answers from a known FAQ, never hallucinates, and gets smarter every week. How it works Visitors chat via the hosted webchat (Chat Trigger). The bot loads the FAQ sheet from Google Sheets and OpenAI answers only from it. Every turn is routed three ways: answered (reply sent), unanswered (logged to the Unanswered tab and the owner notified by Gmail), or lead (visitor left an email — captured in Leads and the owner notified). Repeats never duplicate rows. Every Monday a second lane clusters the unanswered log, ranks gaps by frequency, has OpenAI draft candidate FAQ entries, emails the owner a digest, and appends proposals to FAQ-Pending. The owner copies approved rows into FAQ — the bot only learns what a human signs off. Setup Click Test workflow — the demo lane runs six visitor turns (answerable, unanswered, lead, empty, repeat, bad AI answer) through every route with zero credentials. Attach credentials: Google Sheets, Gmail, OpenAI. Press play on the SETUP node (Lane D) — it creates the spreadsheet with all four tabs, headers and example rows, then prints the spreadsheet_id. Open the Workflow Config node and paste the id plus your owner_email. Then delete the setup lane, activate the workflow and embed the Chat Trigger's public URL in your site. Note: the Google Sheets and Gmail nodes are enabled — once credentials are attached they write real rows and send real emails. An n8n automation workflow template by Vinh Le.