Workflow Templates

Complete security workflow from vulnerability detection to automated remediation, with severity-based routing and full organizational context from Port's catalog. This template provides end-to-end lifecycle management including automatic Jira ticket creation with appropriate priority, AI-powered remediation planning, and Claude Code-triggered fixes for critical vulnerabilities. The full guide is available here. How it works The n8n workflow orchestrates the following steps: Webhook trigger**: Receives vulnerability alerts from security scanners (Snyk, Wiz, SonarQube, etc.) via POST request. Port context enrichment**: Uses Port's n8n node to query your software catalog for service metadata, ownership, environment, SLA requirements, and dependencies related to the vulnerability. AI remediation planning**: OpenAI analyzes the vulnerability with Port context and generates a remediation plan, determining if automated fixing is possible. Severity-based routing**: Routes vulnerabilities through different paths based on severity level: Critical: Jira ticket (Highest priority) → Check if auto-fixable → Trigger Claude Code fix → Slack alert with fix status High: Jira ticket (High priority) → Slack notification to team channel Medium/Low: Jira ticket only for tracking Jira integration**: Creates tickets with full context including vulnerability details, affected service information from Port, and AI-generated remediation steps. Claude Code remediation**: For auto-fixable critical vulnerabilities, triggers Claude Code via Port action to create a pull request with the security patch, referencing the Jira ticket. Slack notifications**: Sends contextual alerts to the appropriate team channel (retrieved from Port) with Jira ticket reference and remediation status. Prerequisites You have a Port account and have completed the onboarding process. Services and repositories are cataloged in Port with ownership information. Your security scanner (Snyk, Wiz, SonarQube) can send webhooks. You have a working n8n instance (Cloud or self-hosted) with Port's n8n custom node installed. Jira Cloud account with appropriate project permissions. Slack workspace with bot permissions to post messages. OpenAI API key for remediation planning. Setup Register for free on Port.io if you haven't already. Create the Context Retriever Agent in Port following the guide. Import the workflow and configure credentials (Port, Jira, Slack, OpenAI, Bearer Auth). Select your Jira project in each Jira node (Critical, High, Medium/Low). Update default-organization/repository with your default repository for Claude Code fixes. Point your security scanner webhook to the workflow URL. Test with a sample vulnerability payload. ⚠️ This template is intended for Self-Hosted instances only.

There's a clear need for an easier way to manage attendee photos from live events, as current processes for collecting, sharing, and categorizing them are inefficient. n8n can indeed help to solve this challenge by providing the data input interface via its forms and orchestrate AI-powered classification of images using AI nodes. However, in some cases - say you run regular events or with high attendee counts - the volume of photos may result in unsustainably high inference fees (token usage based billing) which could make the project unviable. To work around this, Featherless.ai is an AI/LLM inference service which is subscription-based and provides unlimited tokens instead. This means costs are essentially capped for AI usage offering greater control and confidence on AI project budgets. Check out the final result here: https://docs.google.com/spreadsheets/d/1TpXQyhUq6tB8MLJ3maeWwswjut9wERZ8pSk_3kKhc58/edit?usp=sharing How it works A form trigger is used share a form interface to guests to upload their photos from their device. The photos are in one branch, are optimised in size before sending to a vision-capable LLM to classify and categorise against a set list of tags. The model inference service is provided by Featherless and takes advantage of their unlimited token usage subscription plan. The photos in another branch are copied into Google Drive for later reference. Once both branches are complete, the classification results and Google Drive link are appended to a Google Sheets table allowing for quick sorting and filtering of all photos. How to use Use this workflow to gain an incredible productivity boost for social media work. When all photos are organised and filter-ready, editors spend a fraction of the time to get community posts ready and delivered. Sharing the completed Google sheet with attendees helps them to better share memories within their own social circles. Requirements FeatherLess.ai) account for Open Source Multimodal LLMs and unlimited token usage. Google Drive for file storage Google Sheet for organising photos into categories Customising this workflow Feel free to refine the form with custom styles to match your branding. Swap out Google services with equivalents to match your own environment. eg. Sharepoint and Excel.

This workflow automatically creates daily backups of all n8n workflows and stores them in Google Drive, using the n8n API to export workflows and a scheduled retention policy to keep storage organized. The automation runs in two stages: backup and cleanup. Daily Backup Process A Schedule Trigger runs at a defined time each day. The workflow creates a folder in Google Drive using the current date. It calls the n8n API to retrieve the list of all workflows. Each workflow is processed individually and converted into a .json file. The files are uploaded to the daily backup folder in Google Drive. This ensures that every workflow is safely stored and versioned by date. Automatic Cleanup A second scheduled process maintains storage hygiene: The workflow lists all backup folders in the Google Drive root directory. It checks the folder creation date. Any folder older than the defined retention period (default 15 days) is automatically deleted. This prevents unnecessary storage usage while keeping recent backups easily accessible. Key Features Automated daily workflow backups Uses n8n API to export workflows Files stored in Google Drive Automatic retention cleanup Fully documented with sticky notes inside the workflow Uses secure credentials (no hardcoded API keys) Setup Configuration takes only a few minutes: Connect a Google Drive OAuth credential Define the Google Drive root folder ID for backups Configure n8n API credentials securely Adjust: Backup schedule Retention period (default 15 days) Once configured, the workflow will run automatically, creating daily backups and removing old ones without manual intervention.

Use this template if you’re collecting leads in Google Sheets manually or automatically and need to send them emails daily using any personal or professional email provider. It’s simple yet effective. I’ve kept it easy so that anyone without technical or coding knowledge can still automate their emails and achieve excellent ROI. Setting up the workflow takes only 15 minutes. How it works: We connect Google Sheets with n8n to automatically fetch lead data. Google Sheets is used because it’s easy and widely accessible. Then, n8n sends emails daily at your scheduled times to the respective email addresses, using the subject lines and body text you've configured. It also verifies emails before sending. It checks email availability, deliverability, and updates the Google Sheet/CRM with the respective fields. Requirements: A Google Sheet/Excel/CRM tools with leads (A sample Google Sheet link is provided in the template) A working email account with SMTP information (SMTP info for the top 10 email providers is provided in the template) API key from any email verification tool (We use the Hunter API key in our use case. You can find the link in the template.) Setup Steps: You need a Google Sheet where you're collecting leads. You can replace Google Sheets with your CRM tool. Connect it using your credentials. Replace the manual trigger with a scheduled trigger to automate emails at your preferred time. Replace the email verification tool/Hunter API with your own API key. Add your SMTP credentials to connect the template with your preferred email provider. Using SMTP, you can send emails through Gmail, Outlook, Zoho, or any similar provider. This makes sending emails simple and cost-efficient. Note: SMTP, which stands for Simple Mail Transfer Protocol, is a communication protocol used to send email messages between mail servers. After sending the email, we update the Google Sheet with “Sent”; hence, the email is not sent again the next day.

This workflow automates the process of creating cloned voices in ElevenLabs using audio extracted from YouTube videos. It processes a list of video URLs from Google Sheets, converts them to audio, submits them to ElevenLabs for voice cloning*, and records the generated voice IDs back to the spreadsheet. *ONLY FOR STARTER, CREATOR, PRO PLAN Important Considerations for Best Results: For optimal voice cloning quality with ElevenLabs, carefully select your source YouTube videos: Duration**: Choose videos that are sufficiently long (preferably 1-5 minutes of clear speech) to provide enough audio data for accurate voice modeling. Audio Quality**: Select videos with high-quality audio, minimal background noise, and clear vocal recording. Single Speaker: Use videos featuring only **one primary speaker. Multiple voices in the same audio will confuse the cloning algorithm and produce poor results. Consistent Voice**: Ensure the speaker maintains a consistent tone and speaking style throughout the clip for the most faithful reproduction. Key Features 1. ✅ Fully Automated Voice Creation Workflow No manual downloading, converting, or uploading is required. Just paste the YouTube link and voice name into the sheet—everything else happens automatically. 2. ✅ Seamless Audio Extraction Using RapidAPI ensures: High success rate in extracting audio Support for virtually any YouTube video Consistent output format required by ElevenLabs 3. ✅ Hands-Off ElevenLabs Voice Creation The workflow handles all the steps required by the ElevenLabs API, including: Uploading binary audio Naming voices Capturing and storing the resulting voice ID This is much faster than the manual method inside the ElevenLabs dashboard. 4. ✅ Centralized, Reusable Setup Once the API keys are added: The same workflow can be reused indefinitely Users don’t need technical skills Updating only requires editing the sheet How it works: Data Retrieval: The workflow starts by fetching data from a Google Sheets spreadsheet that contains YouTube video URLs in the "YOUTUBE VIDEO" column and desired voice names in the "VOICE NAME" column. It specifically targets rows where the "ELEVENLABS VOICE ID" field is empty, ensuring only unprocessed videos are handled. Video Processing Pipeline: Video ID Extraction: Each YouTube URL is parsed to extract the unique video identifier using a regular expression. Audio Conversion: The video ID is sent to the RapidAPI "YouTube MP3 2025" service, which converts the YouTube video to an audio file (M4A format). Audio Download: The resulting audio file is downloaded locally for processing. Voice Creation: The downloaded audio file is submitted to ElevenLabs API via a POST request to the /v1/voices/add endpoint. This creates a new voice clone based on the audio sample. The voice name is currently hardcoded as "Teresa Mannino" in the workflow but should be dynamically configured to use the value from the "VOICE NAME" spreadsheet column. Data Update: The workflow captures the voice_id returned by ElevenLabs and writes it back to the corresponding row in the Google Sheets spreadsheet in the "ELEVENLABS VOICE ID" column, completing the processing cycle for that video. Set up steps: Prepare the Data Sheet: Duplicate the provided Google Sheets template. Fill in the "YOUTUBE VIDEO" column with YouTube URLs and the "VOICE NAME" column with your desired names for the cloned voices. Ensure your videos meet the quality criteria mentioned above. Configure APIs: RapidAPI: Sign up for a free trial API key from the "YouTube MP3 2025" service on RapidAPI. Enter this key into the x-rapidapi-key header field in the "From video to audio" node. ElevenLabs: Generate an API key from your ElevenLabs account. Configure the "Create voice" node's HTTP Header Authentication with the name xi-api-key and your ElevenLabs API key as the value. Optional Customization: Modify the "Create voice" node to use the dynamic voice name from your spreadsheet instead of the hardcoded "Teresa Mannino" value for more flexible operation. Execute: Run the workflow. It will automatically process each qualifying row, create voices in ElevenLabs, and populate the spreadsheet with the new Voice IDs. Monitor the workflow execution to ensure successful processing of each video. 👉 Subscribe to my new YouTube channel. Here I’ll share videos and Shorts with practical tutorials and FREE templates for n8n. Need help customizing? Contact me for consulting and support or add me on Linkedin.

This n8n workflow is a sophisticated B2B Lead Generation Scraper. It automates the entire journey from discovering businesses on Google Maps to extracting, scoring, and saving high-quality contact emails. Here is a breakdown of the workflow stages: Stage 1: Google Maps Search & Pagination The workflow starts with a list of search queries (e.g., "Dentist New York"). Looping: It processes each query one by one. Smart Pagination: Google Maps usually limits results per page. This workflow detects the nextPageToken and automatically re-calls the API until all available businesses for that query are collected. Filtering: It immediately filters out closed businesses, keeping only those marked as "OPERATIONAL". Stage 2: Deep Web Scraping For every business found with a website, the workflow performs a two-step crawl: Homepage Fetch: It visits the main URL to find immediate contact info. Contact Page Discovery: A code node scans the homepage for links containing keywords like "Contact", "About", "Team", or "Impressum". It then visits these specific sub-pages to find hidden emails. Stage 3: Email Quality Control & Scoring This is the most advanced part of the logic. Instead of just grabbing any email, it uses a Scoring System to rank them: The Filter: It removes technical or junk emails (e.g., sentry@, noreply@, or image files disguised as emails). The Scorecard: +30 Points: Domain match (e.g., info@company.com matches www.company.com). +20 Points: Personal touch (detects dots or names like john.doe@). -40 Points: Generic prefixes (penalizes info@, admin@, sales@). -25 Points: Free providers (penalizes @gmail.com, @yahoo.com). Selection: It sorts all found emails by score and keeps only the top-ranked email for each business. Stage 4: Final Output Deduplication: It ensures no duplicate businesses are added to your list, even if they appeared in multiple search queries. Data Storage: The final, cleaned data—including Business Name, Address, Phone, Website, and the Best Email—is appended to a Google Sheet.

Monitor expiring EntraID application secrets and notify responsible Stay ahead of credential expirations by automatically detecting Entra ID application client secrets and certificates that are about to expire, and sending a neatly formatted email report. What this workflow solves Expired client secrets and certificates are a common cause of unexpected outages and failed integrations. Manually checking expiration dates across many Entra ID applications is tedious and easy to miss. This workflow automates the discovery and reporting of credentials that will expire within a configurable time window. Key features Fetches all Microsoft Entra ID applications along with: Client secrets (passwordCredentials) Certificates (keyCredentials) Splits credentials into individual entries for easier processing Filters credentials expiring within the next N days (configurable) Normalizes results into a consistent structure including: Application name App ID Credential type (Client Secret / Certificate) Credential name + ID Days remaining until expiration Generates an HTML table report, sorted by application name Sends an email only when expiring items are found (otherwise does nothing) How it works Fetches all Entra ID applications and their credential metadata via Microsoft Graph Separates client secrets and certificates into individual entries Filters entries that expire within the configured time window Builds a normalized list of expiring items with days remaining Emails an HTML table report (only if results exist) Setup requirements Microsoft Entra ID app registration* with Microsoft Graph *Application permissions**: Application.Read.All In n8n: Create Microsoft Graph OAuth2 credentials (Client Credentials flow recommended) Assign those credentials to the Get EntraID Applications and Secrets HTTP Request node Update the Set Variables node: notificationEmail: where to send the report daysBeforeExpiry: alert window in days (e.g., 14) Notes The email table highlights soon-to-expire credentials more prominently (based on remaining days). For automation, replace the manual trigger with a Schedule Trigger (e.g., daily/weekly). The workflow accesses metadata only (names/IDs/expiry), not secret values.

This n8n template from Intuz provides a complete solution to automate your order creation process. It seamlessly syncs order data from an Airtable base directly to your Shopify store, creates the official order, and automatically sends a beautiful confirmation email to the customer, closing the loop by updating the status in Airtable. Who's this workflow for? E-commerce Managers Operations Teams Businesses with Custom Order Processes (e.g., B2B, phone orders, quotes) Shopify Store Owners using Airtable as a CRM How it works 1. Triggered from Airtable: The workflow starts instantly when an Airtable Automation sends a signal via a webhook. This happens when you mark an order as ready to be processed in your Airtable base. 2. Fetch Order Details: n8n receives the record ID from Airtable and fetches the complete order details, including customer information and the specific line items for that order. 3. Create Order in Shopify: All the gathered information is used to create a new, official order directly in your Shopify store. 4. Send Confirmation Email: Once the order is successfully created in Shopify, a professionally formatted HTML order confirmation email is sent to the customer via Gmail. 5. Update Airtable Status: Finally, the workflow updates the original order record in Airtable, marking its status as "Done" to prevent duplicate processing and keep your records in sync. Key Requirements to Use This Template 1. n8n Instance: An active n8n account (Cloud or self-hosted). 2. Airtable Base: An Airtable base on a "Pro" plan or higher (required for Airtable Automations). It should contain tables for Orders and Order Line Items. 3. Shopify Store: An active Shopify store with API access permissions. 4. Gmail Account: A Gmail account to send confirmation emails. Setup Instructions 1. Configure the n8n Workflow: Webhook Node: Activate the workflow to get the Production URL from the "Webhook" node. Copy this URL. Airtable Nodes: In the Get a record and Update record nodes, connect your Airtable credentials and select the correct Base and Table IDs. Shopify Node: In the Create an order node, connect your Shopify store using OAuth2 credentials. Gmail Node: In the Send a message node, connect your Gmail account. 2. Set Up the Airtable Automation (Crucial Step): Go to your Airtable base and click on "Automations". Create a new automation. For the trigger, select "When a record meets conditions". Choose your Orders table and set a condition that makes sense for you (e.g., When "Shopify Ordered" is "Pending"). For the action, choose "Run a script". Paste the code below into the script editor: JavaScript const inputConfig = input.config(); const recordId = inputConfig.recordId; const webhookUrl = 'PASTE_YOUR_N8N_PRODUCTION_URL_HERE'; await fetch(webhookUrl, { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ recordId: recordId }), }); ReplacePASTE_YOUR_N8N_PRODUCTION_URL_HERE with the Production URL you copied from n8n. Add an input variable to the script named recordId and set its value to the "Airtable record ID" from the trigger step. Test the script and turn your Airtable Automation ON. Connect with us Website: https://www.intuz.com/services Email: getstarted@intuz.com LinkedIn: https://www.linkedin.com/company/intuz Get Started: https://n8n.partnerlinks.io/intuz For Custom Workflow Automation Click here- Get Started

Schedule appointments from phone calls with AI using Twilio and ElevenLabs This n8n template creates an intelligent phone receptionist that handles incoming calls, answers FAQs, and schedules appointments to Google Calendar. The system uses Twilio for phone handling, ElevenLabs for voice AI and basic conversations, and n8n for complex scheduling logic—keeping responses snappy by only invoking the workflow when calendar operations are needed. Who's it for Businesses that need automated phone scheduling: service companies, clinics, consultants, or any business that takes appointments by phone. Perfect for reducing administrative overhead while maintaining a professional caller experience. Good to know Redis memory is essential—without it, the AI must reparse entire conversations causing severe lag in voice responses Claude 3.5 Sonnet is recommended for best scheduling results Typical response times: ElevenLabs-only responses <1s, n8n tool calls 2-4s All placeholder values must be customized or scheduling will fail How it works Twilio receives incoming calls and forwards to ElevenLabs voice AI ElevenLabs handles casual conversation and FAQ responses instantly When calendar operations are needed, ElevenLabs calls your n8n webhook n8n checks Google Calendar availability using your business rules Claude AI agent processes the request, collects required information, and schedules appointments Redis maintains conversation context across the call Calendar invites are automatically sent to customers How to set up Connect Twilio to ElevenLabs: In Twilio Console, set your phone number webhook to your ElevenLabs agent URL Configure ElevenLabs tools: Add "Client Tools" in ElevenLabs that point to your n8n webhook for checking availability, creating appointments, and updating appointments Set n8n webhook path: Replace REPLACE ME in the "Webhook: Receive User Request" node with a secure endpoint (e.g., /elevenlabs-voice-scheduler) Configure Google Calendar: Replace all REPLACE ME instances with your Calendar ID in the three calendar nodes (Check Availability, Create Appointment, Update Event) Set up Redis: Configure connection details in the "Redis Chat Memory" node Customize scheduling prompt: In the "Voice AI Agent" node, replace all bracketed placeholders with your business details: [TIMEZONE], [START_TIME], [END_TIME], [OPERATING_DAYS], [BLOCKED_DAYS] [MINIMUM_LEAD_TIME], [APPOINTMENT_DURATION], [SERVICE_TYPE] [REQUIRED_FIELDS], [REQUIRED_NOTES_FIELDS] Test: Make a test call to verify availability checking, information collection, and appointment creation Requirements Twilio account with phone number ElevenLabs Conversational AI account Google Calendar with OAuth2 credentials Redis instance (for session management) Anthropic API key (for Claude AI)

How it works This template is an end-to-end demo of an in-house AI agent that can answer a wide range of questions by retrieving information from the Uniconta ERP system. For example users can ask questions related to products, stock, accounting or any other type of information contained in Uniconta. Peliqan.io is used as a "cache" of all Uniconta data. Peliqan uses one-click ELT to sync all data from Uniconta to the built-in data warehouse, allowing for fast & accurate queries. The AI agent uses Text-to-SQL to answer questions. Text-to-SQL is performed via the Peliqan node, added as a tool to the AI Agent. The question of the user - in natural language - is converted to an SQL query by the AI Agent. The query is executed by Peliqan.io on the source Uniconta data and the result is interpreted by the AI Agent. Preconditions You signed up for a Peliqan.io free trial account You have a Uniconta ERP system Set up steps Sign up for a free trial on peliqan.io Add Uniconta as a connection in Peliqan (using an API key from Uniconta) Copy your Peliqan API key (in Peliqan go to Settings > API key) and use it in n8n to add a Peliqan connection Select your data warehouse in the Peliqan node "Execute an SQL query via Peliqan" in the drop-down field "Data warehouse name or id" Optional: run the template script in Peliqan that outputs your specific Uniconta datamodel (tables & columns). Copy your datamodel and paste it in the System Message of the AI Agent (replace the standard Uniconta model already present in this workflow) Visit peliqan.io/n8n for more information. Need help ? Contact Peliqan at support@peliqan.io Disclaimer: This template contains a community node and therefore only works for n8n self-hosted users.

Overview Businesses and freelancers often struggle with the tedious task of manually processing receipts for expense tracking and tax purposes. This workflow automates the entire receipt processing pipeline, extracting detailed information from receipts (including scanned images, photos, PDFs, JPGs, and PNGs) and intelligently categorizing them for tax deductions. What You Can Do Automatically process receipts from various formats (PDFs, JPGs, PNGs, scanned images) Extract detailed expense information with OCR technology Intelligently categorize expenses for tax deductions Maintain compliance with accounting standards and tax regulations Track expenses efficiently throughout the year Who It's For Accountants, small business owners, freelancers, finance teams, and individual professionals who need to process large volumes of receipts efficiently for expense tracking and tax preparation. The Problem It Solves Manual receipt processing is time-consuming and error-prone, especially during tax season. People struggle to organize receipts, extract accurate data from various formats, and categorize expenses properly for tax deductions. This template automates the entire process while ensuring compliance with accounting standards and tax regulations. Setup Instructions: Configure Google Drive credentials for receipt storage access Install the PDF Vector community node from the n8n marketplace Configure PDF Vector API credentials Set up tax category definitions based on your jurisdiction Configure accounting software integration (QuickBooks, Xero, etc.) Set up validation rules for expense categories Configure reporting and export formats Key Features: Automatic retrieval of receipts from Google Drive folders OCR support for photos and scanned receipts Intelligent tax category assignment based on merchant and expense type Multi-currency support for international transactions Automatic detection of meal expenses with deduction percentages Financial validation to catch calculation errors Audit trail maintenance for compliance Integration with popular accounting software Customization Options: Define custom tax categories specific to your business type Set up automated rules for recurring merchants Configure expense approval workflows for team members Add mileage tracking integration for travel expenses Set up automated notifications for high-value expenses Customize export formats for different accounting systems Add multi-language support for international receipts Implementation Details: The workflow uses advanced OCR technology to extract information from various receipt formats, including handwritten receipts and low-quality scans. It applies intelligent categorization rules based on merchant type, expense amount, and business context. The system includes built-in validation to ensure data accuracy and tax compliance. Note: This workflow uses the PDF Vector community node. Make sure to install it from the n8n community nodes collection before using this template.

WooCommerce Daily Sales & Revenue Spike Monitor → Slack Alert This workflow automatically checks your WooCommerce store’s last 24 hours of revenue, top-selling products, and cancelled orders on a daily schedule. It sends Slack notifications when sales cross a defined threshold or provides a detailed status update—including cancellation impact—if the target hasn’t been met, helping teams react quickly without manual reporting. 🚀 Quick Implementation Steps Set up the Schedule Trigger to run daily Connect WooCommerce and fetch recent orders Filter paid and cancelled orders separately Filter both datasets to the last 24 hours Calculate revenue, top products, and cancellation impact Merge and format sales and cancellation data Compare revenue with a configurable threshold Send enriched Slack alerts with sales and cancellation insights What It Does This workflow serves as a daily sales and revenue health monitoring assistant for your WooCommerce store. It runs automatically on a schedule and collects recent order data from WooCommerce via API. Only paid orders (Completed / Processing) are considered for revenue calculations. Cancelled orders are processed in a separate branch to track revenue loss. Orders created within the last 24 hours are filtered for both paid and cancelled orders. The workflow calculates total revenue, order count, average order value, and top-selling products. It also calculates cancelled order count and cancelled revenue to highlight potential revenue leakage. Sales and cancellation data are merged into a single structured object. An IF node checks whether revenue exceeds a predefined threshold. If the threshold is crossed, a Slack Sales Spike Alert is sent with cancellation context. If the threshold is not reached, a Slack Status / Pending Alert is sent showing progress, top products, and cancellation impact—keeping the team informed without noise. Who’s It For Business owners monitoring daily sales and revenue health Sales and marketing teams tracking revenue spikes and losses E-commerce managers using WooCommerce Operations teams monitoring cancellations and fulfillment risks Non-technical users who want actionable insights without dashboards Requirements to Use This Workflow An active WooCommerce store WooCommerce REST API credentials** An n8n instance (cloud or self-hosted) A Slack workspace with incoming webhook or Slack credentials Permission to read WooCommerce orders and post Slack messages How It Works & Set Up Schedule Trigger Configure the Schedule Trigger to run once per day at your preferred time. Fetch Orders from WooCommerce Use the WooCommerce node to retrieve recent orders from your store. Filter Paid Orders Keep only orders with status Completed or Processing. Filter Last 24 Hours Orders A Code node filters paid orders created within the last 24 hours. Calculate Top Products A Code node aggregates product quantities sold in the last 24 hours. Calculate Total Revenue A Code node calculates total revenue, order count, and average order value. Fetch & Process Cancelled Orders A separate WooCommerce branch fetches orders with status Cancelled. Cancelled orders are filtered to the last 24 hours using a Code node. A Code node calculates cancelled order count and cancelled revenue. Merge & Format Sales Data A Merge node combines sales metrics and cancellation metrics. A Code node formats all results into a single JSON object for Slack. Threshold Check An IF node compares total revenue against a fixed threshold. Send Slack Alerts TRUE path: Sends a **Sales Spike Alert including revenue, top products, and cancellation impact. FALSE path: Sends a **Status / Pending Alert showing current performance, top products, and cancellation insights. Activate Workflow Test once and activate the workflow for daily monitoring. How To Customize Nodes Threshold Value**: Update the IF node condition to match your business target Schedule Time**: Change the Schedule Trigger execution time Slack Channels**: Update Slack nodes to post in your desired channels Order Status Logic**: Adjust filters for paid or cancelled orders if needed Time Window**: Modify the 24-hour logic to 12 hours, 48 hours, or weekly Cancellation Sensitivity**: Add conditions to alert on high cancellation volume or revenue impact Add-ons (Optional Enhancements) Add cancellation rate (%) and net revenue calculations Trigger alerts when cancellation revenue exceeds a defined percentage Store daily sales and cancellation history in Google Sheets or a database Add day-over-day or week-over-week comparisons Send alerts to Microsoft Teams or Email Attach a CSV report with order and cancellation details Use Case Examples Detect viral product sales quickly Monitor flash sale performance Identify revenue loss due to cancellations Alert leadership on high-revenue or high-risk days Track campaign-driven sales spikes and drop-offs Support inventory, operations, and customer experience planning > Many more business scenarios can be addressed based on your store’s needs. Troubleshooting Guide | Issue | Possible Cause | Solution | | ---------------------------------- | -------------------------------- | ---------------------------------------- | | No Slack alert received | Revenue did not exceed threshold | Check threshold or test with lower value | | Workflow fails | WooCommerce API error | Verify API credentials and permissions | | Revenue or cancellation shows zero | Orders filtered out | Validate order status and date logic | | Slack message not sent | Wrong Slack credentials | Reconnect Slack node | | Orders missing | Timezone mismatch | Align WooCommerce and n8n timezone | Need Help? Need help setting up this workflow or customizing it further? Our n8n workflow development team at WeblineIndia can assist you with implementation, add-ons, performance optimization and building similar n8n automations tailored to your business needs. 👉 Contact WeblineIndia today to automate smarter and scale faster.