Marketplace
3.557 fertige Workflow-Dateien zum Download, plus 10.661 quellenverknüpfte n8n-Referenzen.
Solve image CAPTCHAs via webhook using CaptchaSonic
Quick overview This workflow exposes a POST webhook that accepts base64 CAPTCHA images and uses the CaptchaSonic community node to solve multiple CAPTCHA types (OCR, reCAPTCHA v2, AWS WAF, TikTok, Binance, and more), returning a standardized JSON response. How it works Receives a POST request on the captchasonic-solve webhook containing a JSON body with a type and required fields like image (base64) and sometimes question. Validates the request payload, checks required fields for the requested CAPTCHA type, and routes the request to the matching solver. Sends the image challenge to CaptchaSonic using the appropriate recognition operation for the selected type. Normalizes the CaptchaSonic result into a consistent JSON structure with success, type, solution, and a solvedAt timestamp. Returns the formatted solution to the original webhook caller, or responds with HTTP 400 and an error message if validation fails. Setup Self-host n8n and install the n8n-nodes-captchasonic community node. Create and select a CaptchaSonic API credential (API key from https://my.captchasonic.com) for the CaptchaSonic nodes. Activate the workflow, copy the production webhook URL for captchasonic-solve, and
Send daily product newsletters via Gmail and track events in Google Sheets
Quick overview This workflow sends a daily product newsletter from Google Sheets via Gmail and tracks opens, clicks, and unsubscribes through an n8n webhook, logging all events back to Google Sheets. How it works Runs every day at 08:00 (configured in the Schedule Trigger). Reads products from Google Sheets and keeps only rows whose send_date matches today. If there are products to send, builds an HTML newsletter with a per-campaign newsletter ID, tracked click URLs, a tracking pixel, and an unsubscribe link, and logs the newsletter contents to Google Sheets. Reads recipients and the unsubscribe list from Google Sheets, removes unsubscribed addresses, and personalizes the newsletter HTML for each recipient by inserting their email and the campaign ID into tracking links. Sends each personalized email via Gmail and appends a “sent” event to the Google Sheets tracking log. Receives open, click, and unsubscribe requests on a webhook endpoint, routes by event type, and logs the event to Google Sheets. For clicks and unsubscribes, filters likely bot/duplicate requests (user-agent checks and recent-event deduping), then redirects to the product URL or returns an unsubscribe confirmation
Detect duplicate Google Drive files and log results to Google Sheets
Quick overview This workflow manually scans a specified Google Drive folder for duplicate and near-duplicate filenames, appends the results to a Google Sheets log, and optionally sends a single Gmail notification when duplicates are found. How it works Runs when you click “Execute workflow” in n8n. Reads the target Google Drive folder ID from the configuration values and retrieves all files in that folder with key metadata (name, size, timestamps, link, and MIME type). Analyzes the file list to detect exact duplicates (same filename) and near-duplicates (common copy/version naming patterns) and assigns a recommended action such as KEEP, DELETE, or REVIEW. If duplicates are found, appends one row per flagged file to a Google Sheets tab and sends a single Gmail notification that the scan needs review. If no duplicates are found, appends a single “NONE FOUND” scan record to Google Sheets to maintain an audit trail. Setup Connect your Google Drive OAuth2 credentials so the workflow can list files in the target folder. Connect your Google Sheets OAuth2 credentials and set the spreadsheet ID in the configuration values, and ensure the target tab (for example, “Sheet1”) has matching colum
Track Slack EOD updates and post executive summaries with Google Sheets and Gemini
Quick overview Youtube Video: https://youtu.be/AbkX2splTTg?si=LTHqLFIWQD4hAYsO This workflow collects end-of-day updates from team members in Slack, stores them in Google Sheets, and posts a concise executive summary back to Slack using Google Gemini. How it works Runs daily at 3pm, reads the team roster from Google Sheets, filters out people marked as on leave, and sends each active member an EOD update form in Slack. Receives Slack button/form submissions via a webhook, parses the interactive payload, and replaces the original message with a confirmation. Checks whether the submitted EOD date matches today’s date, and sends a private Slack alert to the owner if someone submits late. For on-time submissions, reads today’s entries from the EOD submissions Google Sheet, deduplicates by user and date, and appends the new submission to Google Sheets. Runs daily at 5pm, reads today’s submissions and yesterday’s “tomorrow plan” entries from Google Sheets and merges them per user. Aggregates the merged data, calculates attendance and expected submission counts from the team roster, and sends the dataset to Google Gemini to generate an executive summary. Posts the generated Slack-formatte
Find and log high-quality domain contacts with Tomba and Google Sheets
Quick overview This workflow runs on a schedule, pulls “Pending” company domains from Google Sheets, uses Tomba to find email addresses for each domain, filters for high-scoring personal contacts, logs the results to an enrichment sheet, and marks each processed domain as Done. How it works Runs on a schedule to check a Google Sheets “Company domains” tab for rows where the status is set to “Pending”. Processes the pending rows one domain at a time to avoid handling the whole list in a single run. For each domain, queries the Tomba API to retrieve up to 50 email addresses associated with the company domain. Filters the returned results to keep only personal emails with a quality score of 90 or higher and extracts key contact fields (name, email, position, company, domain). Appends the filtered contacts to a Google Sheets “Enrichment” tab. Updates the original domain row in Google Sheets to set the status to “Done” and continues with the next pending domain. Setup Connect Google Sheets credentials and update the spreadsheet and sheet references for both the source “Company domains” tab and the destination “Enrichment” tab. Add your Tomba credentials and ensure the domain input maps
Generate and send personalized client proposals with OpenAI, SendGrid, Slack, and Google Sheets
Quick overview This workflow accepts proposal requests via webhook or an hourly schedule, normalizes and validates the client data, uses OpenAI to generate a tailored proposal with pricing, then sends it via SendGrid, logs the request to Google Sheets, notifies a Slack channel, and returns a webhook response. How it works Receives a proposal request from a webhook POST (or runs hourly on a schedule) and maps incoming fields into a consistent client schema. Validates required fields, converts the budget to a number, and assigns a budget tier for pricing. If required data is missing, sends a SendGrid email to the requester listing the validation errors. Routes valid requests by client type (startup, enterprise, agency, nonprofit, or default) and applies conditional pricing and discounts to build line items and totals. Uses OpenAI (GPT-4o-mini) to generate a seven-section, personalized proposal based on the client details, project scope, template context, and pricing. Formats the generated proposal into a branded HTML email with an investment breakdown table. Sends the proposal via SendGrid, appends a tracking row to Google Sheets, posts a Slack notification, and returns a JSON succes
Grade system prompts in Google Sheets with a Gemini LLM judge
Quick overview This workflow manually grades a system prompt by running it against a sample user task with Google Gemini, then has a second Gemini judge score the prompt (1–10) and write the grade and reason back to Google Sheets. How it works Starts when you run the workflow manually. Reads the prompt list from a Google Sheets spreadsheet and keeps only the last row as the system prompt under test. Sets a fixed sample customer-support task and sends it to a Google Gemini-powered agent using the sheet prompt as its system instructions. Sends the original prompt, the sample task, and the agent’s response to a second Google Gemini judge that returns a structured grade and short justification. Updates the same Google Sheets row with the returned grade and reason. Setup Connect a Google Sheets OAuth2 credential with access to the target spreadsheet. Connect a Google AI Studio (Gemini) credential for the candidate model, grader model, and parser-fixer model. Ensure your sheet has columns for at least prompt, grade, and reason, and that the workflow can match rows using the row_number field. Update the spreadsheet ID/sheet and edit the sample task text if you want to test prompts against
Report daily workflow SLA metrics with the n8n API, data tables and Telegram
Quick overview This workflow runs daily, queries the n8n API for workflows and recent executions, calculates per-workflow success rate, error count and p95 runtime over a rolling window, detects stalled schedules, stores a snapshot in an n8n Data Table, and sends a change-aware fleet health report to a Telegram chat. How it works Runs once per day on a Schedule Trigger. Fetches all workflows and a capped set of recent executions from the n8n API. Calculates fleet and per-workflow metrics over a rolling window, including success rate, error count, p95 runtime, and last run time. Detects active scheduled workflows that appear overdue based on their Schedule Trigger interval and a configurable buffer. Loads the previous metrics snapshot from an n8n Data Table and compares it to the current snapshot to flag slowdowns, success-rate drops, newly stalled workflows, and recoveries. Saves the current snapshot back to the Data Table and sends a formatted report message to Telegram. Setup Create an n8n API key with scopes workflow:list and execution:list, save it as an n8n API credential, and select it in the two n8n API request nodes. Create an n8n Data Table named observability_history with
Book, reschedule and confirm WhatsApp appointments with Claude and Sheets
Quick overview This workflow receives WhatsApp messages via a Meta webhook, uses Anthropic Claude to detect booking intents and extract appointment details, writes updates to Google Sheets, and sends a confirmation or error reply back to the customer on WhatsApp. How it works Receives incoming WhatsApp messages through a Meta webhook endpoint and normalizes key fields like sender phone number, display name, message text, and timestamps. Filters out empty messages and sends the text to Anthropic Claude to classify the intent (book, reschedule, confirm, or unknown) and extract structured appointment details. Validates the request based on intent, including required fields and simple rules like weekday-only appointments and business hours. Appends a new row to the Google Sheets Appointments tab for valid bookings, or updates the appointment status/date/time in Google Sheets for reschedules and confirmations. Builds a personalized WhatsApp reply message describing the result (success, required missing details, or supported actions). Sends the reply back to the customer via the WhatsApp Cloud API and appends the interaction details to the Google Sheets ActivityLog tab. Setup Create a Me
Manage inventory reorders with Google Sheets, Slack, and Gmail
Quick overview Youtube Video: https://www.youtube.com/watch?v=y0uCepHhwSA This workflow monitors inventory from Google Sheets on a schedule, calculates reorder quantities using vendor lead times, logs pending reorders back to Google Sheets, and posts grouped reorder requests to Slack, then sends vendor reorder emails via Gmail when an authorized Slack user approves. How it works Runs on a schedule and reads product inventory and vendor catalog data from Google Sheets. Calculates stock runway and a reorder quantity per product using recent sales and vendor average delivery time. Filters to only items that need reordering and aggregates reorder lines into a vendor-level request. Checks the existing reorder log in Google Sheets to avoid reordering items that are pending/sent or were completed within the last 14 days, then groups remaining items by vendor. Writes each vendor reorder request to a Google Sheets reorder log with status set to pending and posts a formatted restock notification to a Slack channel. Triggers on a Slack reaction event, verifies the reacting user matches the configured approver, extracts the Reorder ID from the Slack thread, and looks up the matching row in Goo
WPublish weekly SMB blog posts with Perplexity, Claude, Gemini, Supabase, and Gmail
Quick overview This workflow runs weekly to generate, research, write, illustrate, and publish a new blog post by combining Supabase (content + storage), Perplexity (topic + research), Anthropic Claude (writing), Google Gemini (cover image), and Gmail (notification). How it works Runs every Friday at 10:00 (cron: 0 0 10 * * 5). Fetches titles of already published posts from Supabase and builds a rotating topic focus that avoids repeating prior angles. Uses Perplexity to propose one fresh, SEO-relevant blog topic and then research it with trends, examples, and SMB-focused insights. Sends the topic and research notes to Anthropic Claude to write a complete post with title, excerpt, meta description, category, read time, and HTML body. Parses the generated text into structured fields, generates a slug, and prepares a published blog post record. Uses Google Gemini to generate a 16:9 cover image, uploads it to Supabase Storage, and attaches the public cover image URL to the post. Inserts the finished post into the Supabase blog_posts table with status set to published and emails the team via Gmail with the publication details. Setup Create a Supabase project with a blog_posts table and
WMonitor negative customer reviews with an HTTP API, Google Sheets and Slack
Quick Overview This workflow polls your review API every 6 hours, filters for reviews rated 3 stars or lower, and posts an alert to a Slack channel for each negative review. How it works Runs every 6 hours on a schedule. Fetches the latest reviews from a configured HTTP endpoint. Filters the returned items to keep only reviews with a rating of 3 or below. Checks whether any negative reviews were found and stops if none exist. Posts each negative review to a selected Slack channel with the rating, author, and review text. Setup Provide a reviews API endpoint (and any required authentication) in the HTTP Request node. Connect Slack using an OAuth2 credential. Select the target Slack channel and adjust the rating threshold in the filter logic if you want a stricter or looser definition of “negative”.
Send appointment reminders from Google Sheets via Gmail and Slack
Quick Overview This workflow runs daily at 9:00, reads appointments from Google Sheets, emails next-day patients reminders via Gmail, and posts a reminder count to a Slack channel. How it works Runs every day at 9:00 using a schedule trigger. Reads all appointment rows from a specified Google Sheets worksheet. Filters the rows to keep only appointments whose Date matches tomorrow’s ISO date (YYYY-MM-DD). Sends a personalized reminder email for each remaining appointment using Gmail. Counts how many reminders are sent and generates a summary payload for tomorrow’s date. Posts the reminder count summary to a selected Slack channel. Setup Connect Google Sheets OAuth and set the target spreadsheet and sheet, ensuring columns like Patient, Email, Date, and Time exist. Ensure the Date values in Google Sheets are stored in a format compatible with the filter logic (ISO-style YYYY-MM-DD at the start of the field). Connect Gmail OAuth and update the sender account, subject, and message text as needed. Connect Slack OAuth and select the channel where the front desk summary should be posted.
Capture real estate leads with Google Sheets, Gmail, and Slack
Quick Overview This workflow captures real estate property inquiries via a webhook, saves the lead to Google Sheets, sends an auto-reply email through Gmail, and posts a notification to a Slack channel before returning a JSON confirmation to the website. How it works Receives a POST request from your website form through a webhook endpoint. Extracts and standardizes the lead details (name, email, phone, property ID, and message) from the incoming request. Appends the inquiry details to a Google Sheets CRM spreadsheet. Sends an acknowledgement email to the prospect using Gmail with the referenced property details. Posts a new-lead alert to your agent team in Slack. Returns a JSON response (for example, { "status": "received" }) to confirm the submission was accepted. Setup Connect Google Sheets OAuth credentials and update the target spreadsheet and sheet tab used to store new leads. Connect Gmail OAuth credentials and customize the subject/body of the auto-reply message. Connect Slack OAuth credentials and choose the channel where agent notifications should be posted. Copy the webhook URL from the webhook trigger and configure your website inquiry form to send a POST request with n
Log ecommerce orders, send Slack alerts, and store data in Google Sheets
Quick Overview This workflow receives ecommerce orders via a webhook, formats key order fields, appends each order to Google Sheets, and posts a Slack notification to different channels based on whether the order total exceeds 200. How it works Receives a POST webhook request containing a new order payload from your store. Extracts and normalizes the order ID, customer name, email, total, and items from the webhook body. Appends the order data to a Google Sheets spreadsheet for logging and reporting. Compares the numeric order total to a 200 threshold to determine whether the order is high value. Posts a message to a Slack VIP channel for orders over 200, or to a standard Slack orders channel for all other orders. Returns a JSON confirmation response (including the order ID) back to the webhook caller. Setup Configure your store to send new order events to this workflow’s webhook URL (POST /new-order). Add a Google Sheets OAuth2 credential and set the target spreadsheet and sheet where orders should be appended. Add a Slack OAuth2 credential and set the channel IDs for the VIP and standard order notifications. Adjust the high-value threshold (currently 200) to match your order rout
Create work4all incoming invoices from Microsoft Outlook supplier emails
Quick Overview This workflow polls a Microsoft Outlook folder for new supplier emails, sends each message to a companion n8n sub-workflow that creates an incoming invoice in work4all, and then categorizes the email (green/yellow/red) and emails errors via Outlook. How it works Runs every minute on a schedule. Fetches all emails from a specified Microsoft Outlook folder that are not already categorized as Red or Green, downloading any attachments. Sends each email to a companion sub-workflow that extracts invoice data from attachments and creates the incoming invoice in work4all. If the sub-workflow returns errors, sends an error notification email via Microsoft Outlook and categorizes the original message as Red. If no errors occur, categorizes the message as Green when booking is clean, or as Yellow + Green when a supplier was created or an account/tax key was set automatically. Setup Import and publish the companion workflow "Create a work4all incoming invoice from email attachments using AI" and select it in the Execute Workflow step. Add Microsoft Outlook credentials with permission to read the target mailbox and send emails. Update the Outlook folder ID to monitor and ensure t
WScrape business emails from Google Maps to Google Sheets
Quick overview This workflow takes a list of Google Maps search queries, extracts candidate business website URLs from the search results, visits each site, scrapes email addresses from the page content, and appends cleaned, deduplicated emails to Google Sheets fully automated, no manual research needed. How it works A manual trigger fires with a pinned list of Google Maps search queries, each representing a location and business type combination. A query loop iterates through each query, launching a sub-workflow execution per query and applying a configurable wait between executions to reduce request bursts. The sub-workflow sends an HTTP GET to the Google Maps search results URL for that query and reads the raw HTML response. A code node extracts all URLs from the HTML using a regex pattern, after which a filter node removes known system domains such as Google, gstatic, schema.org, and Wix internals, and a deduplication node removes repeated URLs before visiting. A URL loop processes each candidate business website one at a time, fetching the page HTML and passing it into the email processing flow. A code node applies a regex to the fetched page content to extract email-shaped st
WFetch and parse Amazon SP-API reports into structured TSV rows
Quick Overview This workflow manually requests an Amazon Selling Partner (SP-API) report, polls until it is ready, downloads the report document, optionally decompresses it if it is GZIP, and parses the TSV contents into one n8n item per row. How it works Starts when you run the workflow manually. Uses Login with Amazon (LWA) to exchange your refresh token, client ID, and client secret for an access token. Calls the Amazon SP-API Reports API to create a report for the configured report type and marketplace. Polls the Amazon SP-API until the report processing status is DONE (or errors if it fails or times out). Fetches the report document metadata and downloads the report file from the provided URL. If the document is GZIP-compressed, decompresses the file and then parses the TSV into structured JSON items, outputting one item per row. Setup Create and authorize Amazon SP-API (Login with Amazon) credentials, then fill in the refresh_token, client_id, and client_secret values in the Config step. Set the correct SP-API endpoint region (EU/NA/FE), report_type, and marketplace_ids values in the Config step. If you want to store or route results, add downstream nodes after the parsed row
Monitor website changes with PolyDoc screenshots and email alerts
Quick Overview This workflow checks a website URL every 6 hours, detects content changes by hashing the normalized HTML, and when a change is found it uses PolyDoc to capture a full-page screenshot and emails the PNG as an attachment. How it works Runs every 6 hours on a schedule. Sets the target URL to monitor and fetches the page HTML with an HTTP request. Normalizes the HTML (removing scripts/styles/comments), hashes it, and compares it with the previous run stored in workflow static data. If the hash changed, PolyDoc captures a full-page PNG screenshot of the URL. Sends an email with the screenshot attached and the monitored URL in the subject and body. Setup Update the monitored website URL in the Settings step. Add your PolyDoc API credentials to the PolyDoc screenshot step. Configure an SMTP email credential and set the to/from email addresses in the email step.
Detect competitor launch signals from ads with OpenAI and Google Sheets
Quick Overview This workflow runs weekly to scan competitor ad copy from Meta, Google Ads, and LinkedIn via Adyntel, detects newly emerging terms, uses OpenAI to assess launch signals, and records results in Google Sheets while sending a Slack alert when a launch signal is detected. How it works Runs every week on a schedule (Monday) to start the competitor monitoring cycle. Reads competitors marked as Pending from Google Sheets and processes them one by one. For each competitor domain, pulls current ads from Meta, Google Ads, and LinkedIn using Adyntel and combines the results. Extracts and deduplicates ad titles and body copy, then loads the competitor’s previously known terms from Google Sheets. Extracts candidate new terms from this week’s ad copy, filters for terms that recur across multiple ads, and decides whether there are meaningful new terms to analyze. If meaningful new terms exist, sends the context to OpenAI to classify the terms and determine whether a product launch signal is present, then appends the signal record and the newly classified terms to Google Sheets. If no meaningful new terms exist, appends baseline terms from this week’s ad titles to Google Sheets to p
Extract ecommerce product data with Google Sheets, ScrapingBee and Gemini
Quick Overview This workflow manually runs to read a list of webpage URLs from Google Sheets, scrape each page with ScrapingBee, and use Google Gemini to extract structured product data from screenshots with an HTML fallback, then append the results back into a Google Sheets sheet. How it works Runs when you manually trigger the workflow. Reads the list of URLs to scrape from a Google Sheets spreadsheet. Fetches a full-page screenshot for each URL using the ScrapingBee API. Sends the screenshot (and the URL for context) to a Google Gemini model to extract product details into a structured JSON format, calling a ScrapingBee HTML fetch tool when screenshot extraction is incomplete. Converts any fetched HTML to Markdown and returns it to the Gemini agent to complete the extraction. Splits the extracted product array into individual items and appends them as new rows in the Google Sheets “Results” sheet. Setup Create a Google Sheets service account connection in n8n and set the target spreadsheet and the “List of URLs” and “Results” sheet selections. Add a Google Gemini (PaLM) API credential in n8n and ensure the selected model (gemini-1.5-pro-latest) is available for your account. Add
Email form
On form submission, validates the email with Hunter and sends a message via SendGrid.
Lead Enrichment To Pipedrive
On a form submission, enriches the lead with Hunter and Clearbit, then creates the contact in Pipedrive.
TheHive to SIGNL4 Alerting
On a webhook, evaluates a TheHive condition and fires a SIGNL4 alert, halting on error.