Workflow Templates

📰 Reddit to Newsletter (Automated Curation with Open AI 4o Mini ) Turn the best posts from a subreddit into a ready-to-send HTML newsletter — no copy-pasting, no wasted time. This workflow fetches new posts, filters by topic of interest, analyzes comments, summarizes insights, and composes a clean HTML email delivered straight to your inbox with Gmail. 💡 What this workflow does ✅ Fetches posts from your chosen subreddit (default: r/microsaas, sorted by “new”) 🏆 Selects the Top 10 by upvotes, comments, and recency 🧭 Defines a topic of interest and runs a lightweight AI filter (true/false) without altering the original JSON 💬 Pulls and flattens comments into a clean, structured list 🧠 Summarizes each post + comments into main_post_summary, comment_insights, and key_learnings ✍️ Generates a newsletter in HTML (not Markdown) with headline, outline, sections per post, quotes, and “by the numbers” 📤 Sends the HTML email via Gmail with subject “Reddit Digest” (editable) 🛠 What you’ll need 🔑 Reddit OAuth2 connected in n8n 🔑 OpenAI API key (e.g., gpt-4o-mini) for filtering and summarization 🔑 Gmail OAuth2 to deliver the newsletter 🧵 A target subreddit and a clearly defined topic of interest 🧩 How it works (high-level) Manual Trigger → Get many posts (from subreddit) Select Top 10 (Code node, ranking by ups + comments + date) Set topic of interest → AI filter → String to JSON → If topic of interest Loop Over Items for each valid post Fetch post comments → Clean comments (Code) → Merge comments → Merge with post Summarize post + comments (AI) → Merge summaries → Create newsletter HTML Send Gmail message with the generated HTML ⚙️ Key fields to adjust Subreddit name* and “new” filter in *Get many posts Ranking logic* inside *Top 10 Code node Text inside Set topic of interest** Prompts* for *AI filter, Summarize, and Create newsletter (tone & structure) Recipient & subject line* in *Send Gmail message ✨ Use cases Weekly digest** of your niche community Podcast or newsletter prep** with community insights Monitoring specific themes** (e.g., “how to get first customers”) and delivering insights to a team or client 🧠 Tips & gotchas ⏱️ Reddit API limits: tune batch size and rate if the subreddit is very active 🧹 Robust JSON parsing: the String to JSON node handles clean, fenced, or escaped JSON; failures return error + raw for debugging 📨 Email client quirks: test long newsletters; some clients clip lengthy HTML 💸 AI cost: the two-step (summarization + HTML generation) improves quality but can be merged to reduce cost 🧭 Quick customization Change microsaas to your target subreddit Rewrite the topic of interest (e.g., “growth strategies”, “fundraising”, etc.) Adapt the newsletter outline prompt for a different tone/format Schedule with a Cron node for daily or weekly digests 📬 Contact & Feedback Need help tailoring this workflow to your stack? 📩 Luis.acosta@news2podcast.com 🐦 @guanchehacker If you’re building something more advanced with curation + AI (like turning the digest into a podcast or video), let’s connect — I may have the missing piece you need.

How It Works This workflow automates energy portfolio governance for energy managers, sustainability teams, and policy compliance officers. It eliminates the manual effort of aggregating multi-source energy data, applying forecasting and optimisation logic, and distributing performance outcomes to stakeholders. Three scheduled API feeds, weather data, energy demand, and renewable generation, are combined into a unified dataset. The Energy Governance Agent, backed by shared memory and a governance model, coordinates three specialist agents: a Renewable Forecasting Agent (predictive generation modelling), a Weather Analysis Agent (climate-adjusted demand assessment), and a Policy Compliance Agent (regulatory alignment checking). Five tools support the orchestration: an Energy Calculator, Optimisation Algorithm Tool, External Data API Tool, Sustainability Research Tool, and Structured KPI Output parser. Results are distributed across three outputs, a Slack sustainability alert, a Gmail performance dashboard email, and a Google Sheets KPI store, giving stakeholders immediate, channel-appropriate visibility into energy governance outcomes. Setup Steps Import workflow; configure the Energy Analysis Schedule trigger interval. Set API endpoint URLs for Fetch Weather Data, Fetch Energy Demand, and Fetch Renewable Generation nodes. Add AI model credentials to the Agents. Connect Slack credentials to the Send Sustainability Alert node. Link Gmail credentials to the Email Performance Dashboard node. Link Google Sheets credentials; set the sheet ID for the Energy KPIs tab. Prerequisites OpenAI API key (or compatible LLM) Slack workspace with bot credentials Gmail account with OAuth credentials Google Sheets with Energy KPIs tab pre-created Use Cases Energy managers automating renewable generation forecasting against real-time demand data Customisation Swap the Optimisation Algorithm Tool parameters to target carbon intensity, cost, or grid stability objectives Benefits Parallel triple-source ingestion ensures governance decisions are based on complete, synchronised energy data

Turn raw feedback into actionable product insights. This workflow collects feedback from both customers and staff via a single Jotform, uses Gemini AI to analyze and categorize it, then intelligently routes it: Actionable bugs and feature requests* become tasks in specific *Trello** lists, tagged with source and priority. General feedback* is logged in a structured *Airtable** base for later review. Urgent bugs* trigger instant *Slack** alerts for your dev team. An optional confirmation email is sent via Gmail if the submitter provides their address. Stop manually sorting feedback and ensure nothing falls through the cracks. This workflow centralizes input, automates triage, and delivers structured data directly to your product and development teams. Features Unified Feedback Collection:** Uses a single Jotform for customers and staff. AI-Powered Triage:** Gemini AI categorizes feedback (Bug, Feature Request, General), suggests priority, and extracts keyword tags. Intelligent Filtering:** An IF node separates actionable tasks from general comments. Automated Task Creation:** Creates Trello cards in specific lists ("Bugs," "Feature Backlog") with relevant labels (Source, Urgent). Structured Logging:** Saves all general feedback to an Airtable base for review and trend analysis. Conditional Alerts:* Notifies a Slack channel *only for high-priority bugs. Optional Email Confirmation:** Sends a thank-you email if the submitter provides their address. Nodes Used 🟣 Jotform Trigger (Jotform Trigger) ✉️ Gmail (Send Confirmation Email) 🧠 AI Agent (AI Feedback Triage) 🃏 Trello (Create Trello Card) 📣 Slack (Alert Dev Team) 🗂️ Airtable (Log General Feedback to Airtable) 🔧 Set, **❓ IF, 🚫 No Operation, do nothing How to use this template Follow these steps to configure the workflow with your accounts and specific IDs. 1. Set up Jotform, Trello, and Airtable (CRITICAL) Before starting, you must create the Jotform form, Trello board, and Airtable base exactly as described in the "Required Setup" section at the end of this document. 2. Configure the Jotform Trigger Node Credentials:** Connect your Jotform account. Form:** Select your "Help us improve IdeaToBiz" form (replace the title with your company name). Resolve Data:* Ensure the *"Resolve Data"* toggle in the node's parameters is turned *ON**. 3. Configure the Config (Set) Node This node stores your Trello IDs. You must replace the placeholder values. Find Your IDs:** Open your Trello board, add .json to the URL, and press Enter. Search the JSON page for your List names ("Bugs," "Feature Backlog") and Label names ("Customer," "Staff," "Other," "Urgent") to find their corresponding "id" values. Action:** Paste your unique IDs into the value fields in this node. 4. Configure the Email Provided? (IF) and Send Confirmation Email (Gmail) Nodes IF Node:** No configuration needed. Gmail Node:** Credentials: Connect your Gmail (or other email service) account. Customize: Edit the Subject and Body to match your company's voice. 5. Configure the AI Feedback Triage Node Credentials:** Connect your Google AI (Gemini) credentials. Check Prompt:** Ensure the prompt correctly references your feedback field (e.g., {{ $('Jotform Trigger').item.json['Feedback Details'] }}). Check Schema:** Ensure the "Structured Output" JSON schema matches the required fields (task_title, category, suggested_priority, tags). 6. Configure the Is it a Bug or Feature? (IF) Node No configuration needed. This node filters based on the AI output. 7. Configure the Create Trello Card Node Credentials:** Connect your Trello credentials. Board ID:** Select your Product Feedback board. Check Expressions:** Verify that the expressions for List ID and Labels correctly pull the IDs from your Config node and data from the AI Feedback Triage and Jotform Trigger nodes. The template should be pre-filled, but double-check node names if you renamed them. 8. Configure the Is it an Urgent Bug? (IF) Node No configuration needed. This checks the AI output before alerting Slack. 9. Configure the Alert Dev Team (Slack) Node Credentials:** Connect your Slack credentials. Channel:** Select the channel for urgent bug alerts (e.g., #dev-alerts). Customize:** Edit the message text if desired. Ensure the Trello card URL expression ({{ $('Create Trello Card').item.json.shortUrl }}) is correct. 10. Configure the Log General Feedback to Airtable Node Credentials:** Connect your Airtable credentials. Base ID:** Select your Product Feedback Log base. Table ID:** Select your Feedback Submissions table. Enable Typecast:* In the node's *Options, ensure the **Typecast toggle is ON. This is crucial for allowing n8n to create new tag options in Airtable. Check Field Mappings:** Verify that the field mappings correctly reference the AI Feedback Triage and Jotform Trigger nodes. 11. Activate Your Workflow! Once all credentials and IDs are configured, save and activate your workflow. How to Adapt the Template Change Task Destination:* Replace the Trello node with *ClickUp, **Asana, Jira, or another task manager. You'll need to adapt the field mappings. Change Logging Destination:* Replace the Airtable node with *Google Sheets, **Notion, or send logs via Email or Discord. Adjust AI Prompt:** Modify the prompt in the AI Feedback Triage node to change how feedback is categorized, prioritized, or tagged. Modify Filtering Logic:** Change the conditions in the Is it a Bug or Feature? IF node (e.g., maybe you also want "UI/UX Issue" to go to Trello). Refine Alerting:** Change the conditions in the Is it an Urgent Bug? IF node or send alerts for different categories (e.g., alert the design team for UI issues). Required Setup Jotform Form Setup Create Account: If needed, sign up at Jotform. Create Form: Build a form titled "Help us improve IdeaToBiz" (or similar). Add Fields: Radio Button: Label I am a..., Options Customer, Staff, Other (Required: ON). Email: Label Your Email (Optional) (Required: OFF). Long Text: Label Feedback Details (Required: ON). Submit Button: Label Submit Feedback. Trello Board Setup Create Board: Create a new Trello board named Product Feedback. Create Lists (Columns): Add at least these two lists: Feature Backlog Bugs Create Labels: Go to Menu -> More -> Labels and create: Urgent (Red recommended) Customer (Blue recommended) Staff (Green recommended) Other (Grey recommended) Airtable Base Setup Create Base: Create a new Airtable base named Product Feedback Log. Create Table: Name the table Feedback Submissions. Configure Fields: Rename the primary field (Name) to Feedback Summary (Type: Single line text). Rename Notes to Full Feedback (Type: Long text). Delete Assignee. Rename Status to Source (Type: Single select, Options: Customer, Staff, Other). Add Email field (Type: Email). Add AI Tags field (Type: Multiple select). Add Submitted At field (Type: Created time).

Snyk Vulnerability Automation Workflow with Webhook, Jira, Slack & Airtable This workflow receives vulnerability data(e.g., Snyk, Dependabot or any security scanner) from Snyk through a webhook, standardizes and validates the payload, checks Jira for duplicates using a unique vulnerability key, and either updates an existing Jira issue or creates a new one. It also sends real-time alerts to Slack and stores every new vulnerability in Airtable for reporting and auditing. The workflow ensures fast triage, prevents duplicate Jira tickets and centralizes all data for easy tracking. Quick Start – Implementation Steps Add the n8n Webhook URL to Snyk. Configure Jira, Slack and Airtable credentials in n8n. Adjust severity rules or Jira fields if required. Activate the workflow — vulnerability triage becomes fully automated. What It Does This workflow automates how your team processes vulnerabilities reported by Snyk. When a new vulnerability arrives, the system first normalizes the payload into a clean, consistent format. It then validates required fields such as the vulnerability ID, CVSS score, title and URL. If anything is missing, the workflow instantly sends a Slack alert so the team can review. If the payload is valid, the workflow assigns a severity level and generates a unique “vulnerability key.” This key is used to search Jira for existing issues. If a match is found, the workflow updates the existing Jira ticket and notifies the team. If no match exists, the workflow creates a brand-new Jira issue, sends a Slack alert and also writes the data into Airtable for centralized tracking and analytics. This ensures accurate documentation, avoids duplicates and gives teams visibility through both Jira and Airtable. Who’s It For This workflow is ideal for: DevOps and platform engineering teams Security engineers QA and development teams Companies using Snyk for vulnerability scanning Teams needing automated Jira creation and Airtable reporting Requirements to Use This Workflow To fully use this workflow, you need: An n8n instance (cloud or self-hosted) A Snyk webhook configured to send vulnerability notifications A Jira Software Cloud account A Slack workspace with bot permissions An Airtable base and personal access token Basic understanding of JSON fields How It Works Receive Vulnerability – Snyk posts data to an n8n webhook. Normalize Payload – Converts inconsistent Snyk formats into a standard structure. Validate Required Fields – Missing fields trigger a Slack alert. Assign Severity – CVSS score is mapped to Low/Medium/High/Critical. Generate Vulnerability Key – Used for deduplication (e.g., vuln-SNYK-12345). Check Jira for Matches – Searches by label to detect duplicates. Duplicate Handling – Updates existing Jira issue and sends Slack notification. Create New Issue – If no duplicate exists, creates a new Jira ticket. Store in Airtable – Adds a new vulnerability row for reporting and history. Slack Alerts – Notifies the team of new or updated vulnerabilities. Setup Steps Import the workflow JSON file into n8n. Configure credentials: Jira Slack Airtable Add the generated webhook URL inside your Snyk project settings. Update Jira project ID, issue type, or description fields as needed. Map Airtable fields (Title, CVSS, Severity, URL, Key, etc.). Update Slack channel IDs. Activate the workflow. How To Customize Nodes Customize Severity Rules Modify the node that maps CVSS score ranges: Change thresholds Add custom severity levels Map severity to Jira priority Customize Jira Fields Inside the Create or Update Jira Issue nodes, you can modify: Project ID Issue type Labels Description template Assigned user Customize Slack Messages Adjust Slack text blocks to: Change formatting Add emojis or styling Mention specific users or teams Send different messages based on severity Customize Airtable Storage Update the Airtable node to: Add new columns Save timestamps Link vulnerabilities to other Airtable tables Store more metadata for reporting Add-Ons (Optional Enhancements) You can extend this workflow with: Auto-close Jira tickets when Snyk marks vulnerabilities as “fixed”. Severity-based Slack routing (e.g., Critical → #security-alerts). Email notifications for high-risk vulnerabilities. Google Sheets or Notion logging for long-term tracking. Weekly summary report generated using OpenAI. Mapping vulnerabilities to microservices or repositories. Automated dashboards using Airtable Interfaces. Use Case Examples Automatic Vulnerability Triage – Instantly logs new Snyk findings into Jira. Duplicate Prevention – Ensures every vulnerability is tracked only once. Slack Alerts – Real-time notifications for new or updated issues. Airtable Reporting – Creates a central, filterable database for analysis. Security Team Automation – Reduces manual reviews and saves time. Troubleshooting Guide | Issue | Possible Cause | Solution | |-----------------------------|--------------------------------------------------|--------------------------------------------------------| | Slack alert not sent | Wrong API credentials or channel ID | Re-check Slack configuration | | Jira issue not created | Incorrect project ID / issue type | Update Jira node details | | Duplicate detection not working | Vulnerability key or label mismatch | Confirm key generation and JQL settings | | Airtable row not added | Wrong base or field mapping | Reconfigure Airtable node | | Webhook not triggered | Snyk not pointing to correct URL | Re-add the n8n webhook in Snyk | | Severity not correct | CVSS parsing error | Check normalization and mapping node | Need Help? If you need help setting up this workflow, customizing the logic, integrating new nodes or adding advanced reporting, feel free to reach out to our n8n automation development team at WeblineIndia. We can help automate with advanced security processes, build dashboards, integrate additional tools or expand the workflow as per your business needs.

Template Overview This n8n workflow provides an intelligent, timezone-aware AI voice calling system for e-commerce businesses to automatically confirm customer orders via phone calls. The system uses VAPI (Voice AI Platform) to make natural, conversational calls while respecting customer time zones and business hours. 🎯 Use Case Perfect for e-commerce businesses that want to: Automatically confirm high-value or important orders via phone Reduce order cancellations and disputes Provide personalized customer service at scale Maintain human-like interactions while automating the process Respect customer time zones and calling hours ✨ Key Features Timezone Intelligence Automatically detects customer timezone from shipping address or phone number Only calls during appropriate business hours (10 AM - 3 PM local time, weekdays) Schedules calls for appropriate times when outside calling hours Uses timezone-aware greetings (Good morning/afternoon/evening) AI-Powered Conversations Natural, context-aware conversations using VAPI Personalized greetings with customer names and local time awareness Intelligent confirmation detection from call transcripts Handles customer concerns and change requests gracefully Smart Call Management Automatic retry logic with attempt tracking Call quality assessment and cost tracking Detailed transcript analysis and sentiment detection Follow-up alerts for calls requiring human intervention Comprehensive Tracking Complete call history and analytics in Airtable Real-time status updates throughout the process Detailed reporting on confirmation rates and call quality Cost tracking and ROI analysis 🏗️ Workflow Architecture Main Flow (Order Confirmation) Order Webhook - Receives order data from e-commerce platform Data Validation - Validates required fields (phone, status) Timezone Detection - Determines customer timezone and calling eligibility Call Routing - Either initiates immediate call or schedules for later VAPI Integration - Makes the actual AI voice call Status Tracking - Updates database with call results Scheduled Flow (Retry System) Runs every 15 minutes to check for scheduled calls Respects retry limits and calling hours Automatically processes queued confirmations Webhook Handler (Results Processing) Receives VAPI call completion webhooks Analyzes call transcripts for confirmation status Sends follow-up alerts or confirmation emails Updates final order status 🔧 Prerequisites & Setup Required Services VAPI Account - For AI voice calling functionality Airtable Base - For order tracking and analytics SMTP Server - For email notifications n8n Instance - Self-hosted or cloud

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Who is this for? Automation enthusiasts, content creators, or social media managers who post article-based threads to Bluesky and want to automate the process end-to-end. What problem is this solving? Manual content repackaging and posting can be repetitive and time-consuming. This workflow automates the process from capturing article URLs (via Telegram or RSS) to scraping content, transforming it into a styled thread, and posting on Bluesky platform. What this workflow does Listens on Telegram or fetches from RSS feeds (AI Trends, Machine Learning Mastery, Technology Review). Extracts content from URLs using JinaAI. Converts the article into a neat, scroll-stopping thread via LangChain + Gemini / OpenAI ChatGPT. Splits the thread into multiple posts. The first post is published with “Create a Post”, while subsequent posts are replies. Adds short delays between posting to avoid rate limits. Setup Add credentials for Telegram Bot API, JinaAI, Google Gemini, and Bluesky App Password. Add or customize RSS feeds if needed Test with a sample URL to validate posting sequence. How to customize Swap out RSS feeds or trigger sources. Modify prompt templates or thread formatting rules in the LangChain/Gemini node. Adjust wait times or content parsing logic. Replace Bluesky with another posting target if desired. Made by: Khaisa Studio Need customs workflows? Contact Me!

How It Works Automates fraud risk detection for financial transactions by analyzing real-time webhook events through AI-powered scoring. Target audience: fintech companies, payment processors, and banking teams preventing fraud losses. Problem solved: manual fraud checks are reactive and slow; automated detection catches suspicious transactions instantly. Workflow receives transactions via webhook, configures processing parameters, runs OpenAI GPT-4 fraud analysis, calculates risk scores, branches on risk level, holds high-risk transactions, alerts fraud teams, logs incidents, and documents evidence for compliance investigations. Setup Steps Configure webhook endpoint for transaction ingestion. Set OpenAI API key and fraud detection prompts. Connect Google Sheets for incident logging. Enable email alerts to fraud team distribution list. Map risk thresholds (high/low). Prerequisites OpenAI API key, webhook-capable transaction source, Gmail for alerts, Google Sheets access, incident tracking database. Use Cases Payment processors detecting card fraud, fintech platforms catching account takeovers Customization Adjust risk thresholds and scoring logic. Add phone/SMS alerts for urgency. Benefits Detects fraud within seconds, reduces financial losses by up to 90%

What Problem Does It Solve? SEO professionals and marketers spend hours manually searching keywords to analyze competitor content. Copying and pasting SERP results into spreadsheets is tedious and prone to formatting errors. Analyzing "why" a page ranks requires significant mental effort and time for every single keyword. This workflow solves these by: Automatically fetching live Google search results for a list of keywords. Using AI to instantly analyze the top ranking pages for Intent, Strengths, and Weaknesses. Delivering a consolidated, strategic SEO report directly to your email inbox. How to Configure It API Setup: Connect your Decodo credentials (for scraping Google results).- Connect your Google Gemini credentials (for the AI analysis). Connect your Gmail account (to send the final report). Keyword Input: Open the "Edit Fields" node and replace the placeholder items (keyword_1, etc.) with the actual search terms you want to track. Email Recipient: Update the "Send a message" node with your email address. How It Works The workflow triggers manually (or can be scheduled). It loops through your defined list of keywords one by one. Decodo performs a real-time Google search for each term and extracts organic results. A JavaScript node cleans the data, removing ads and irrelevant snippets. The AI Agent acts as an expert SEO analyst, processing the top results to generate a concise audit. Finally, the workflow compiles all insights into a single email report and sends it to you. Customization Ideas Change the output: Save the analysis to a Google Sheet or Notion database instead of Email. Adjust the AI Persona: Modify the system prompt to focus on specific metrics (e.g., content gaps or backlink opportunities). Automate the Input: Connect a Google Sheet to dynamically pull new keywords every week. Schedule It: Replace the Manual Trigger with a Cron node to run this report automatically every Monday morning. If you need any help Get in Touch

Who's it for Open-source maintainers, product teams with public repositories, and any organization receiving a steady stream of GitHub Issues. Ideal for small teams who waste hours per week triaging duplicates and misrouted reports. How it works When a new Issue is opened, a GitHub webhook fires this workflow. It first filters for the "opened" action, then fetches the last 30 Issues from the repository. All Issue texts (new + past) are sent to OpenAI's embeddings API in a single batch call for efficiency. The workflow calculates cosine similarity between the new Issue and every past Issue. If the maximum similarity exceeds 0.85, the new Issue is auto-closed with a comment referencing the original. Otherwise, AI classifies it into one of four categories: bug (adds label + Slack alert to dev team), question (posts FAQ link as a comment), feature (appends to a roadmap Google Sheet), or spam (auto-close with label). AI is used only for classification — the duplicate detection uses deterministic vector math, and every action is rule-based. Set up steps Generate a GitHub Personal Access Token with repo scope Create a webhook on your repository pointing to this workflow's URL, subscribing to Issues events Create a Google Sheet named feature_roadmap with columns: date_added, issue_number, title, author, url, status Open Set Configuration and fill in the repo owner, repo name, Sheet ID, Slack channel, and FAQ URL Register GitHub and OpenAI Header Auth credentials and connect Google Sheets and Slack Activate the workflow How to customize Adjust duplicate_threshold for stricter or looser matching, change the embeddings model, or swap Sheets for Notion or Airtable.

TimeRex AI-Powered Booking Automation Description (for n8n template submission) Transform your TimeRex booking management with AI-powered automation. This workflow automatically processes bookings, enriches data with AI insights, and keeps your team informed via Slack—all in real-time. What This Workflow Does 🤖 AI-Powered Intelligence Smart Company Detection**: Automatically identifies company names from guest email domains Booking Categorization**: Uses Google Gemini to classify bookings (Sales/Support/Interview/Partnership/Media) Meeting Brief Generation**: AI creates actionable preparation notes for hosts before each meeting ⚡ Automated Processing Receives webhooks from TimeRex for confirmed and cancelled bookings Validates requests with security token verification Logs enriched booking data to Google Sheets Sends detailed Slack notifications with AI-generated insights 🛡️ Security & Reliability Token-based webhook authentication Security alerts for unauthorized access attempts Automatic cancellation handling with data cleanup Use Cases Sales Teams**: Automatically categorize leads and prepare meeting briefs Recruitment**: Streamline interview scheduling with AI-powered candidate insights Customer Success**: Track support meetings and prepare context for calls Media Relations**: Manage press interviews with automated briefings How It Works TimeRex sends a webhook when a booking is confirmed or cancelled Security token is verified (failed attempts trigger Slack alerts) For confirmed bookings: Media source is detected from calendar name Company name is extracted from email domain AI categorizes the booking purpose AI generates a meeting preparation brief Enriched data is saved to Google Sheets Slack notification is sent with AI insights For cancellations: Booking is found by Event ID Row is deleted from Google Sheets Cancellation alert is sent to Slack Setup Instructions Webhook Configuration Copy the webhook URL from the "TimeRex Webhook" node Paste it in TimeRex Settings → Webhook Security Token Copy your TimeRex security token Update the Verify Security Token node with your token Google Sheets Create a spreadsheet with these columns: event_id, booking_date, guest_name, guest_email, calendar_name, meeting_url, host_name, media_source, company_name, booking_category, ai_meeting_brief, created_at Update all Google Sheets nodes with your Sheet ID AI Credentials Connect your Google Gemini API credentials to both AI model nodes Slack Connect your Slack account Select your notification channel in all Slack nodes Activate Turn on the workflow and start receiving AI-enhanced booking notifications! Requirements TimeRex account with webhook access Google Cloud account (for Sheets & Gemini API) Slack workspace n8n instance (self-hosted or cloud) Customization Tips Modify the Filter by Calendar Type node to match your calendar naming convention Adjust AI prompts in the LLM Chain nodes for different categorization or brief styles Add more media sources to the Media Master sheet for accurate source tracking Extend the workflow with email confirmations or calendar event creation Short Description (100 characters max) Automate TimeRex bookings with AI-powered categorization, meeting briefs, and Slack notifications. Categories Sales Productivity AI Scheduling Tags TimeRex, Booking, AI, Google Gemini, Slack, Google Sheets, Automation, Meeting Management, LLM, Scheduling

WooCommerce Weekly Sales KPI Reporting to Slack & Google Sheets This workflow automatically generates a weekly sales performance report from WooCommerce and shares it with your team. It runs on a weekly schedule, fetches last week’s orders and refunds, calculates key sales KPIs, stores the results in Google Sheets and sends a summarized report to a Slack channel. Quick Implementation Steps (Get Started Fast) Connect WooCommerce, Slack and Google Sheets credentials in n8n. Update the WooCommerce store domain in the Configure WooCommerce Store node. Review the Slack channel and Google Sheet settings. Activate the workflow. That’s it — your weekly sales KPIs will now be generated and shared automatically. What It Does This workflow helps you track and share weekly WooCommerce performance without manual effort. It automatically calculates key sales metrics such as total orders, total revenue, average order value, refunds and top-performing products based on the previous week’s data. The workflow begins on a weekly schedule and determines the exact date range for the last completed week. Using this date range, it pulls sales orders and refund data from WooCommerce through HTTP requests. Multiple calculations are then performed to generate meaningful KPIs that are useful for both operational and leadership-level reporting. Once the KPIs are calculated, the workflow consolidates them into a clean report format. The data is saved in Google Sheets for long-term tracking and a readable summary is sent to a Slack channel so stakeholders can quickly review weekly performance. Who’s It For E-commerce store owners using WooCommerce Operations and sales teams tracking weekly performance Business managers who want automated KPI reporting Teams using Slack and Google Sheets for collaboration and reporting Requirements to Use This Workflow An active WooCommerce store with REST API access WooCommerce Consumer Key and Secret (Basic Auth) An n8n instance with scheduled workflows enabled A Slack workspace with permission to post messages A Google Sheets account with access to the target spreadsheet How the Workflow Works Weekly Schedule Trigger The workflow runs once per week. The exact day and time are configurable. Calculate Last Week’s Date Range A Code node calculates the start and end dates of the previous week. Configure WooCommerce Store The WooCommerce store domain is defined once and reused across API requests. Fetch Weekly Data from WooCommerce Orders with completed and processing status Refund data for the same date range Calculate KPIs Separate Code nodes calculate: Total orders and total revenue Average order value Refund count and refund amount Top products based on revenue Merge KPI Results All calculated KPIs are combined into a single dataset. Prepare Final KPI Report Fields Only required, clean fields are retained for reporting. Store Data in Google Sheets Each workflow run appends one new row with weekly KPI data. Send Weekly Report to Slack A formatted summary is posted to the selected Slack channel. Setup Instructions Update the WooCommerce domain in the Configure WooCommerce Store node. Verify WooCommerce API credentials in all HTTP Request nodes. Select the desired Slack channel in the Slack node. Confirm the target Google Sheet and worksheet. Adjust the weekly schedule if needed. Activate the workflow. How To Customize Nodes Weekly Sales KPI Trigger** Change the day or time to run the workflow at any point during the week. Configure WooCommerce Store** Update the domain if you move to a different store or environment. HTTP Request Nodes** Modify order statuses or add filters as needed. KPI Calculation Code Nodes** Add new metrics or adjust existing calculations. Slack Node** Send reports to a different channel or workspace. Google Sheets Node** Store data in another sheet or spreadsheet. Add-ons (Additional Features) Monthly or daily KPI reporting Email-based KPI reports Separate reports for different WooCommerce stores Alerting when revenue drops below a threshold Dashboard integration using BI tools Use Case Examples Weekly sales performance review for management Tracking revenue and refunds trends over time Sharing automated reports with remote teams Maintaining a historical KPI log in Google Sheets Supporting business decisions with consistent weekly data There can be many more use cases depending on how this workflow is customized or extended. Troubleshooting Guide | Issue | Possible Cause | Solution | |------|---------------|----------| | No data in Slack | Workflow not active | Activate the workflow | | Empty KPIs | No orders in the selected week | Verify WooCommerce data | | Incorrect dates | Schedule misconfiguration | Review trigger timing | | Google Sheets not updating | Permission issue | Reconnect Google Sheets credentials | | WooCommerce API error | Invalid credentials | Check Consumer Key and Secret | Need Help? If you need help setting up this workflow, customizing KPIs or building advanced reporting automation, our n8n workflow developers at WeblineIndia are here to help. Our team has strong expertise in n8n workflow automation, WooCommerce integrations and business intelligence reporting. Whether you want to extend this workflow or build a similar solution tailored to your business needs, feel free to reach out to WeblineIndia for expert support.

Overview This workflow automates bulk email campaigns with built-in validation, deliverability protection, and smart send-time optimization. It processes CSV leads, validates emails, enriches data, and schedules campaigns intelligently. Emails are sent using controlled inbox rotation, while engagement tracking and analytics continuously improve performance. How It Works Campaign Input Receives campaign data and CSV leads via webhook. Lead Processing Extracts CSV data, splits leads, and validates email format. Domain & Quality Checks Verifies domains using MX records and filters invalid leads. Lead Enrichment Adds timezone, domain type, and engagement score for better targeting. Lead Storage Stores valid leads and separates invalid ones for tracking. Campaign Execution Scheduler fetches active campaigns and selects top leads. Send Optimization Calculates best send time per lead based on timezone and historical performance, while selecting inboxes within sending limits. Email Delivery Waits until optimal time and sends emails using selected inbox. Tracking & Logging Logs sent emails and updates inbox usage statistics. Event Tracking Captures opens, clicks, replies, and bounces via webhook. Performance Analytics Updates campaign stats and analyzes engagement trends. Continuous Optimization Updates send-time rules to improve future campaign performance. Setup Instructions Connect webhook for campaign and CSV upload Configure send limits, delays, and MX API Set up Postgres with required tables Connect Gmail or SMTP for sending Configure event webhook for tracking Enable campaign and analytics schedulers Test with sample campaign before activating Use Cases Running cold email campaigns at scale Improving email deliverability and sender reputation Automating lead validation and enrichment Optimizing send times based on engagement data Managing multi-inbox outbound systems Requirements n8n instance with webhook support Postgres database Gmail or SMTP email account(s) MX record lookup API (e.g., Google DNS) Email tracking system or webhook integration Notes Inbox rotation and throttling help prevent spam and protect reputation. Engagement-based lead scoring improves campaign performance. Send-time optimization is continuously refined using real data. You can extend this workflow with personalization or AI-generated emails.