Category: n8n Workflows

What This Workflow Does

This automated Stripe invoicing workflow monitors ClickUp for status changes and automatically creates invoices in Stripe when specific conditions are met. Once an invoice is generated, the workflow sends it via Gmail to notify you or your team about the new invoice creation. This eliminates manual invoice creation and ensures timely notifications across your business tools.

How It Works

The workflow follows these steps:

• A ClickUp trigger watches for updates to tasks or projects in your ClickUp workspace
• A conditional check evaluates whether the status change meets your invoice creation criteria
• If conditions are met, an HTTP request communicates with the Stripe API to generate a new invoice
• The invoice details are processed through the Stripe node to finalize creation
• A Gmail notification is automatically sent to alert your team about the new invoice
• The workflow logs the action back to ClickUp for record-keeping and tracking

Use Cases

• Service-based businesses that invoice clients upon project completion by updating ClickUp task status
• Subscription management where invoice creation is triggered by status changes in your project management system
• Freelance agencies that need automatic invoice generation when client projects reach specific milestones
• E-commerce businesses that require invoicing when orders transition to a fulfillment status in ClickUp
• Consulting firms that generate invoices automatically when client engagements are marked as ready to bill

Nodes Used

• ClickUp Trigger: Monitors ClickUp for status updates and changes
• If Node: Creates conditional logic to determine when invoices should be created
• HTTP Request: Makes API calls to communicate with Stripe and other services
• Stripe Node: Handles invoice creation and management in your Stripe account
• Gmail Node: Sends automated email notifications about new invoices
• ClickUp Node: Logs workflow actions back to ClickUp for documentation
• Sticky Note: Provides workflow documentation and important reminders

Prerequisites

• An active ClickUp account with projects and tasks set up
• A Stripe account (recommended to use Test Mode first for safe testing)
• A Gmail account connected to n8n for sending notifications
• n8n instance with access to the above applications
• API credentials and authentication tokens for ClickUp and Stripe
• Configured ClickUp statuses that will trigger invoice creation

Difficulty Level

Intermediate. This workflow requires basic knowledge of automation concepts, API integration, and conditional logic. While the setup involves connecting three different services, the workflow structure is straightforward. Users should be comfortable with authentication credentials and have basic understanding of their Stripe and ClickUp configurations. Testing in Stripe’s Test Mode before going live is highly recommended.

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

What This Workflow Does

The Student Admission and Onboarding Automation workflow streamlines the entire student application process by automating data validation, processing, and database updates. This n8n workflow eliminates manual data entry, reduces processing time, and ensures consistent application handling across your educational institution. By scheduling daily executions, the workflow continuously monitors and processes pending applications without requiring manual intervention.

How It Works

The workflow operates through a series of interconnected automated steps that handle student applications from initial submission to database integration:

• A scheduled trigger initiates the workflow every day at 7 AM, ensuring consistent processing times
• Student data is extracted from Excel spreadsheets or connected databases containing pending applications
• Application data is validated for completeness, format accuracy, and required field verification
• Validated applications are processed and transformed into the required database format
• Student records are updated in the primary student database with processed information
• Email notifications are sent to relevant stakeholders confirming application status
• Webhook responses provide real-time feedback on workflow execution and data processing results

Use Cases

• Batch Application Processing: Process hundreds of student applications daily during admission seasons without manual intervention
• Multi-Stage Validation: Ensure data integrity by validating applications against multiple criteria before database entry
• Automated Notifications: Send confirmation emails to students and admission officers about application status and next steps
• Database Synchronization: Keep student records synchronized across multiple systems and spreadsheets in real-time
• Scheduled Reporting: Generate daily reports of processed applications and maintain audit trails for compliance purposes

Nodes Used

• Schedule Trigger: Initiates workflow execution at 7 AM daily for consistent processing schedules
• Microsoft Excel: Reads pending student applications and application data from Excel spreadsheets
• Code Node: Implements custom validation logic and data transformation rules for application processing
• If Condition: Routes applications based on validation results and status conditions
• Email Send: Dispatches notifications to students and admissions staff regarding application status
• Respond to Webhook: Provides immediate feedback on workflow execution and processing outcomes
• Sticky Note: Provides workflow documentation and processing guidelines within the automation canvas

Prerequisites

• n8n instance installed and configured with workflow automation capabilities
• Microsoft Excel or Google Sheets integration connected for reading application data
• Database connection configured for student record management and updates
• Email service configured for sending notifications to students and staff
• Webhook endpoint available for receiving real-time execution feedback
• Excel spreadsheet containing student application data with standardized column headers
• Access credentials for all connected services with appropriate permissions
• Pre-defined validation rules and data format specifications for student applications

Difficulty Level

Intermediate: This workflow requires moderate n8n experience and understanding of database operations, data validation concepts, and email service configuration. Users should be comfortable working with conditional logic, data transformation in code nodes, and integrating multiple services. Basic knowledge of Excel data structures and email notification setup is recommended. Customization of validation rules and data mapping will require coding skills.

This workflow template is shared under the March 4, 2026

What This Workflow Does

This workflow automates the entire content syndication process by extracting articles from your sitemap, processing them through AI, generating platform-specific social media posts, and publishing them across Twitter and LinkedIn. It eliminates manual posting work and ensures consistent content distribution across multiple channels.

How It Works

The workflow begins by parsing your XML sitemap to identify all published content. It then checks a Google Sheets database to determine which articles have already been processed, preventing duplicate syndication. For new articles, the workflow fetches the full content and uses AI (Google Gemini) to generate customized social media posts optimized for each platform. Finally, it automatically publishes these posts to both Twitter and LinkedIn while logging the processed articles back to Google Sheets for future reference.

Use Cases

• Marketing agencies managing content distribution for multiple clients across social platforms
• Publishers automatically sharing blog posts and news articles to increase reach and engagement
• Content creators maintaining consistent social media presence without manual posting overhead
• Corporate communications teams ensuring company updates are published across all channels simultaneously
• SEO professionals amplifying content distribution to boost article visibility and backlink opportunities

Nodes Used

• Manual Trigger and Schedule Trigger for workflow initiation
• XML node for parsing sitemap data
• HTTP Request for fetching article content
• Split Out and Filter nodes for data processing and validation
• Google Sheets integration for tracking processed articles
• Google Gemini AI and Agent nodes for generating social content
• Structured Output Parser for formatting AI responses
• Twitter and LinkedIn nodes for publishing posts
• Merge and Aggregate nodes for combining workflow data
• Code node for custom logic and transformations
• Conditional logic with If node for workflow branching

Prerequisites

• A website with an XML sitemap accessible via URL
• Google Sheets account with a spreadsheet for tracking processed articles
• Google Gemini API key for AI-powered content generation
• Twitter/X account with API credentials for posting
• LinkedIn account with proper API access for publishing
• n8n instance with credentials configured for all external services

Difficulty Level

Advanced. This workflow requires configuration of multiple third-party API credentials, understanding of XML parsing, and familiarity with Google Sheets integration. Users should have experience with n8n workflows and be comfortable setting up authentication tokens for social media platforms.

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

What This Workflow Does

This automated workflow continuously monitors supplier risk by integrating data from Dun & Bradstreet, news sources, and your business database. It scores suppliers based on multiple risk factors and automatically sends alerts to Gmail when risk thresholds are exceeded. The system enables proactive supply chain management by identifying potential disruptions before they impact operations.

How It Works

The workflow operates on a scheduled trigger, running at configured intervals to assess supplier health. Here is the process flow:

• Schedule trigger initiates the workflow at set times
• PostgreSQL database retrieves your current supplier list and risk parameters
• HTTP requests fetch real-time supplier data from Dun & Bradstreet financial records
• News API integration searches for recent news mentions affecting supplier reputation
• Custom code node calculates risk scores based on financial health, news sentiment, and historical data
• Conditional logic evaluates whether scores exceed your defined thresholds
• Gmail sends automated alerts for critical and high-risk suppliers
• Google Sheets logs all results for audit trails and trend analysis

Use Cases

• Manufacturing Supply Chains: Monitor component suppliers for financial instability or production disruptions reported in industry news
• Retail Procurement: Track vendor financial health and market reputation to prevent stockouts from supplier failures
• Logistics Operations: Identify shipping and fulfillment partners with emerging risks before service degradation occurs
• Pharmaceutical Distribution: Maintain compliance by monitoring critical suppliers for regulatory violations or quality issues
• Technology Vendors: Assess software and hardware suppliers for financial distress or security-related news coverage

Nodes Used

• Schedule Trigger: Sets the frequency for automated workflow execution
• Postgres: Connects to your database to retrieve supplier lists and configuration parameters
• HTTP Request: Fetches supplier data from Dun & Bradstreet APIs and external sources
• News API: Searches for recent news articles mentioning your suppliers
• Code Node: Custom JavaScript logic calculates risk scores using weighted criteria
• If Node: Routes workflow based on risk level thresholds
• Gmail: Sends alert notifications for high-risk suppliers
• Google Sheets: Logs risk assessments and historical data for reporting
• Sticky Note: Provides inline documentation and configuration instructions

Prerequisites

• n8n instance with database connectivity
• PostgreSQL database containing supplier master data
• Dun & Bradstreet API credentials for financial data access
• News API key for news monitoring functionality
• Gmail account configured for n8n with app-specific password or OAuth token
• Google Sheets document for logging risk scores and alerts
• Defined risk scoring methodology and threshold parameters

Difficulty Level

Intermediate. This workflow requires basic familiarity with n8n, understanding of API connections, and ability to customize the risk scoring logic. Database setup knowledge and Gmail authentication are necessary. Most users can deploy the template within 30 minutes after configuring API credentials and database connections.

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

What This Workflow Does

This workflow automates the remediation of security vulnerabilities by enriching vulnerability alerts with organizational context from Port. It intelligently routes security findings to the appropriate teams or AI agents for rapid response and remediation, eliminating manual triage and accelerating your security response time.

How It Works

The workflow follows a streamlined process to handle security vulnerabilities:

• A webhook receives new vulnerability alerts from your security scanner (such as Snyk, Dependabot, or similar tools)
• The workflow queries Port’s context lake to enrich the alert with relevant organizational and service information
• OpenAI analyzes the vulnerability details and determines appropriate remediation steps
• An if statement routes the vulnerability to the correct team or AI agent based on severity and service ownership
• Slack notifications are sent to notify the relevant teams of the vulnerability and required actions
• The workflow logs and tracks all remediation activities for compliance and audit purposes

Use Cases

• Automatically triage and enrich vulnerability alerts from multiple security scanners with service ownership and deployment information
• Route critical vulnerabilities directly to on-call engineers or security teams via Slack notifications
• Generate AI-powered remediation recommendations tailored to your specific service architecture and tech stack
• Track vulnerability remediation workflows end-to-end for compliance reporting and security metrics
• Reduce mean time to remediation (MTTR) by automating alert enrichment and team notification

Nodes Used

• Webhook: Receives incoming vulnerability alerts from security scanners
• Port.io (Custom Node): Enriches vulnerabilities with organizational context and service metadata
• OpenAI: Analyzes vulnerabilities and generates remediation recommendations
• If: Routes vulnerabilities based on severity level and service ownership
• HTTP Request: Makes API calls to external systems or internal tools as needed
• Slack: Sends notifications to teams about vulnerabilities and required actions
• Sticky Note: Provides workflow documentation and step descriptions

Prerequisites

• An active n8n instance with webhook capabilities enabled
• A security scanner or vulnerability management tool configured to send alerts (Snyk, Dependabot, or similar)
• Port account with API access and configured context lake data
• OpenAI API key for vulnerability analysis and recommendation generation
• Slack workspace with bot permissions for sending messages to channels
• Proper authentication credentials configured for all integrated services

Difficulty Level

Intermediate. This workflow requires familiarity with webhooks, API integrations, and conditional routing. Setup involves configuring connections to Port, OpenAI, and Slack, but the workflow logic is well-structured and easy to customize for your organization’s specific needs.

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

What This Workflow Does

This n8n workflow automates booking management by integrating with Xendit payment processing. It captures booking requests through a webhook, processes payment information, and manages the booking workflow with status updates and confirmations.

How It Works

The workflow operates through the following process:

• A webhook receives incoming booking requests from your application or form
• The Set node organizes and structures the booking data
• Custom code validates and transforms the request parameters
• Xendit API integration processes payment transactions securely
• An HTTP request sends booking confirmation to external systems
• A wait timer introduces delays for asynchronous processing
• The workflow responds back to the webhook with status confirmation

Use Cases

• Hotel and accommodation booking systems with instant payment processing
• Restaurant or venue reservation platforms requiring upfront deposits
• Event ticketing systems that need automated payment collection
• Service provider scheduling with payment verification before confirmation
• Tour and travel booking automation with multi-step payment flows

Nodes Used

• Webhook: Receives incoming booking requests and triggers the workflow
• Set: Initializes and structures variables for the booking process
• Code: Executes custom JavaScript for data validation and transformation
• HTTP Request: Communicates with external APIs and confirmation endpoints
• Xendit (GOWA): Processes payments through Xendit’s payment gateway
• Wait: Introduces delays for asynchronous operations and processing intervals
• Respond to Webhook: Sends confirmation response back to the requesting client
• Sticky Note: Provides inline documentation and workflow notes

Prerequisites

• Active Xendit account with API credentials (Test or Live environment)
• Xendit API Key generated from your dashboard account settings
• A webhook URL from n8n workflow for receiving booking requests
• Understanding of webhook integration and HTTP request handling
• Basic knowledge of JSON data structures for booking information
• Access to any external booking management systems for integration

Difficulty Level

Intermediate. This workflow requires familiarity with payment gateway integration, webhook configuration, and API authentication. Users should understand how to configure Xendit API credentials and map booking data fields correctly. No advanced programming knowledge is required, but comfort with API documentation and debugging 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 your entire service package recommendation process, from initial lead capture through proposal delivery and follow-up scheduling. It intelligently matches client budgets to appropriate service tiers, generates personalized proposal emails with relevant case studies, automatically logs all interactions to your sales pipeline tracker, and schedules calendar reminders for timely follow-ups. This eliminates manual proposal writing while ensuring consistent, professional communication that converts inquiries into booked calls.

How It Works

• Form Trigger: Captures lead information including budget, project type, and contact details from your intake form
• Google Sheets Lookup: References your package database to match the lead’s budget range to recommended service tiers and corresponding case studies
• Switch Logic: Routes leads based on budget category (starter, professional, enterprise) to appropriate proposal templates
• Set Variables: Constructs personalized proposal content with client name, recommended package, pricing, and relevant case studies
• Gmail Send: Delivers beautifully formatted proposal email with all package details and social proof
• Google Calendar: Automatically schedules a follow-up reminder for your team based on lead priority
• Sticky Note: Creates a visual reminder card for high-value leads requiring immediate attention

Use Cases

• Freelance Service Providers: Automatically recommend design, development, or marketing packages based on client budget constraints, reducing sales cycle time from days to minutes
• SaaS Companies: Match prospects to appropriate plan tiers (Basic, Pro, Enterprise) with relevant customer success stories and ROI calculations
• Digital Agencies: Deliver customized project proposals with case studies matching the prospect’s industry and project scope within hours of inquiry
• Coaching Businesses: Route clients to group programs, one-on-one coaching, or premium packages based on their stated investment level
• B2B Consulting: Generate tiered engagement proposals automatically while ensuring sales team receives calendar alerts for strategic follow-ups

Nodes Used

• Form Trigger: Entry point capturing lead submission data
• Google Sheets: Stores package tiers, pricing, and case study library for dynamic recommendations
• Switch: Routes workflow based on budget range conditions
• Set: Assembles proposal content with dynamic variables
• Gmail: Sends personalized proposal emails
• Google Calendar: Schedules follow-up reminders
• Sticky Note: Creates priority alerts for high-value opportunities

Prerequisites

• Active n8n instance (self-hosted or cloud)
• Google account with Sheets and Gmail access
• Pre-built Google Sheet containing your service packages, pricing tiers, and case study library organized by industry or project type
• Google Calendar connected for scheduling follow-ups
• Web form or lead capture system configured to trigger the workflow
• Email templates prepared with proposal format and branding
• Understanding of your sales process and follow-up timelines

Difficulty Level

Intermediate: This workflow requires basic familiarity with n8n node configuration, Google Sheets data structure, and conditional logic using the Switch node. No coding required, but understanding your sales process and proper data organization in Google Sheets is essential for optimal results. Allow 30-45 minutes for initial setup and testing.

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

What This Workflow Does

The Service Ticket Triage Helper automatically analyzes incoming service tickets using artificial intelligence to classify and validate critical information. When a new ticket arrives, the workflow uses AI to determine whether essential fields like ticket type, priority level, and recipient assignment can be accurately identified from the ticket content.

How It Works

The workflow begins by capturing a new service ticket through the Taiga trigger. A sticky note provides workflow context and instructions. The system then evaluates the ticket data through conditional logic to check if sufficient information exists. An AI agent powered by OpenAI’s language model analyzes the ticket content to extract and classify:

• Ticket type classification (bug, feature request, support issue, etc.)
• Priority level determination (critical, high, medium, low)
• Recipient or assignment recommendation

The structured output parser formats the AI’s analysis into consistent, actionable data that can be used for further workflow automation or manual review.

Use Cases

• Customer support teams receiving tickets through multiple channels can automatically validate data completeness before assignment to support specialists.
• Development teams can use this workflow to pre-screen bug reports and feature requests to identify which tickets have sufficient detail for immediate action.
• IT help desk operations can triage incoming requests by automatically categorizing them and flagging incomplete submissions for additional information.
• Service desk managers can identify patterns in incomplete ticket submissions to improve customer intake forms and self-service documentation.
• Multi-team organizations can automatically route tickets to the correct department based on AI-determined classification before human review.

Nodes Used

• Taiga Trigger: Captures incoming service tickets from the Taiga project management system.
• Sticky Note: Provides documentation and workflow context for team reference.
• If Node: Implements conditional logic to check data completeness and determine workflow path.
• Taiga Node: Interacts with Taiga to retrieve or update ticket information.
• Switch Node: Routes the workflow based on classification results.
• Agent Node: Enables AI-powered analysis and decision-making on ticket content.
• Output Parser Structured: Converts AI responses into structured, formatted data.
• LM Chat OpenAI: Provides the language model capabilities for ticket analysis and classification.

Prerequisites

• Active Taiga project management account with API access configured.
• OpenAI API key with sufficient credits for language model queries.
• n8n instance with access to the OpenAI integration and agent capabilities.
• Service tickets containing at minimum a title and description field.
• Basic understanding of workflow triggers and conditional logic in n8n.

Difficulty Level

Advanced. This workflow requires knowledge of AI integration, conditional logic, structured data parsing, and API connections. Users should be comfortable working with language models, understanding prompt engineering concepts, and troubleshooting multi-node workflows. Customization of the AI prompts and classification criteria will likely be necessary for specific use cases.

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

What This Workflow Does

This n8n workflow automates the process of sending WhatsApp reminder messages to customers who have abandoned their shopping carts on Shopify. It cleans and verifies phone numbers, retrieves abandoned cart data, includes direct product links via Rapiwa, and schedules messages at optimal times to recover lost sales.

How It Works

The workflow operates through the following process:

• A schedule trigger initiates the workflow at specified intervals to check for new abandoned carts
• The httpRequest node retrieves abandoned cart data from your Shopify store
• A code node cleans WhatsApp numbers by removing spaces, dashes, parentheses, and special characters to standardize the format
• The if node validates that numbers are legitimate, active WhatsApp accounts to prevent wasted messages and credits
• Google Sheets integration stores and tracks all abandoned cart records and messaging attempts
• The splitInBatches node divides contacts into manageable groups to prevent API rate limiting
• A wait node introduces delays between batch sends to comply with WhatsApp API restrictions
• The Rapiwa integration generates shortened product links and sends personalized WhatsApp messages with cart recovery content

Use Cases

• E-commerce Cart Recovery: Automatically remind customers about items left in their shopping carts within hours of abandonment to increase conversion rates
• Time-Sensitive Promotions: Send flash sale alerts and limited-time offers via WhatsApp to customers with abandoned carts, leveraging urgency to drive purchases
• Multi-Product Campaigns: Notify customers about complementary or related products they viewed alongside abandoned items to increase average order value
• Customer Segmentation: Target high-value customers or repeat buyers who abandoned carts with personalized messages and exclusive incentives
• International Sales: Reach customers across different regions using WhatsApp while maintaining compliance with local messaging regulations

Nodes Used

• httpRequest: Fetches abandoned cart data from Shopify API and sends WhatsApp messages through Rapiwa
• scheduleTrigger: Executes the workflow automatically at defined intervals (hourly, daily, or custom schedules)
• code: Cleans phone numbers by removing formatting characters and standardizing international number formats
• stickyNote: Provides inline documentation and workflow notes for team reference
• if: Validates WhatsApp numbers and creates conditional logic branches for active versus inactive accounts
• googleSheets: Logs abandoned cart details, customer information, and message delivery status for analytics and auditing
• wait: Introduces time delays between message batches to respect WhatsApp API rate limits and improve deliverability
• splitInBatches: Divides large contact lists into smaller groups to process messages efficiently without exceeding API quotas

Prerequisites

• Active Shopify store with API access credentials and abandoned cart tracking enabled
• Rapiwa account with WhatsApp Business API integration and message credits
• Google Sheets account for data logging and optional CRM integration
• Valid WhatsApp Business phone number registered through Meta Business Platform
• Basic understanding of n8n workflow structure and node configuration
• Customer phone numbers stored in Shopify customer profiles with country codes
• API keys and authentication tokens for Shopify, Rapiwa, and Google Sheets services

Difficulty Level

Intermediate: This workflow requires familiarity with API integrations, phone number formatting logic, and WhatsApp messaging platforms. Users should be comfortable configuring authentication credentials and understanding conditional logic flows. Basic coding knowledge helps when customizing the phone number cleaning logic, but pre-built templates reduce complexity.

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