Category: n8n Workflows

What This Workflow Does

This n8n workflow automates the processing and routing of WordPress Contact Form 7 submissions. When a visitor submits a contact form on your WordPress site, the workflow automatically captures the response, classifies it by type or department, generates a draft reply using AI, and logs the information for your team to review and action.

How It Works

The workflow begins when a contact form submission triggers a webhook from your WordPress site. Here is the step-by-step process:

• A Contact Form 7 submission is sent via webhook to n8n
• The incoming data is formatted and prepared for processing
• Google Gemini AI analyzes the message content to understand context and intent
• A text classifier categorizes the submission into predefined departments or topics
• An LLM chain generates a professional draft response with subject line and email body
• The classified information and draft reply are stored in Google Sheets for team review
• The workflow is logged with completion details

Use Cases

• Customer Support Triage: Automatically sort support tickets by urgency level and route them to the appropriate support team member or department
• Lead Qualification: Classify incoming leads by business type, budget range, or interest category to prioritize sales follow-ups
• Content Inquiry Management: Route blog inquiries, partnership proposals, and media requests to the correct department automatically
• Event Registration Processing: Categorize event registrations by attendance type and automatically draft personalized confirmation emails
• Feedback Collection: Classify customer feedback as praise, complaint, or suggestion, then generate appropriate response templates for your team

Nodes Used

• Webhook: Receives Contact Form 7 submissions from WordPress
• Set Node: Formats and prepares the form data for processing
• Google Gemini: Analyzes message content using advanced AI language models
• Text Classifier: Categorizes submissions into defined categories or departments
• Chain LLM: Generates professional draft email responses with subject lines
• Gmail: Sends notifications or responses via email
• Google Sheets: Records and stores classified submissions and draft replies
• Output Parser Structured: Formats the final output in a structured format
• Sticky Note: Provides workflow documentation and notes

Prerequisites

• Active WordPress site with Contact Form 7 plugin installed
• CF7 to Webhook plugin installed and activated on your WordPress site
• n8n account with access to create and manage workflows
• Google account for Gemini AI access and Google Sheets integration
• Gmail account configured for sending email notifications
• Webhook URL from n8n added to the CF7 to Webhook plugin settings
• Predefined classification categories created before workflow deployment

Difficulty Level

Intermediate. This workflow requires basic knowledge of n8n, WordPress plugins, and integration setup. You will need to configure the webhook connection between WordPress and n8n, set up Google API credentials, define your classification categories, and test the workflow before deploying to production. No coding is required, but familiarity with automation platforms is recommended.

This workflow template is shared under the n8n fair-code license. Free to use and modify.

What This Workflow Does

This n8n workflow automates a scheduled task that retrieves data from an external API and sends the results via email. It runs on a predetermined schedule, making it ideal for automating routine data collection and notifications without manual intervention.

How It Works

The workflow follows this process:

• A cron trigger initiates the workflow at your specified time intervals
• An HTTP request node fetches data from an external API endpoint
• A function node processes and transforms the retrieved data
• A Gmail node formats and sends the processed information via email
• A sticky note provides documentation and reference information for workflow management

Use Cases

• Daily weather report aggregation sent to your inbox every morning
• Scheduled monitoring of website uptime or API availability with automated alerts
• Weekly data summaries from analytics platforms compiled and emailed to stakeholders
• Automated price tracking for e-commerce products with periodic email notifications
• Regular data synchronization between external services with email confirmation logs

Nodes Used

• Cron: Schedules workflow execution at specific times and intervals
• HTTP Request: Fetches data from external APIs and web services
• Function: Executes custom JavaScript code to transform and process data
• Gmail: Sends formatted emails with workflow results
• Sticky Note: Adds documentation and notes within the workflow canvas

Prerequisites

• An active n8n instance or n8n cloud account
• Access credentials for the target API you wish to query
• Gmail account with app password authentication enabled or OAuth2 credentials configured
• Knowledge of API endpoints and response structure for your data source
• Basic understanding of JavaScript for the function node (optional but recommended)

Difficulty Level

Intermediate. This workflow requires basic API knowledge and familiarity with n8n node configuration. The function node may need customization depending on your specific data transformation needs, making JavaScript knowledge helpful for advanced modifications.

This workflow template is shared under the n8n fair-code license. Free to use and modify.

What This Workflow Does

This workflow automates lead capture and customer engagement by connecting WordPress Elementor forms directly to email marketing and CRM systems. When someone submits a form on your website, the workflow automatically saves their information to a spreadsheet database, sends confirmation emails to both the lead and your team, and enrolls them in scheduled promotional campaigns.

How It Works

The workflow begins when an Elementor form submission triggers a webhook. The lead data is immediately processed and stored in Google Sheets or Excel, creating a centralized CRM database. Simultaneously, two automated emails are sent—one notifying the website owner of the new lead and another welcoming the customer. On a scheduled basis, the workflow pulls contacts from the spreadsheet and sends batch promotional messages to keep your audience engaged with timely marketing content.

Use Cases

• Service-based businesses collecting client inquiries and sending instant confirmation emails with service details
• E-commerce stores capturing customer interest in products and sending follow-up promotional offers on a weekly schedule
• Real estate agencies capturing property inquiry forms and automatically notifying agents while sending buyer information packets
• SaaS companies collecting trial signup forms and sending onboarding emails plus scheduled feature update campaigns
• Event organizers capturing registrations and sending confirmation emails with event details plus reminder campaigns before the event date

Nodes Used

• Webhook – Listens for incoming Elementor form submissions from your WordPress site
• Gmail – Sends automated emails to lead recipients and website owners
• Schedule Trigger – Initiates recurring email campaigns at specified intervals
• Google Sheets – Stores lead data in a spreadsheet CRM and retrieves contacts for campaigns
• Split in Batches – Divides large contact lists into manageable groups for email sending
• No Operation – Handles conditional paths without executing additional actions
• Sticky Note – Provides workflow documentation and setup instructions

Prerequisites

• WordPress site with Elementor forms installed and configured
• n8n account with webhook capabilities enabled
• Gmail account or Google Workspace for sending automated emails
• Google Sheets or Excel spreadsheet for storing lead data
• Basic understanding of webhook URLs and form integration
• Email templates prepared for lead confirmations and promotional campaigns

Difficulty Level

Intermediate. This workflow requires connecting multiple platforms and understanding how webhooks capture form data. While the core setup is straightforward, customizing email templates and scheduling campaigns requires some configuration knowledge. Beginners may need to reference documentation for webhook URL setup and Gmail authentication.

This workflow template is shared under the n8n fair-code license. Free to use and modify.

What This Workflow Does

This n8n workflow automates weekly technology research by leveraging artificial intelligence to gather, analyze, and distribute tech news and insights. Every Monday at 9 AM, the system uses Perplexity AI to research the latest technology trends, stores findings in Notion for organization and reference, and delivers a comprehensive summary via Gmail to keep you informed about industry developments.

How It Works

The workflow operates through a series of coordinated steps that run on a predetermined schedule:

• A scheduled trigger initiates the workflow every Monday morning at 9 AM
• The AI monitoring agent receives a system prompt that defines its research goals and parameters
• Perplexity AI conducts searches and gathers current technology research based on the agent’s instructions
• The Think tool processes and analyzes the collected information
• Results are formatted and stored in a Notion database for long-term tracking and reference
• A Gmail message is automatically composed and sent with the weekly research summary

Use Cases

• Technology Blog Research: Automatically gather weekly trending topics and emerging technologies to fuel content creation for tech blogs and publications
• Competitive Intelligence Monitoring: Track competitor announcements, product releases, and industry movements to stay ahead in the market
• Software Developer Updates: Collect weekly summaries of new programming languages, frameworks, libraries, and development tools relevant to your tech stack
• Executive Briefings: Generate weekly executive summaries of significant tech industry news and disruptions for leadership presentations
• Academic Research Support: Automate the collection of latest research papers, breakthroughs, and academic developments in specific technology fields

Nodes Used

• Schedule Trigger: Configures the automated weekly execution at a specific day and time
• Gmail: Handles the sending of formatted research summaries via email
• Perplexity AI via OpenRouter: Performs intelligent web research and analysis using advanced language models
• Sticky Note: Provides inline documentation and workflow notes for clarity
• Notion: Stores and organizes research findings in a structured database format
• n8n Agent: Manages the overall research workflow and decision-making process
• Think Tool: Processes and analyzes information before storage and distribution

Prerequisites

• An active n8n account with workflow creation capabilities
• Gmail account configured with SMTP access or n8n Gmail integration
• Notion account with database creation permissions
• OpenRouter API key for accessing Perplexity AI models
• Basic understanding of AI prompts and research parameters
• Email address configured to receive weekly research reports

Difficulty Level

Intermediate. This workflow requires familiarity with scheduling concepts, API integrations, and basic prompt engineering. Users should be comfortable with n8n’s interface and have experience setting up at least one external service integration. Customizing the AI agent’s prompt and adjusting research parameters requires some technical knowledge, but the workflow structure itself is straightforward to implement.

This workflow template is shared under the n8n fair-code license. Free to use and modify.

What This Workflow Does

This n8n workflow automates WordPress SEO optimization by integrating GPT-5 Nano with Yoast SEO. It analyzes your WordPress content, generates SEO-optimized suggestions, and automatically applies improvements to enhance search engine rankings and content quality across your website.

How It Works

The workflow uses a webhook trigger to receive content from WordPress, processes it through GPT-5 Nano for AI-powered analysis and optimization suggestions, and then applies those recommendations using the Yoast SEO plugin. Content is batched for efficient processing, with results logged to Google Sheets and notifications sent via Gmail. The system includes error handling to ensure smooth operation across multiple posts.

Use Cases

• Automatically optimize blog post titles, meta descriptions, and keywords for better search rankings
• Batch process existing WordPress content to improve SEO performance across your entire site
• Generate AI-powered content suggestions that comply with Yoast SEO best practices and guidelines
• Create weekly reports of optimized content and track SEO improvements in Google Sheets
• Streamline content review workflows by combining AI suggestions with Yoast recommendations before publishing

Nodes Used

• Manual Trigger – Start the workflow manually from n8n dashboard
• Webhook – Receive content triggers from WordPress
• Split in Batches – Process multiple posts efficiently
• HTTP Request – Connect to WordPress and Yoast SEO APIs
• OpenAI (@n8n) – Generate SEO optimization suggestions using GPT-5 Nano
• Set – Configure and map data between workflow steps
• Stop and Error – Handle workflow errors and validation
• Split Out – Distribute processed data to multiple outputs
• Markdown – Format optimization results for readability
• Code – Execute custom logic for data transformation
• Google Sheets – Log optimization results and create reports
• Gmail – Send notifications about completed optimizations
• Summarize – Condense optimization data for summaries
• Sticky Note – Add workflow documentation and notes

Prerequisites

• WordPress website with Yoast SEO plugin installed and activated
• OpenAI API key for GPT-5 Nano access
• n8n instance (self-hosted or cloud)
• WordPress REST API enabled
• Google Sheets account for logging results
• Gmail account for sending notifications
• Yoast SEO API credentials or plugin access tokens

Difficulty Level

Intermediate to Advanced. This workflow requires familiarity with API connections, WordPress administration, and basic workflow logic. Users should understand how to configure OAuth credentials for Google and OpenAI services, and have knowledge of WordPress REST API endpoints and Yoast SEO data structures.

This workflow template is shared under the n8n fair-code license. Free to use and modify.

What This Workflow Does

This Snyk Vulnerability Automation Workflow automatically detects, validates, and routes security vulnerabilities from Snyk or other vulnerability sources to the appropriate teams and tracking systems. It captures vulnerability data through a webhook, standardizes the information, validates critical fields, and intelligently distributes alerts and tickets to Slack, Jira, and Airtable based on severity and validity.

How It Works

The workflow begins with a webhook that receives vulnerability payloads from Snyk or external security scanning tools. The incoming data flows through a normalization function that converts all vulnerability information into a consistent, standardized format. A validation function then checks that essential fields such as vulnerability ID, title, CVSS score, affected package, and source URL are present and properly formatted.

Valid vulnerabilities automatically proceed through conditional logic that routes them to multiple destinations simultaneously. The workflow sends real-time alerts to Slack for immediate team notification, creates corresponding Jira tickets for formal tracking and remediation, and logs all vulnerability details in an Airtable database for historical record-keeping and analysis. Invalid or incomplete vulnerability records are flagged and held for manual review, ensuring no critical information is lost.

Use Cases

• Security teams receiving vulnerability reports from Snyk can automatically create Jira tickets and notify developers in Slack, reducing manual data entry and response time.
• DevOps teams managing multiple projects can centralize all vulnerability data in Airtable while maintaining real-time communication through Slack and formal tracking in Jira.
• Organizations integrating multiple security tools can normalize vulnerability data from different sources into a single standardized workflow, ensuring consistent processing regardless of the scanning tool.
• Compliance-focused teams can maintain detailed audit trails in Airtable while ensuring no critical vulnerabilities are missed through automated Slack notifications and ticket creation.
• Development teams can receive immediate Slack notifications about vulnerabilities affecting their projects while automatically generating technical tickets in Jira with all necessary context and metadata.

Nodes Used

• Webhook: Entry point that receives vulnerability payloads from Snyk or external security sources in real-time.
• Function: Normalizes and standardizes incoming vulnerability data into a consistent format across all sources.
• Code: Validates that required fields including vulnerability ID, title, CVSS score, package name, and URL are present and valid.
• If: Conditional branching that routes valid vulnerabilities to processing destinations and flags invalid records for manual review.
• Slack: Sends real-time alerts and notifications to team channels about detected vulnerabilities and their severity levels.
• Jira: Creates and updates tickets in Jira for formal vulnerability tracking, assignment, and remediation workflow management.
• Airtable: Records all vulnerability data in a centralized database for logging, analysis, reporting, and historical reference.
• Sticky Note: Provides workflow documentation and guidance for users and team members reviewing the automation process.

Prerequisites

• An active n8n instance with webhook functionality enabled and accessible from your Snyk or security tool environment.
• Snyk account with API access or configured webhooks to send vulnerability notifications to your n8n webhook URL.
• Jira instance with API token authentication configured for automated ticket creation and updates.
• Slack workspace with a bot token or webhook URL configured to send messages to designated security channels.
• Airtable account with a base created for vulnerability tracking, including properly configured tables and fields.
• Basic understanding of JSON data structures for vulnerability payloads and field mapping between systems.

Difficulty Level

Intermediate. This workflow requires familiarity with webhook configuration, data normalization, and multi-system integration. Users should be comfortable mapping fields between different platforms and understanding conditional logic, but no advanced programming is required as the core logic is pre-built and modular.

This workflow template is shared under the n8n fair-code license. Free to use and modify.

What This Workflow Does

This workflow automates customer support by combining artificial intelligence with your WHMCS ticketing system. When customers interact with the chatbot, it intelligently understands their questions, processes them through Google Gemini AI, and automatically creates support tickets in WHMCS without manual intervention. This streamlines your support process and ensures no customer inquiry goes unaddressed.

How It Works

The workflow operates through a series of interconnected nodes that handle conversation and ticket creation:

• A chat trigger receives incoming customer messages through a conversational interface
• The memory buffer window maintains conversation context across multiple exchanges
• Google Gemini AI analyzes the customer’s message and determines the appropriate response
• An agent node orchestrates the workflow and decides whether to create a support ticket
• HTTP request tools communicate with your WHMCS API to automatically generate tickets with customer details and issue descriptions

Use Cases

• SaaS companies receiving high volumes of billing and account questions that can be automatically logged as tickets for follow-up
• Web hosting providers capturing technical support requests from customers and creating tickets with relevant system information
• Digital agencies managing client inquiries by automatically creating internal tickets while providing immediate chatbot responses
• E-commerce platforms handling customer complaints and returning them as priority support tickets in WHMCS
• Managed service providers documenting all customer interactions and ensuring nothing falls through the cracks

Nodes Used

• Chat Trigger: Captures incoming customer messages and initiates the workflow
• Memory Buffer Window: Maintains conversation history to provide context-aware responses across multiple turns
• LM Chat Google Gemini: Powers intelligent response generation using Google’s advanced language model
• Agent: Orchestrates the entire workflow and makes decisions about ticket creation
• HTTP Request Tool: Communicates with WHMCS API to create tickets with customer information

Prerequisites

• An active n8n instance (self-hosted or cloud)
• Google Gemini API credentials and appropriate API key
• WHMCS installation with API access enabled
• WHMCS API credentials (username and API key)
• Basic understanding of webhook URLs and API endpoints
• Properly configured customer fields in WHMCS for ticket creation

Difficulty Level

Intermediate. This workflow requires configuration of external APIs (Google Gemini and WHMCS) and understanding of conversation flow management. Most technical users with API experience can set this up in 30-45 minutes. Customization for specific business logic may require additional development.

This workflow template is shared under the n8n fair-code license. Free to use and modify.

What This Workflow Does

TagihanAir is an automated water billing system that integrates Telegram messaging with Google Sheets and AI-powered data processing. The workflow collects water consumption data through a Telegram bot, processes it using Google Gemini AI, validates the information, and stores everything in a structured Google Sheet for billing records.

How It Works

The workflow begins when a user sends a message to the Telegram bot. The message triggers the automation pipeline, which uses a switch node to route the data appropriately. The AI language model (powered by Google Gemini) processes the input to extract relevant billing information such as customer name, previous meter reading, current meter reading, and pricing. The structured output parser validates and formats this data, which is then automatically recorded in a Google Sheet with columns for all billing details including volume consumed, price per cubic meter, charges, and total amount due. Users receive confirmation through Telegram once their data is processed.

Use Cases

• Water utility companies automating meter reading collection and bill calculation
• Property management organizations tracking tenant water consumption
• Municipal services processing residential water billing requests
• Agricultural operations monitoring water usage across multiple locations
• Commercial enterprises managing water expense allocation across departments

Nodes Used

• Telegram Trigger: Listens for incoming messages from users
• Switch Node: Routes messages based on conditions
• Telegram Send: Sends confirmation messages back to users
• Chain LLM: Orchestrates the AI processing pipeline
• Google Gemini LM Chat: Processes natural language input using Google’s AI model
• Structured Output Parser: Formats and validates extracted billing data
• Google Sheets: Stores billing records in organized spreadsheet format
• Code Node: Performs custom calculations and transformations
• Set Node: Manages variable assignments throughout the workflow
• Sticky Note: Provides documentation and notes within the workflow

Prerequisites

• Active Telegram account with messaging capability
• Telegram Bot created via BotFather with valid API token
• Google account with access to Google Sheets
• Google Cloud project with Gemini API enabled
• n8n account with automation platform access
• Pre-created Google Sheet with designated columns for billing data
• Basic understanding of workflow automation concepts

Difficulty Level

Intermediate. This workflow requires setting up multiple external services (Telegram Bot, Google Sheets, Google Gemini API) and understanding how to connect them through n8n. While the automation itself handles most complex tasks through AI processing, initial configuration demands careful attention to API tokens, spreadsheet structure, and node connections. Users with experience in chatbots or data automation will find this workflow more accessible.

This workflow template is shared under the n8n fair-code license. Free to use and modify.

What This Workflow Does

The Wazuh Alert Investigation workflow automates the process of receiving security alerts from Wazuh, analyzing them using artificial intelligence, summarizing the findings, and delivering investigation results directly to Telegram. This workflow combines security monitoring with intelligent analysis to streamline incident response and threat investigation.

How It Works

The workflow begins when a webhook receives an incoming Wazuh alert. The system conditionally routes the alert based on specific criteria using an if node. The alert data is then processed through an OpenAI language model chat interface that performs deep analysis of the security event. A summarization node condenses the analysis into concise, actionable insights. Finally, the investigation results are delivered to a Telegram channel or chat for immediate notification and review by security teams.

Use Cases

• Security teams receiving real-time notifications of suspicious activities with AI-powered analysis and recommendations for remediation
• Automated threat intelligence gathering where Wazuh alerts are analyzed and summarized for executive security briefings
• Incident response workflows that triage alerts based on severity and send detailed investigation summaries to on-call security personnel
• Compliance monitoring systems that log and analyze security alerts while maintaining audit trails through summarized Telegram notifications
• MSP (Managed Service Provider) operations centers that handle alerts from multiple customer Wazuh instances with centralized analysis and reporting

Nodes Used

• Webhook: Receives incoming Wazuh security alerts as HTTP requests
• If: Conditionally routes alerts based on specified criteria and alert properties
• NoOp: Placeholder node for workflow branching logic
• OpenAI Chat (LM Chat): Analyzes alert content using large language model intelligence
• Summarization: Condenses analysis results into brief, actionable summaries
• Telegram: Sends investigation results and summaries to Telegram channels or users

Prerequisites

• Active Wazuh installation with the ability to configure webhook notifications
• OpenAI API key for accessing GPT language model capabilities
• Telegram bot token with appropriate permissions to send messages
• Telegram channel or user ID where alerts should be delivered
• n8n instance with internet access to reach external APIs
• Basic understanding of Wazuh alert configuration and webhook setup

Difficulty Level

Intermediate. This workflow requires familiarity with Wazuh alert systems, API authentication with OpenAI, and Telegram bot configuration. Users should have experience setting up webhooks and basic understanding of conditional logic in automation workflows. No advanced coding is required, but technical troubleshooting skills are beneficial.

This workflow template is shared under the n8n fair-code license. Free to use and modify.

What This Workflow Does

The Dynamic Weather Forecast Bot is an automated system that delivers weather information through multiple channels while leveraging AI-powered capabilities for intelligent forecast analysis. This workflow combines scheduled reporting with interactive chat functionality, enabling both passive information delivery and active user engagement.

How It Works

The workflow operates in two complementary modes that work independently yet share the same data processing infrastructure:

• Scheduled Daily Summary: Automatically triggers every day at 9:00 AM to fetch weather data via HTTP request, process it through custom code logic, and distribute formatted summaries to Gmail and Slack simultaneously
• Interactive AI Agent Mode: Responds to chat triggers by accepting user queries, processing them through an OpenAI language model with memory buffering, and using HTTP tools to fetch real-time weather data on demand
• Memory Management: The workflow maintains conversation context through a buffer window, allowing the AI agent to understand conversation history and provide coherent multi-turn interactions

Use Cases

• Daily Weather Briefings for Remote Teams: Automatically send weather summaries to team members via Slack every morning, helping distributed teams plan their day with current conditions
• Weather-Dependent Business Operations: Retail stores, construction companies, or outdoor event planners can receive automated alerts about weather patterns affecting their operations
• Personal AI Weather Assistant: Users can chat naturally with the AI agent asking questions like “What should I wear tomorrow?” or “Is it safe to travel this weekend?”
• Multi-Channel Weather Notifications: Ensure critical weather information reaches stakeholders through both email and Slack, guaranteeing message delivery across preferred communication channels
• Weather Impact Analysis for Decision Making: Businesses can query the AI agent about weather implications for scheduling, inventory management, or customer planning

Nodes Used

• Manual Trigger: Allows manual execution of the workflow for testing purposes
• Schedule Trigger: Executes the workflow on a defined schedule, set to daily at 9:00 AM
• HTTP Request: Fetches weather data from external APIs and sends formatted messages to various endpoints
• Code: Processes and transforms raw weather data into formatted summaries
• Gmail: Sends weather reports and notifications via email
• Slack: Distributes messages to Slack channels and users
• Sticky Note: Provides workflow documentation and notes within the editor
• Chat Trigger: Captures user messages from chat interfaces
• Agent: Orchestrates AI-powered decision making and tool usage
• LM Chat OpenAI: Processes natural language through GPT models for intelligent responses
• Memory Buffer Window: Maintains conversation history for contextual AI responses
• HTTP Request Tool: Enables the AI agent to fetch real-time data during conversations

Prerequisites

• Active n8n instance or n8n Cloud account with workflow execution capabilities
• Weather API credentials (such as OpenWeatherMap, WeatherAPI, or similar service)
• Gmail account with app-specific password for SMTP authentication
• Slack workspace with bot token and appropriate channel permissions
• OpenAI API key for accessing GPT language models
• Basic understanding of workflow triggers and HTTP API integration
• Configured email and Slack credentials in n8n credentials manager

Difficulty Level

Intermediate. This workflow requires familiarity with multiple integrations and some understanding of AI agent configuration. While individual components are straightforward, coordinating scheduled tasks, custom code logic, multiple notification channels, and AI-powered interactions requires moderate technical knowledge. Beginners should review each node’s configuration carefully, while experienced users can easily customize data sources and processing logic.

This workflow template is shared under the n8n fair-code license. Free to use and modify.