Workflow Templates

Why You Need This Right Now 💡 Stop the panic attacks. We've all been there - accidentally deleted a workflow that took hours to build, or worse, corrupted your entire automation setup. This workflow is your safety net. Save your weekends. Instead of spending hours recreating lost work, get back to what matters. One setup protects everything, automatically. Sleep better at night. Your workflows are safely stored in two places with full version history. If something breaks, you're back online in minutes, not days. Perfect For These Situations ⚡ ✅ Business owners running critical automations ✅ Agencies managing client workflows ✅ Teams who need audit trails ✅ Anyone who values their time and sanity How It Actually Works 🔧 Think of it like having a personal assistant who: Checks your workflows twice daily (you can change this) Creates organized backups with timestamps Stores them safely in Google Drive AND GitHub Tells you it's done via Telegram or Discord Keeps everything tidy with smart folder organization The result? A timestamped folder in your Google Drive and organized files in your GitHub repo. Everything is searchable, restorable, and audit-ready. Quick 5-Minute Setup 🚀 Import this workflow to your n8n Connect your accounts (Google Drive, GitHub, optional notifications) Set your preferences (which folder, which repo, how often) Test it once to make sure everything works Relax knowing your workflows are protected What You'll Need 📋 Your n8n instance (obviously!) Google Drive account (free works fine) GitHub account (free works too) 5 minutes of setup time Optional: Telegram or Discord for notifications Pro Tips for Power Users 🧠 Want to level up? Here are some ideas: Add encryption** for sensitive workflows Create restore workflows** for one-click recovery Set up pull requests** for team review of changes Customize schedules** based on your workflow update frequency Created by: khaisa Studio - Automation experts who actually use this stuff daily Tags: backup, automation, n8n, google-drive, github, workflow-protection, business-continuity Questions? Get in touch - I'm always happy to help fellow automation enthusiasts! Remember: The best backup is the one you set up before you need it. Your future self will thank you!

How it works This workflow runs every morning to collect news from multiple RSS feeds across global, business, finance, and tech categories. It processes and filters the most recent articles, then uses an AI model to select the most relevant global stories. The selected news is formatted into a clean digest. Finally, the digest is automatically delivered to a Slack channel. Step-by-step Trigger and setup feeds** Schedule Trigger – Runs the workflow daily at a fixed time. Define News Categories – Stores all RSS feed URLs in one place. Prepare RSS Feed List – Converts feed data into iterable items. Fetch and process articles** Loop Through RSS Feeds – Iterates through each RSS source. Fetch RSS Articles – Pulls articles from each feed. Filter Latest 10 Articles – Sorts and keeps the most recent items. Merge All RSS Articles – Combines all articles into one dataset. AI selection and delivery** AI Select Top Global News – Uses AI to pick the most important stories. Groq Chat Model – Provides the language model for analysis. Format News For Slack Message – Structures AI output into clean messages. (Sub-node) JSON Extraction Logic – Parses AI response into usable article data. Post News Digest to Slack – Sends the final formatted digest to Slack. Why use this? Automates end-to-end news aggregation and summarization Filters noise and highlights only high-impact global stories Keeps teams informed directly within Slack Reduces manual effort in tracking multiple news sources Easily scalable by adding more RSS feeds or categories

Daily WooCommerce Sales Snapshot to Slack with Google Sheets Logging This workflow automatically collects WooCommerce sales data every day, calculates key sales metrics, sends a clean summary to Slack and logs the same data into Google Sheets for historical tracking. It helps teams stay informed about daily performance without manually checking dashboards or reports. Quick Implementation Steps (Get Started Fast) Import the workflow JSON into n8n. Connect your WooCommerce, Slack and Google Sheets credentials. Verify the Slack channel and Google Sheet selection. Activate the workflow. Receive daily sales updates automatically. What It Does This workflow runs on a daily schedule and fetches all recent orders from a WooCommerce store. It filters the orders to include only paid ones (Processing and Completed) and further narrows them down to those created within the last 24 hours. Using separate Code nodes, the workflow calculates essential sales metrics such as total revenue, number of orders, average order value (AOV) and the top-selling products. These metrics are merged into a single structured object for consistent downstream use. Finally, the workflow sends a formatted sales summary to a Slack channel for quick visibility and appends the same data as a row in Google Sheets. This creates a reliable daily log that can be used for trend analysis and reporting. Who’s It For WooCommerce store owners Sales and operations teams Marketing teams tracking daily performance Business managers who prefer Slack updates Analysts maintaining sales history in spreadsheets Requirements to Use This Workflow Active WooCommerce store with API access n8n instance (self-hosted or cloud) Slack workspace with permission to post messages Google Sheets document for logging data Valid credentials configured in n8n for: WooCommerce Slack Google Sheets How It Works A Schedule Trigger runs the workflow once per day. Orders are fetched from WooCommerce. Only paid orders (Processing / Completed) are considered. Orders from the last 24 hours are filtered. Sales metrics are calculated: Total Revenue Order Count Average Order Value (AOV) Top Selling Products Metrics are merged into a single object. A formatted summary is: Sent to Slack Appended or updated in Google Sheets How To Set Up Configure the Schedule Trigger time. Add WooCommerce credentials. Review paid order filtering logic. Select Slack channel. Select Google Sheet and worksheet. Test the workflow. Activate it. How To Customize Nodes Change schedule time in the Schedule Trigger. Modify order statuses in the Filter Paid Orders node. Adjust the 24-hour window in the Code node. Increase or decrease top products count. Customize Slack message formatting. Add or remove Google Sheets columns. Add-ons (Optional Enhancements) Weekly or monthly summaries Revenue comparison (day-over-day / week-over-week) Revenue threshold alerts Multiple Slack channels Dashboard integrations from Google Sheets Use Case Examples Daily sales snapshot for store owners Morning updates for sales teams Automated sales logging for finance teams Performance tracking without dashboards Remote team visibility via Slack Many more variations are possible depending on business needs. Troubleshooting Guide | Issue | Possible Cause | Solution | |------|---------------|----------| | Slack message not received | Slack credentials or channel issue | Verify Slack API and channel | | Google Sheet not updating | Incorrect sheet or mapping | Recheck sheet selection | | Orders missing | Order status filter too strict | Update filter conditions | | Revenue incorrect | Time filter issue | Verify last 24-hour logic | | Workflow not running | Workflow inactive | Activate workflow | Need Help? If you need help setting up, customizing or extending this workflow, our n8n automation experts at WeblineIndia can assist. We specialize in: n8n automation workflows Business process automation Custom integrations and reporting Contact WeblineIndia to build reliable and scalable automation tailored to your business.

Tags: Logistics, Supply Chain, OTIF, KPI Tracking, Performance Management, AI Analysis, Notion Context Hi! I'm Samir, Supply Chain Engineer, Data Scientist based in Paris, and founder of LogiGreen. > Let's use AI with n8n to automate supply chain performance tracking! Tracking On-Time In-Full (OTIF) delivery performance is critical for retail logistics, but manually compiling data, computing KPIs, and writing analysis reports is time-consuming and error-prone. This workflow automates the entire process: collecting shipment data, aggregating weekly KPIs, generating AI powered performance analyses, and pushing everything into a Notion dashboard. For business inquiries, you can find me on LinkedIn Demo of the workflow The workflow collects shipment records from your TMS and WMS, then aggregates them by week. An AI Agent analyses each week's performance and generates summary cards in Notion. Weekly OTIF data is automatically pushed to a Notion database for tracking and visualisation. Who is this template for? This template is ideal for logistics and supply chain teams looking to automate KPI reporting: Supply chain managers** tracking delivery performance across carriers and warehouses Logistics analysts** who need automated weekly OTIF scorecards Operations teams** looking to leverage AI for performance insights Tutorial A complete tutorial (with explanations of every node) is available on YouTube: What does this workflow do? This automation uses Notion databases and OpenAI AI Agents to build a complete OTIF scorecard: The workflow is triggered manually (or on a schedule). Shipment data is collected from your TMS and WMS systems. Records are aggregated by week, computing On-Time rate, In-Full rate, and OTIF rate. An AI Agent analyses each week's performance and identifies trends, issues, and recommendations. Weekly KPI rows are pushed to the Daily OTIF Summary database in Notion. Per-week AI analysis cards are created in the AI Generated Analysis database. A second AI Agent generates a global performance summary across all weeks. The global summary card is updated in Notion with the overall analysis. Next Steps Before running the workflow, follow the sticky notes and configure: Connect your Notion API credentials and update the database IDs in all Notion nodes Add your OpenAI API Key to the AI Agent nodes Update the "Collect Shipments from TMS & WMS" node with your actual data source (API, Google Sheets, or database) Adjust the AI prompts to match your specific KPI thresholds and business context Set up the Notion template with the two required databases: "Daily OTIF Summary" and "AI Generated Analysis" Duplicate the Notion template to your workspace before connecting the workflow (Optional) Change the trigger from manual to a scheduled cron for automated weekly reporting Submitted: 8 March 2026 Template designed with n8n version 2.10.12

Landing Page Lead Intake via Webhook to Zoho CRM, Jira Task & Slack Alerts This n8n workflow captures lead data from a landing-page webhook, validates required fields and then processes the lead by creating a Zoho CRM Lead, generating a Jira Task and notifying a Slack channel. If required fields are missing, the workflow skips CRM + Jira creation and instead notifies Slack with available lead details. ⚡ Quick Start: 5-Step Fast Implementation Import this workflow JSON into n8n. Configure credentials: Zoho CRM OAuth2, Jira Cloud, Slack OAuth2. Copy the webhook URL and connect it to your landing page form. Ensure your form sends: first_name, last_name, company_name, email, phone, title, description, referrer. Activate workflow → send test POST → verify Zoho, Jira & Slack outputs. What It Does This workflow works as an automated lead pipeline. When the landing page sends JSON to the webhook, the workflow checks if last_name and company_name are present. If both fields exist, it proceeds to create a Zoho CRM lead, then generates a Jira task using the same data. A detailed Slack message is then posted with all lead information and the newly created Jira task ID. If any of the required fields are missing, the workflow does not create CRM or Jira entries. Instead, it sends a Slack notification with available details so teams can intervene manually without incorrect CRM data entry. Who’s It For Marketing teams capturing leads from landing pages. Sales teams using CRM and Jira for task tracking. Internal teams who want Slack alerts for new leads. Agencies and startups handling inbound lead flow. Anyone requiring automated lead routing without manual work. Prerequisites n8n instance Zoho CRM OAuth2 credential Jira Software Cloud credential Slack OAuth2 credential A landing page that sends POST JSON payloads Required payload fields: first_name last_name company_name email phone title description referrer How to Use & Setup Step 1: Import Workflow Go to n8n → Workflows → Import workflow JSON. Step 2: Configure Credentials Add your credentials in: Zoho CRM (Create a lead) Jira Software Cloud (Create an issue) Slack (Send a message & Send a message1) Step 3: Connect Webhook Copy the Webhook URL from the Webhook node and configure your landing page to send POST JSON to it. Step 4: Field Validation The If node checks: last_name exists company_name exists If both exist → CRM + Jira + Slack If missing → Slack-only alert Step 5: Test Workflow Send sample JSON using your landing page or Postman. Check Zoho CRM, Jira task creation, and Slack messages. Step 6: Activate Workflow Enable workflow after verification. How To Customize Nodes? Webhook Node Add/remove expected fields Modify payload structure If Node Add more validations Switch to OR logic Zoho CRM Lead Node Add additional fields Modify CRM field mapping Jira Task Node Change project, issue type, priority, assignee Modify description template Slack Nodes Change channel Rewrite notification messages Add Slack formatting Add-ons (Optional Enhancements) Email notification to lead Google Sheets entry logging Duplicate lead detection Lead scoring system CRM sync extensions (Contact, Account, etc.) Use Case Examples Marketing campaign lead automation. Instant Slack alerts for new inbound leads. Customer inquiry → Jira task workflow. Data quality enforcement (avoid CRM pollution). Trigger for larger lead qualification workflow. (And many more possible use cases.) Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|----------------|----------| | Webhook not triggered | Wrong webhook URL or wrong HTTP method | Check URL and ensure POST is used | | Zoho lead not created | Invalid credentials or missing required mapping | Reconnect Zoho credentials and verify fields | | Jira task not created | Wrong project/issue/assignee config | Verify project, issue type & permissions | | Slack message not sent | Token expired or incorrect channel ID | Re-authenticate Slack and confirm channel | | Workflow stops at If node | last_name or company_name missing | Update landing page form to include fields | | Slack message missing values | Wrong field names in payload | Ensure JSON fields match expected structure | Need Help? For assistance with setup, customization or building enhanced automation workflows, our n8n team at WeblineIndia can help you build & optimize your automations. We support: Workflow customization Add-on development Integration with other CRMs or apps Advanced automation logic

Automatically import new user signups from any database, filter by signup date, and enroll users into your Saleshandy email sequence for immediate engagement. Activity is logged to a spreadsheet (e.g., Google Sheets) for tracking and analytics. Fully configurable, no hardcoded values. Prerequisites A database with a users table (fields: id, full_name, email, created_at) Saleshandy account with API key and an active sequence. Spreadsheet (e.g., Google Sheets) with columns: ID, Name, Email, Created_at Configured OAuth/API credentials for each service How It Works Fetches new signups from your database within your desired date range (e.g., daily or weekly). Splits user names and formats user data as needed. Adds each user to your Saleshandy sequence using their name and email. Logs every processed record in your spreadsheet for further tracking and analytics. Runs automatically on your defined schedule (example: daily trigger). Set Up Steps Estimated time: 10–20 minutes Collect your database and Saleshandy access credentials, and spreadsheet info. Edit database node(s) to include your connection and correct date filter. Set your Saleshandy API key and target sequence ID. Enter your spreadsheet link or ID and authenticate as needed. Test the workflow with a small user batch before scheduling it for routine runs. Check sticky notes by each workflow node for details and best practices. Requirements Database connection credentials and access Saleshandy API key and sequence ID Google Sheets (or alternative) setup credentials Customisation Tips Edit the date filter to adjust the range (last day, week, month, or custom) Add error-handling nodes to catch issues with API calls or data Set up notifications (email, Slack, etc.) for process success/failure Rename nodes to reflect your business logic or steps Replace the manual trigger with a webhook or scheduled cron if desired Configure workflow variables for all credentials and IDs—avoid hardcoding

CSO Agent with Sales Team Description Complete AI-powered sales department with a Chief Sales Officer (CSO) agent orchestrating specialized sales team members for comprehensive revenue operations and sales automation. Overview This n8n workflow creates a comprehensive sales department using AI agents. The CSO agent analyzes sales opportunities and delegates tasks to specialized agents for lead generation, copywriting, proposals, objection handling, demos, and follow-up sequences. Features Strategic CSO agent using OpenAI O3 for complex sales strategy and decision-making Six specialized sales agents powered by GPT-4.1-mini for efficient execution Complete sales funnel coverage from lead generation to deal closure Automated proposal and contract generation Objection handling playbooks and closing techniques Demo preparation and presentation materials Follow-up and nurture campaign automation Team Structure CSO Agent**: Strategic sales oversight and team coordination (O3 model) Lead Generation Specialist**: Prospecting, research, qualification, cold outreach Sales Copywriter**: Pitch decks, proposals, sales collateral, persuasive content Proposal & Contract Specialist**: Deal structuring, terms negotiation, contracts Objection Handler**: Sales objections, responses, closing techniques Demo & Presentation Expert**: Demo scripts, presentation materials, call preparation Follow-up & Nurture Specialist**: Sequence campaigns, relationship building How to Use Import the workflow into your n8n instance Configure OpenAI API credentials for all chat models Deploy the webhook for chat interactions Send sales requests via chat (e.g., "Create a complete B2B SaaS sales campaign") The CSO will analyze and delegate to appropriate specialists Receive comprehensive sales deliverables and strategies Use Cases Complete Sales Funnels**: Lead generation → Qualification → Demo → Proposal → Close Account-Based Sales**: Personalized outreach strategies for enterprise accounts Product Launch Sales**: Go-to-market strategy with full sales enablement Objection Playbooks**: Comprehensive responses to common sales objections Demo Optimization**: Compelling presentations tailored to different audiences Follow-up Automation**: Systematic nurturing to prevent lead loss Proposal Generation**: Professional proposals with terms and pricing Sales Training**: Objection handling and closing technique development Requirements n8n instance with LangChain nodes OpenAI API access (O3 for CSO, GPT-4.1-mini for specialists) Webhook capability for chat interactions Optional: Integration with CRM systems (Salesforce, HubSpot, etc.) Cost Optimization O3 model used only for strategic CSO decisions GPT-4.1-mini provides 90% cost reduction for specialist tasks Parallel processing enables simultaneous agent execution Template library reduces redundant content generation Integration Options Connect to CRM systems for lead management Integrate with email platforms for outreach automation Link to proposal and contract management tools Export to sales enablement platforms Performance Metrics Lead qualification accuracy and conversion rates Proposal win rates and deal velocity Objection handling success rates Demo-to-close conversion optimization Follow-up engagement and response rates Contact & Resources Website**: nofluff.online YouTube**: @YaronBeen LinkedIn**: Yaron Been Tags #SalesOps #LeadGeneration #SalesEnablement #RevenueGrowth #SalesAutomation #B2BSales #SalesStrategy #ProposalAutomation #DemoOptimization #SalesAI #n8n #OpenAI #MultiAgentSystem #SalesTech #RevOps #PipelineAutomation

This workflow allows you to create an affiliate, add metadata, and add the affiliate to a program. Tapfiliate node: This node allows you to create a new affiliate in Tapfiliate. Tapfiliate1 node: This node allows you add metadata to the affiliate that you created previously. Based on your use-case, you may or may not require this node. Tapfiliate2 node: This node allows you to add the affiliate that you created previously to a program. Based on your use-case, you might want to replace the Start node with a trigger node that gets you the information of an affiliate.

This workflow uses a WooCommerce trigger that will run when a new customer has been added, It will then add the customer to Mautic. To use this workflow you will need to set the credentials to use for the WooCommerce and Mautic nodes.

This workflow allows you to send daily weather updates via an SMS message using the Plivo node. Cron node: The Cron node will trigger the workflow daily at 9 AM. OpenWeatherMap node: This node will return data about the current weather in Berlin. To get the weather updates for your city, you can enter the name of your city instead. Plivo node: This node will send an SMS with the weather update, which was sent by the previous node.

Lead-Routing-Engine-with-SLA-Auto-Reassignment This repository contains an SLA-based lead routing workflow built in n8n, designed to ensure fast lead response, fair sales distribution, and controlled escalation without relying on a full CRM system. The workflow focuses on routing discipline and operational safety, not feature completeness. What This Workflow Does At a high level, the system: 1) Accepts new leads from a generic intake form 2) Assigns leads to sales reps using round-robin 3) Enforces a response SLA 4) Automatically re-routes uncontacted leads 5) Allows sales to mark leads as CONTACTED via Slack 6) Escalates to a manager once if SLA is repeatedly violated Architecture Overview Core Components 1) n8n 2) Google Sheets 3) Slack Primary Data Stores 1) sales_sheet (list of active sales reps) 2) lead_sheet (lead state and routing history) 3) routing_state_sheet (global routing + escalation flags) End-to-End Flow A) Lead Intake & Normalization 1) New leads enter via Form Trigger 2) Phone numbers are normalized to 62xxxxxxxx (Indonesia International Direct Dialing code) 3) A unique lead_id is generated 4) Lead is initialized with: stage = NEW route_count = 0 B) Initial Assignment (Round Robin) 1) Active sales reps are loaded from sales_sheet 2) Global last_index is read from routing_state_sheet 3) Lead is assigned to the next sales rep in sequence 4) Assignment metadata is stored: assigned sales timestamps route count 5) last_index is updated centrally C) Slack Notification (New Lead) 1) Assigned sales receives a Slack message 2) Message includes a “Mark as CONTACTED” button 3) SLA expectation is clearly communicated (1 hour by default) D) SLA Monitoring (Scheduled) 1) A scheduled trigger runs every hour 2) Workflow scans leads where: stage = NEW SLA window has elapsed since last assignment E) SLA Re-Routing For each qualifying lead: 1) Lead is reassigned to the next sales rep 2) Route count is incremented 3) Timestamps are updated 4) Slack notification is sent to the new assignee This process repeats until the lead is contacted or escalated. F) Controlled Escalation If route_count >= threshold (default: 10): 1) Workflow checks escalation state (escalated_<lead_id>) 2) If not escalated yet: Manager is notified via Slack Escalation flag is written 4) If already escalated: No further action is taken Escalation is one-time per lead. G) Stage Update via Slack (CONTACTED) 1) Sales marks a lead as CONTACTED via Slack button 2) Incoming Slack action is validated: Only assigned sales is allowed Only if current stage is NEW 3) Update is idempotent 4) Unauthorized or stale actions receive Slack feedback Once contacted: 1) SLA routing stops 2) Lead remains stable Safeguards Built In 1) Ownership enforcement (Only the assigned sales rep can update a lead) 2) Idempotent stage transitions (Prevents duplicate or stale Slack actions) 3) One-time escalation (No notification spam) 4) Fail-fast behavior (Missing sales data or malformed payloads halt execution early) Google Sheets Schema sales_sheet | Column | Description | |----------|-----------------| | name | Sales name | | email | Optional | | slack_id | Slack user ID | | active | ON / TRUE | lead_sheet | Column | Description | | -------------- | --------------------- | | lead_id | Unique identifier | | name | Lead name | | phone | Normalized phone | | stage | NEW / CONTACTED / QUALIFIED / CLOSED LOST | | assigned_sales | Current owner | | sales_slack_id | Slack ID | | route_count | Number of re-routes | | created_at | Creation timestamp | | assigned_at | Last assignment | | last_routed_at | Last SLA routing | | contacted_at | When marked contacted | routing_state_sheet | key | value | | ------------------- | ---------------------- | | last_index | Last round-robin index | | escalated_<lead_id> | Escalation timestamp | Limitations (By Design) 1) Google Sheets is not transactional 2) SLA enforcement is time-bucketed, not real-time 3) No concurrency locking across parallel runs 4) Slack is required for interaction 5) This is not a CRM, only a routing engine These constraints are explicit and intentional. When This Design Works Well 1) Small to mid-size teams 2) Human-response SLAs (minutes/hours) 3) Teams needing discipline, not heavy tooling 4) CRM-lite or pre-CRM environments When to Migrate Consider migrating if you need: 1) High-volume ingestion 2) Sub-minute SLA guarantees 3) Strong transactional consistency 4) Advanced analytics or forecasting The routing logic itself is portable to SQL or CRM systems.

🔧 AI-Powered Cold Call Machine 🎯 Purpose The AI-Powered Cold Call Machine is a fully automated workflow designed to generate qualified leads from LinkedIn, evaluate them using AI-based scoring, identify key decision-makers, and generate personalized cold call scripts. All results are saved to a Google Sheet-based CRM. ⚙️ How It Works 1. Initialization Triggered either manually or via schedule. Pulls configuration from a Google Sheet’s Settings tab (e.g., target product, keywords, company size, API key). 2. Company Search on LinkedIn Uses the Ghost Genius API to search for companies based on cleaned, relevant keywords extracted by OpenAI. Handles pagination, up to 1000 companies per batch. 3. Company Filtering Each company goes through: Data enrichment via Ghost Genius (website, size, followers, etc.). Filtering: Must have a LinkedIn page with a website. Must have 200+ followers. Deduplication: checks if the company already exists in the CRM. 4. AI-Based Company Scoring A specialized AI model scores each company from 0 to 10 based on: Industry fit. Size/location alignment. Potential pain points that match your offering. If the company is new and relevant (score ≥ 7), it is saved in the Companies sheet. 5. Decision Maker Identification Uses Sales Navigator API (via Ghost Genius) to find employees with targeted job titles. For each matching profile: Enriches contact data (title, bio, etc.). Retrieves phone number (if available). Generates a 20-second personalized cold call script using OpenAI, based on company and profile data. Saves all information in the Leads tab of the CRM. If no decision maker is found, the company status is marked accordingly. 📈 Outcome A fully enriched, qualified lead database. Custom cold call scripts** ready to be used by SDRs or founders. Zero manual work – from search to lead generation, everything is automated. 💡 Use Case Perfect for SDRs, founders, or growth marketers looking to scale cold outreach without sacrificing personalization or running into LinkedIn scraping limits.