Browse 12,955 Workflows

By WeblineIndia

Quick overview This workflow runs daily to query the GDELT News API for a chosen theme, detects unusual one-day news-volume spikes, uses Google Gemini to generate a market-impact analysis for a sector and watchlist tickers, logs the results to Google Sheets, and posts an alert to Slack. How it works Runs every day at the configured hour using a schedule trigger. Builds a GDELT query for the configured theme, sector, and watchlist tickers, then requests a 1-day news timeline from the GDELT Doc API. Calculates the latest news-volume value, computes a 7-day baseline from prior timeline points, and flags the event if the spike exceeds the 50% threshold. For detected spikes, assigns a severity level (LOW/MEDIUM/HIGH) and classifies the event category based on theme keywords. Sends the event metrics to Google Gemini to produce a JSON analysis including an event summary, narrative, sector impact, ticker-by-ticker impacts, market implication, and disclaimer. Appends the combined spike metrics and Gemini analysis to a Google Sheets log for historical tracking. Posts a formatted Slack message with the spike details and AI analysis to the selected channel. Setup Add a Google Gemini (PaLM/AI Studio) API credential and select the Gemini model you want to use. Connect Google Sheets credentials, and set the target spreadsheet/document ID and sheet tab, ensuring the columns used by the workflow exist (or allow n8n to create them). Connect Slack credentials and choose the channel where the alert should be posted. Update the monitored theme, sector, and ticker list (and optionally the spike threshold in code) to match what you want to track. Additional info Add-ons The current workflow already combines scheduled monitoring, GDELT data collection, statistical spike detection, event classification, Gemini analysis, Google Sheets logging, and Slack alerting. The following are potential extensions that can be added to expand its usage: Email Alerts Add an email notification after event analysis so important alerts can also be delivered through email. Multiple Themes Run multiple themes through the workflow instead of monitoring only one configured theme. For example, separate monitoring could be created for different sectors or event categories. Additional Data Sources Add other news or market-data sources alongside GDELT to provide additional information before the Gemini analysis stage. Historical Trend Analysis Store historical results and compare current event activity against longer-term historical patterns. Database Storage Replace or supplement Google Sheets with a database for larger-scale event history and querying. Advanced Alert Rules Add conditions based on: Severity Spike percentage Event type Specific ticker impact Sector impact This can help reduce unnecessary notifications. Dashboard Integration Connect the stored event data to a reporting or dashboard system to visualize event trends over time. Multi-Channel Notifications Add additional notification channels so different teams can receive alerts through their preferred communication system. These are extension ideas only. They are not part of the current workflow JSON. Use Case Examples 1. Semiconductor Export Monitoring The current workflow configuration monitors: Theme: semiconductor export Sector: Semiconductors Tickers: NVDA, AMD, TSM, INTC, AVGO It can detect a significant increase in news activity around semiconductor exports and use Gemini to assess the potential impact on the configured watchlist. 2. Energy Event Monitoring The event classification logic supports themes containing oil or energy. A suitable configured theme can therefore be used to identify news spikes related to energy events and classify them as: ENERGY 3. Supply Chain Monitoring Themes containing shipping or supply are classified as: SUPPLY CHAIN This can be used to monitor unusual news activity around supply-chain-related themes. 4. Sector-Specific Market Intelligence A team can configure a theme and sector together with a watchlist of relevant tickers. When a significant news spike occurs, Gemini can provide a structured assessment of how the event may affect the selected sector and individual tickers. 5. Automated Global Event Alerts The workflow can be used as a scheduled monitoring system where users do not need to manually check news volume every day. Significant spikes are processed automatically, logged to Google Sheets, and delivered through Slack. These are examples based on the capabilities and classification logic present in the workflow. There can be more use cases depending on how the theme, sector, ticker list, and downstream integrations are configured. Troubleshooting Guide | Issue | Possible Cause | Solution | | --------------------------------------------- | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | | Workflow does not start automatically | The schedule trigger is not configured as expected or the workflow is inactive | Check Daily Event Scan Trigger and make sure the workflow is activated | | GDELT request fails | The GDELT HTTP Request configuration is incorrect or the API does not return the expected response | Check the Fetch GDELT News Timeline URL, query parameters, and returned data | | Not enough timeline data | The GDELT response contains fewer than two timeline entries | Verify the GDELT response and the selected theme | | Spike is always false | The calculated increase is below the 50% threshold | Review the news volume and adjust spikeThreshold if required | | Event does not continue after spike detection | spikeDetected is not true | Check the calculation in Calculate News Volume Spike and the condition in Check Spike Threshold | | Event category is OTHER | The theme does not contain any configured category keywords | Update the theme or extend the logic in Classify Event Category | | Gemini returns an empty response | Gemini did not return content | Check the Gemini credential, model configuration, and node execution | | Gemini response cannot be parsed | Gemini returned content that is not valid JSON | Check the Gemini prompt and ensure the requested response follows the defined JSON structure | | Google Sheets logging fails | Google Sheets credentials or destination configuration is incorrect | Check the credentials, spreadsheet, worksheet, and column mapping | | Slack alert is not delivered | Slack credentials or destination channel configuration is incorrect | Check the Slack credential and channel configuration | | Ticker analysis is missing | The watchlist data is not available in the expected format | Check the tickers configuration and the data passed into the Gemini node | | Historical results are not appearing | The Google Sheets node cannot append the record | Check the Google Sheets node execution and column mappings | Need Help? Setting up an n8n workflow may require more than importing the workflow JSON. API credentials, business rules, data mappings, integrations, notification channels and custom automation requirements may need to be configured based on your environment. WeblineIndia can help you design, customize and implement n8n automation workflows based on your business requirements. For more information about our n8n automation services, expertise, workflow development and related solutions, visit: Everything in n8n Automation | Offshore Workflow Experts. An n8n automation workflow template by WeblineIndia.

By Tom Last

Quick overview This workflow acts as a generic state-machine runtime in n8n, replaying a case from an event stream stored in Data Tables, validating and appending new events, and optionally dispatching an entered-state task by starting a bound n8n sub-workflow asynchronously. How it works Receives an execution request from another workflow and validates the input event (or an inspect-only request) and its identifiers. Loads and validates state-machine definitions from an n8n Data Table catalog. Reads the case’s existing events from an n8n Data Table, replays them to reconstruct the current state, and checks whether the requested transition is allowed (or returns the current status for inspect). If the event is accepted and not a duplicate, appends the new event to the case event stream Data Table with the next sequence number and resolved correlation/causation details. If the entered target state declares a task, looks up the machine/version/task binding in a Data Table and prepares a task invocation payload. If a binding is available, starts the bound n8n workflow asynchronously and returns the applied transition result along with dispatch status, otherwise returns the applied transition result with an “unavailable” dispatch reason. Setup Create and connect three n8n Data Tables for machine definitions, the case event stream, and task bindings, and update the Data Table IDs in the corresponding Data Table nodes. Populate the machine definitions table with JSON definitions that include matching machine/version columns and exactly one default flag in the catalog. Populate the task bindings table with one row per machine + version + task that maps to a published n8n workflowId to run for that task. Call this workflow from an adapter workflow using Execute Workflow and pass either {"caseId":"...","operation":"inspect"} or an event envelope including caseId, eventId, type, payload, and (for new cases) machine and machineVersion. An n8n automation workflow template by Tom Last.

By Sam

Quick overview Ask a question in a form; this workflow searches the web with DuckDuckGo and has an OpenRouter model write a report in which every claim cites a page it read, with every quote checked against its source. Self-hosted n8n only. How it works Receives a question and depth selection from an authenticated n8n Form. Uses an OpenRouter LLM to split the question into 3–5 sub-questions and DuckDuckGo search queries based on the selected depth. Runs each query through the DuckDuckGo Search community node, fetches top results with page text, grades whether evidence is usable or blocked, and paces requests to reduce rate limiting. Deduplicates and numbers all collected sources (S1, S2, …) and stops early with a notice if there are too few usable sources or too many searches are blocked. Uses the LLM to extract per-sub-question findings with exact quotes, then programmatically verifies each quote exists in the corresponding source text and discards unverified findings. If enough verified findings exist, the LLM writes a Markdown report citing only source IDs, and the workflow removes uncited sentences, invalid citations, links/HTML, and adds an evidence-coverage table and a clickable source list. Renders the final Markdown to HTML and displays the report (or a “no report” explanation) back in the form response. Setup Use a self-hosted n8n instance and install the community node n8n-nodes-duckduckgo-search via Settings → Community nodes. Create and select an OpenRouter credential (API key) for the OpenRouter chat model used for planning, extraction, and writing. Publish the n8n Form trigger and use its production URL to submit questions (the form requires users to be signed in to n8n). Requirements Self-hosted n8n only: community nodes cannot be installed on n8n Cloud The community node n8n-nodes-duckduckgo-search An OpenRouter account and API key No API key or account is needed for DuckDuckGo Customization Change the depth options in the form; each sub-question is one DuckDuckGo search Change how many pages are read per search in Search DuckDuckGo Swap the OpenRouter model; any model that returns JSON reliably works Keep the wait between searches: DuckDuckGo limits requests per IP address Send the report by email or Slack instead of showing it on the form page Additional info The canvas preview does not render community nodes, so the full canvas is in the screenshot at the top of the description. The AI-suggested JSON replaced all six sticky notes with one saying the workflow "does not contain any nodes", so I kept the original file; its sticky notes follow the sticky-note guidelines. Source and notes: https://github.com/samnodehi/n8n-nodes-duckduckgo/tree/main/docs/examples. An n8n automation workflow template by Sam.

By Juan Carlos Morales

Quick overview Turn 1–10 video clips, an optional voiceover and optional SRT captions into one finished MP4 for YouTube Shorts, Reels or TikTok, without hosting FFmpeg yourself. Built for faceless channels, AI video pipelines and agencies. Runs on Apify at $0.20 per finished video; failed jobs and the demo are free. How it works Starts when you run the workflow manually. Builds a video job payload that includes a list of clip URLs plus optional voiceover and SRT captions, along with orientation, fit mode, and a maximum duration. Sends the job to the Apify Short Video Assembler API to scale/crop or pad clips, concatenate them, add the voiceover, and burn in captions into a single MP4. Returns the resulting public MP4 URL along with the render duration and job status. Setup Create an Apify account and copy your Apify API token from Apify Console. In the HTTP request to Apify, add an HTTP Header Auth credential with Authorization: Bearer . Update the job payload to include 1–10 publicly accessible clips URLs (and optionally voiceover_url and captions_srt) and adjust orientation, fit, and max_seconds as needed. Requirements Apify account (free tier works) and its API token Video clips and audio at public http(s) URLs Pay per use: $0.20 per finished video on Apify, no subscription Customization Set orientation to vertical (1080x1920), horizontal or square, and fit to crop or pad Limit length with max_seconds (1-60) Swap the manual trigger for a schedule, form or webhook, and send the video URL to YouTube, Google Drive or Slack Additional info Try it before adding your own media: run the workflow once with the empty clips list and it renders a free 12-second demo video. Each output is checked (length, resolution, audio track) before you are charged. An n8n automation workflow template by Juan Carlos Morales.

By Abdullah Saeed Aly Elhusseiny

Quick overview Handshake AI turns every conference handshake into a follow-up. Send a Telegram card photo, voice note or text; OpenAI (and Groq for voice) extracts and researches the contact, saves it to Google Sheets, drafts a Gmail follow-up and sends an interactive Telegram card for review, sending and reminders. How it works Triggers from a Telegram message/callback, a daily 9:00 schedule, a Sunday 18:00 schedule, or a self-call when one photo contains multiple cards. Interprets the incoming message (photo, voice, text, command, reply edit, or button tap). Only chat IDs listed in allowedChatId can use the bot; until that is set, it only replies with its guide and your chat ID. For photos, downloads the image from Telegram and uses OpenAI to extract one or more contact records; for voice notes, downloads and transcribes audio via Groq and then uses OpenAI to extract the contact; for plain text, uses OpenAI to structure the contact details. Normalizes the contact data, checks Google Sheets for an existing match to avoid duplicates, then uses OpenAI web search to research the person and generate a lead score plus a personalized follow-up message. Creates or replaces a Gmail draft when an email address is available, writes/updates the contact row in the Google Sheets “Contacts” tab, and posts a Telegram summary card with buttons for actions like showing/sending/rewriting the draft, snoozing, marking status, WhatsApp/LinkedIn links, and saving a vCard. Handles commands like /ask, /search, /people, /top, /stats, /recap, /nudges, and /match by reading from Google Sheets, using OpenAI where needed, and replying in Telegram (including drafting intro emails in Gmail for suggested introductions). Sends a daily Telegram reminder of due follow-ups and quiet contacts, and a weekly Telegram message suggesting introductions based on your saved contacts. Setup Create a Telegram bot with @BotFather and add a Telegram Bot credential in n8n. Add credentials for OpenAI, Google Sheets and Gmail. For voice notes, add your Groq API key as an HTTP Header Auth credential (Name: Authorization, Value: Bearer YOUR_GROQ_KEY) on the "Transcribe voice note" node. Create a Google Sheet with a tab named “Contacts” and put “id” in cell A1, then paste the spreadsheet ID into the Config values. Fill in the Config values (your name, role, offer, default event name, language/tone, follow-up delay, allowedChatId, and time zone) and ensure the workflow time zone matches your local schedule requirements. Activate the workflow and send /start to your bot. The reply ends with your chat ID: paste it into allowedChatId in Config (add more IDs with commas; the first one is the owner who gets reminders and can send emails). Until you do, the bot only replies with its guide. Requirements A Telegram bot token from @BotFather An OpenAI API key (models are set to gpt-4.1-mini) Gmail and Google Sheets accounts A free Groq API key for voice notes (optional) Customization Change the tone, language or length of the emails in Config and in the Write follow-up email prompt. Change how many days until a follow-up reminder with followUpDays in Config. Swap Google Sheets for another database by replacing the sheet steps; every section reads and writes the same columns Additional info Tip: in @BotFather use /setcommands to show the commands in Telegram's menu (help, people, search, top, match, nudges, stats, edit, ask, recap, event). Nothing is ever emailed without your tap on Send: follow-ups are saved as Gmail drafts first. Contacts stay in your own Google Sheet. An n8n automation workflow template by Abdullah Saeed Aly Elhusseiny.

By Mugdha Vairagade

Quick overview This workflow runs an email-verified, timed quiz using n8n Forms, n8n Data Tables, and SMTP email sending, including resend limits, one-attempt-per-email enforcement, random question selection, automatic scoring, and saving results. How it works Receives a quiz sign-up through an n8n Form with a name and email address. Normalizes and validates the entry, checks n8n Data Tables to see if the email has already participated, and applies per-email and per-hour rate limits for verification codes. If allowed, generates a 6-digit verification code, sends it via SMTP email, and logs only a SHA-256 hash of the code to the quiz_codes n8n Data Table. Prompts the participant to enter the emailed code in a second n8n Form and verifies it against the latest stored hash while enforcing code expiry and a maximum number of attempts. When the code is valid, creates a participant record in the quiz_results n8n Data Table and selects 10 random multiple-choice questions plus 1 feedback question from the quiz_questions n8n Data Table. Presents the timed quiz form, then scores submitted answers (or records a timeout/late submission), updates the participant’s result in n8n Data Tables, and shows the score completion page when applicable. Setup Create an SMTP credential (for example Cloudflare Email Routing/Email Sending over SMTP) and update the sender details used to send the verification email. Run the one-time manual setup path to create the quiz_codes and quiz_results n8n Data Tables. Create and populate a quiz_questions n8n Data Table with columns qid, type, difficulty, text, options, answer, and active, ensuring at least 10 active mcq questions (4 options separated by |) and at least 1 active text question. Activate the workflow and share the public URL of the entry form so participants can start the sign-up process. Requirements 1) Three data tables - quiz_questions, quiz_codes, quiz_results created from the provided CSV files. 2. Claudeflare SMTP credential with Customization Change the time limit and the difficulty mix in Pick Questions1. Change the code expiry and resend limits in Check Request. Edit the result messages in Score Answers1. An n8n automation workflow template by Mugdha Vairagade.

By Umarjon

Quick overview This workflow watches your Gmail inbox for Upwork job-alert emails, uses OpenAI to extract and score each job against your freelancer profile, then sends high-scoring opportunities as formatted cards to Telegram with a button to open the job link. How it works Triggers every minute when a new Upwork email arrives in Gmail matching the search filter. Adds your freelancer profile, preferred language, and minimum score threshold to the incoming email data. Uses OpenAI (GPT model) to parse the email, extract all listed jobs, and return a JSON list with summaries, risks, and a 0–10 fit score. Splits the results into one item per job, drops jobs below the minimum score, and selects a safe Upwork link (direct job URL, “View job details” link, or a fallback search link). Formats each remaining job into an HTML Telegram message card with score, budget, summary, and key reasons/risks. Sends each card to Telegram with an inline button that opens the job on Upwork. Setup Connect Gmail Trigger credentials and adjust the Gmail search query (e.g., sender and time window) to match your Upwork alert emails. Add OpenAI credentials and confirm the selected model is available for your account. Create a Telegram bot with @BotFather, add Telegram credentials in n8n, and set your target chat ID in the Telegram message node. Update the “Your profile & settings” values (profile text, language, and minimum score) to match your preferences. An n8n automation workflow template by Umarjon.

By Jason

Quick overview This workflow runs on demand to scrape Google Maps business listings with websites via Apify, enriches each website with emails and phone numbers using Apify’s Contact Details Scraper, and appends the merged lead data (business details plus contacts and social links) to Google Sheets. How it works Runs when you manually execute the workflow. Defines the search query, target location, maximum places to crawl, and an Apify spend cap. Uses Apify’s Google Maps Scraper to collect businesses that have a website for the specified search and location. De-duplicates the resulting websites and sends the unique domains to Apify’s Contact Details Scraper to extract emails, phone numbers, contact URLs, and social profiles. Merges the Google Maps business data with the extracted contact details by matching on website domain. Appends the combined lead rows to a selected Google Sheets worksheet. Setup Add an Apify API token credential and select it in both Apify nodes (Google Maps Scraper and Contact Details Scraper). Add a Google Sheets credential, then choose the target spreadsheet and worksheet in the Google Sheets append step. Update the search term, location, maxPlaces, and maxCostUsd values to match your lead criteria and budget. Requirements Apify account (free plan works). Google Maps Scraper bills per place; Contact Details Scraper bills only for websites where an email or phone is found (about $3 per 1,000). Each run is capped by maxCostUsd. Customization Loop over several searches or cities, run it on a Schedule trigger, add a Filter to keep only rows with an email, or send rows to your CRM instead of Google Sheets. Additional info Uses the verified Apify community node (@apify/n8n-nodes-apify). On self-hosted n8n, install it from Settings > Community nodes. Contact details come only from public business websites; follow CAN-SPAM, GDPR and similar rules when contacting leads. An n8n automation workflow template by Jason.

By dilshi

Quick overview This workflow collects blog keywords via an n8n form, uses Anthropic Claude to plan and write an SEO-focused article based on a reference post’s structure, then assembles the content into HTML, generates SEO metadata and FAQs, and saves the result as a draft post in WordPress. How it works Receives a blog request from an n8n form with keywords, desired section count, and a target word count. Fetches a reference article URL over HTTP and extracts its title, headings, and paragraph pacing to guide the new article’s structure. Uses Anthropic Claude to generate a JSON outline containing a post title, a short introduction, and question-style H2 section headings with writing prompts. Writes each section’s body in HTML with Anthropic Claude, then sanitizes the output and combines it with the introduction into a single article body. Uses Anthropic Claude to produce a quick summary, suggested SEO title, meta description, and five FAQs, then formats the summary and FAQs into HTML. Creates a draft WordPress post with the assembled HTML content and returns a form completion message showing the suggested SEO title and meta description. Setup Add an Anthropic credential for the Claude steps used to generate the outline, section content, and SEO/FAQ fields. Add a WordPress credential (typically via application password) with permission to create posts. Update the reference article URL, target audience, and tone of voice values in the workflow settings before running. Activate the workflow and use the form URL from the form trigger to submit keywords and article length parameters. An n8n automation workflow template by dilshi.

By NewBrainsAI

Quick Overview This workflow runs every weekday morning to read open document requests from Google Sheets, uses OpenAI to draft reminder emails in your firm’s tone, sends them via Gmail, and updates the sheet with the last-sent date and reminder count. How it works Runs every weekday at 8am on a schedule. Loads rows from the Google Sheets “Requests” tab where Status is set to Open. Calculates how many reminders have been sent, how many days have passed since the last email, and whether the next email is a first request, reminder, or final reminder. If enough time has passed and the reminder limit is not exceeded, uses OpenAI to generate a short email subject and body for the specific client and document. Sends the generated email to the client using Gmail with the configured reply-to address. Updates the same Google Sheets row with today’s date in “Last sent” and increments the “Reminders” count. Setup Create a Google Sheet with a “Requests” tab that includes columns Client, Email, Document, Due date, Status, Last sent, Reminders, and ensure open items have Status set to Open. Add Google Sheets credentials and paste your spreadsheet ID into the workflow’s Settings values. Add Gmail credentials and set the reply-to address in the Settings values. Add an OpenAI credential, and (optionally) adjust the tone, daysBetweenReminders, and maxReminders settings to match your reminder policy. An n8n automation workflow template by NewBrainsAI.

By Gilbert Losert

Quick overview This workflow watches for new unread Gmail messages, uses OpenAI to classify each email and draft a reply, then either creates a Gmail draft in the original thread and labels the message for follow-up, or files it by applying FYI/Noise labels. How it works Triggers every minute when a new unread email arrives in Gmail. Sends the email subject and snippet to OpenAI to return a category, a draft reply, and a flag indicating whether the sender is waiting for an answer. If an answer is needed, creates a Gmail draft reply in the same thread addressed to the original sender. Labels the original Gmail message as YouDecide when OpenAI classifies it as “du”, otherwise labels it as Drafted. If no answer is needed, labels the original Gmail message as Noise when OpenAI classifies it as “werbung”, otherwise labels it as FYI. Setup Connect your Gmail OAuth2 account and select the same credential in the Gmail trigger and all Gmail action steps. Add your OpenAI API credentials and pick a model that can return JSON. The system message is already written - adjust the four category definitions if your inbox needs different buckets. Create the four Gmail labels used by the workflow (YouDecide, Drafted, FYI, Noise) and update the label IDs in the labeling steps if they differ in your account. An n8n automation workflow template by Gilbert Losert.

By Scout Forge

Quick overview This workflow runs every Monday to fetch new Google Maps business leads via an Apify actor, filters them using an AI-based target description, and appends the matched leads to a Google Sheets worksheet. How it works Runs every Monday at 08:00 on a schedule. Sets the Google Maps search query, location, ideal-customer description, and maximum number of leads to retrieve. Calls the Apify actor (scoutforge/google-maps-leads) to collect only new leads that match the provided target description. Appends the returned lead records to a selected Google Sheets spreadsheet and worksheet. Setup Add an Apify token as an HTTP Header Auth credential with header name Authorization and value Bearer YOUR_APIFY_TOKEN_HERE. Update the search query, location, target description, and max leads in the configuration step to match your prospecting needs. Connect your Google Sheets account, then select the target spreadsheet and sheet where leads should be appended. Requirements Apify account (free accounts get 10 leads per run) Google account with Google Sheets Customization Add several search queries or change the schedule Send leads to Airtable or a CRM instead of Google Sheets Add an email outreach step after the leads are saved Additional info The actor filters businesses with an AI relevance check before charging, so you only pay for leads that match your target description. Pricing is per lead delivered ($0.035). Start with maxLeads set to 10 to test the workflow on a free Apify account. Actor page: https://apify.com/scoutforge/google-maps-leads. An n8n automation workflow template by Scout Forge.