Workflow Templates

Intelligent seller governance enforcement and compliance automation How It Works This workflow automates marketplace seller compliance monitoring and enforcement for platform trust, legal, and operations teams. It receives seller data via webhook, routes it through a central Governance Agent backed by persistent memory, and fans out to four specialised AI sub-agents: Policy Monitoring (with compliance scoring and violation severity calculation), Appeals Review, and Enforcement Decision. A Structured Enforcement Output parser standardises results before routing to enforcement actions. The workflow then prepares an audit log, writes to an Enforcement Audit Trail, and triggers multi-channel notifications — Gmail appeal decisions, warning emails, Slack alerts to the compliance team, and suspension notices. Finally, seller records are updated in a Seller Compliance Records store. This eliminates manual case reviews, ensures consistent policy application, and creates a full auditable enforcement trail at scale. Setup Steps Configure webhook URL in Receive Seller Data node and secure with authentication. Set AI model credentials (OpenAI/Anthropic) in all agent and model nodes. Add Slack credentials and target channel to Notify Compliance Team node. Connect database/Google Sheets credentials. Activate and test with a sample seller payload. Prerequisites Gmail account with OAuth2 credentials Slack workspace and bot token Database or Google Sheets for audit and records storage Use Cases Automated suspension and warning issuance for policy-violating marketplace sellers Customisation Swap enforcement channels (e.g., replace Gmail with SendGrid) Benefits Eliminates manual seller case reviews — scales enforcement without added headcount

AI Email Assistant: Get Actionable Gmail Alerts on Telegram Who is this for? This template is designed for busy professionals, founders, freelancers, and support teams who want to stay on top of important emails without constantly checking Gmail. It’s ideal for anyone who needs instant, actionable notifications directly on Telegram. What problem is this workflow solving? / Use case Important emails often get buried under newsletters, promotions, and low-priority messages. Constantly refreshing Gmail wastes time and breaks focus. This workflow acts as an AI-powered email filter and alert system. It monitors your inbox, analyzes incoming messages, and sends only relevant, actionable summaries to Telegram — so you can react quickly without inbox overload. What this workflow does Monitors your Gmail inbox for new emails. Uses AI (OpenAI) to analyze and classify each email. Extracts key information such as: Urgency level Required action Summary of the message Sends a structured, concise alert to Telegram. Optionally highlights emails that require: Immediate reply Payment confirmation Meeting scheduling Client follow-up The result: you receive smart, decision-ready notifications instead of raw email forwards. Setup Import the workflow into your n8n instance. Connect Gmail credentials Add your Google account in n8n. Grant permission to read your inbox. Select the mailbox/folder you want to monitor. Set up OpenAI credentials Add your OpenAI API key in n8n. Ensure billing is active. Connect Telegram Create a Telegram bot via @BotFather. Copy the bot token into n8n. Add your Chat ID (or group ID) where alerts should be sent. Test the workflow Send a test email to your Gmail. Confirm that a summarized, actionable message appears in Telegram. How to customize this workflow to your needs Filter specific senders** Modify the Gmail trigger to monitor only emails from clients, payment platforms, or specific domains. Adjust AI instructions** Edit the system prompt to: Classify emails by priority (High / Medium / Low) Detect invoices, contracts, or support requests Automatically draft suggested replies Change alert format** Customize the Telegram message structure (add emojis, urgency labels, or action buttons). Add automation branches** Extend the workflow to: Create tasks in Notion or Trello Add calendar events automatically Label emails in Gmail based on AI classification With this template, your inbox becomes an AI-powered assistant that filters noise and delivers only what truly matters — directly to Telegram in real time. 👋 Need help or want to customize this? 📩 Contact: LinkedIn 📺 YouTube: @DRFIRASS 🚀 Workshops: Mes Ateliers n8n Need help customizing? Contact me for consulting and support : Linkedin / Youtube / 🚀 Mes Ateliers n8n

This workflow manages subscription billing reminders and data updates via Telegram. It runs daily at 8:00 AM to check for upcoming due subscriptions, formats relevant information, and sends reminders to users. It also processes user messages for subscription management—adding, updating, or retrieving billing info—using AI-powered natural language understanding. Main outcomes include automated subscription tracking, timely reminders, and conversational interaction through Telegram, reducing manual tracking efforts and improving billing accuracy. Automation Benefits Time & Cost Savings Manual Process: Several hours/week spent managing subscriptions and reminders manually. Automated Process: Workflow completes checks, reminders, and data updates in under a minute. Time Savings: Saves approximately 5 hours weekly, translating to significant productivity gains and cost reduction. ROI: Automation pays for itself within the first month due to saved labor. Error Reduction: Minimized manual entry errors, ensuring accurate billing records and timely reminders. Business Impact Solves the problem of manual subscription tracking and reminders. Scales effortlessly as subscription list grows. Opens new opportunities for proactive customer engagement, personalized messaging, and integrated billing insights. Setup Guide Prerequisites Google Sheets account with subscription data sheet. OpenAI API key with access to GPT-4. Telegram bot token with messaging permissions. Email SMTP setup if email reminders are used. API Configuration Google Sheets: Generate OAuth2 credentials, enable Sheets API, and authorize access. OpenAI: Create API key, set model to GPT-4, and test connectivity. Telegram: Create bot via BotFather, retrieve token, and set webhook URL. Webhook URL: Use the provided URL in the Telegram bot settings. Node-by-Node Setup OpenAI Chat Model: Enter API credentials, select GPT-4 model. Google Sheets: Input spreadsheet ID, sheet name, and ensure correct permissions. Telegram Nodes: Insert chat ID, message parsing, and response formatting. Schedule Trigger: Confirm cron expression for daily execution. For AI nodes, test with sample messages to verify formatting and extraction. Testing & Validation Run workflow manually. Confirm data is retrieved, processed, and responses sent. Verify subscription updates in Google Sheets. Check Telegram chats for correct message flow. N8N Documentation References Google Sheets Node OpenAI Node Telegram Node Schedule Trigger Maintenance & Troubleshooting Regular Maintenance (Monthly) Check API credentials and renew tokens if expired. Monitor workflow logs for errors. Review Google Sheets data for consistency. Update API keys when new versions or permissions are granted. Verify currency conversion accuracy periodically. Common Issues & Solutions Workflow not triggering: check schedule settings and webhook URLs. Data not updating: verify Google Sheets credentials and permissions. Incorrect responses: test AI prompt inputs and outputs. API failures: regenerate API keys or check quota limits. Reconfigure nodes if external API changes. Monitoring & Alerts Set up email or Slack alerts for failures. Regularly review execution logs. Track key metrics like successful runs, error rates, and response times. Support & Escalation Check n8n logs first for errors. Export workflow for support if needed. Use n8n community forums for common issues. Contact API providers for account-specific problems. Emergency procedures: restart workflow, regenerate tokens. Updates & Improvements Review workflow performance quarterly. Optimize AI prompts for better accuracy. Backup workflow configurations before major changes. Incorporate user feedback for feature enhancements.

Optimize your performance review process with this automated workflow. Running daily at 8 AM, it retrieves scheduled reviews from a Google Sheet, validates upcoming sessions, processes each review, and sends email reminders to participants. It also updates Google Calendar events, notifies HR via Slack, and logs review statuses back into the sheet — ensuring a seamless, tracked, and multi-channel communication experience. 📅🤖 What This Template Does Step 1: Triggers Daily Check at 8 AM to initiate the review process. ⏰ Step 2: Gets Review Schedule by reading planned reviews from a Google Sheet. Step 3: Filters Upcoming Reviews to focus on sessions within the next 3 days. Step 4: Validates Reviews Scheduled? Ensures reviews exist and are ready to process. Step 5: Splits into Manual to handle each review individually. Step 6: Prepares Review Data for notifications and updates. Step 7: Branches actions:   → Sends Email Reminder to participants.   → Updates Calendar Event with the scheduled session.   → Notifies HR on Slack with review details.   → Updates Review Status in the Google Sheet with logged feedback. Key Benefits Automates daily review scheduling and reminders Ensures timely calendar updates and notifications Centralizes feedback logging in Google Sheets Enhances HR visibility with Slack alerts Reduces manual coordination efforts Improves review process consistency Features Daily trigger at 8 AM Google Sheet integration for review schedule Filtering for upcoming reviews (next 3 days) Validation of scheduled reviews Multi-channel notifications (email, Slack) Google Calendar event creation Real-time status updates in sheets Manual processing for individual reviews Requirements GOOGLE_SHEET_ID**: Your Google Sheet ID (structured as below) Credentials Needed:** Google Sheets OAuth2 Gmail API Key Google Calendar OAuth2 Slack Bot Token (with chat:write permissions) Customize:** • Review schedule columns (e.g., Employee, Date, Reviewer, Status) • Reminder email template • Slack channel for HR notifications • Calendar event duration Google Sheet Structure: Create a sheet with columns: Employee Name Review Date Reviewer Status Feedback Updated At Target Audience HR teams managing performance reviews 👥 Managers scheduling regular check-ins ⏳ Organizations ensuring review compliance 📋 Remote teams needing centralized updates 🌐 Companies prioritizing employee feedback 📈 Step-by-Step Setup Instructions Set up Google Sheet  → Create a sheet with columns: Employee Name, Review Date, Reviewer, Status, Feedback, Updated At.  → Replace YOUR_SHEET_ID in the workflow with your actual Sheet ID. Configure Daily Trigger  → Set the "Daily Check at 8 AM" node to run at 8:00 AM IST (adjust for timezone if needed). Connect Google Calendar  → Enable Google Calendar OAuth2 and select the relevant calendar (e.g., hr@company.com). Customize Review Filter  → In "Filter Upcoming Reviews," set the range to check the next 3 days from today (e.g., October 24–27, 2025). Set Up Notifications  → Edit the "Send Email Reminder" template (e.g., include review date and link).  → Configure "Notify HR on Slack" with your HR channel ID. Test the Flow  → Add a test review entry in the sheet (e.g., date within 3 days).  → Run manually or wait until 8 AM IST on October 25, 2025 → Verify email, calendar event, Slack message, and sheet update. Go Live  → Enable the daily trigger.  → Monitor sheet and notifications for the first run. Workflow Complete! Reviews scheduled, reminders sent, and feedback logged — all on autopilot. Metrics to Track: Reviews scheduled daily Reminder delivery success Calendar update rate Feedback logging completion

APK Upload Monitoring and Automated MobSF Analysis with Slack Reporting This workflow monitors a Google Drive folder for newly uploaded APK files, automatically downloads them, triggers a MobSF static analysis scan, processes the output to detect unused or risky libraries and sends a developer-friendly summary directly to Slack. It is ideal for teams who want fast, automated insights into Android app dependencies. ⚡ Quick Start: Rapid Implementation Steps Connect Google Drive and select the APK upload folder. Add your MobSF server URL in both HTTP Request nodes. Add your OpenAI API credentials. Connect Slack and choose your preferred channel. Activate the workflow — you're ready to automate APK analysis. What It Does This workflow automates the complete static analysis process for Android APK files. When an APK is uploaded to a specific Google Drive folder, n8n immediately retrieves the file and sends it to MobSF for scanning. MobSF returns detailed JSON-based findings, including code, library usage and component insights. The workflow then uses a series of JavaScript code nodes to extract relevant package information, compare used vs. detected packages, identify unused dependencies and classify them by risk. These results are transformed into a concise summary using an AI model. Finally, the summary is posted automatically to a Slack channel for fast team visibility. This enables developers to take quick action on dependency cleanup, performance optimizations or security risks without manually reading the full MobSF report. Who’s It For Android developers wanting automated dependency insights QA/security teams needing MobSF scans on every APK upload DevOps engineers maintaining CI/CD pipelines Mobile teams who frequently share build artifacts Organizations wanting fast Slack-based reporting Requirements to Use This Workflow A Google Drive account with access to an APK upload folder A running MobSF instance (Docker supported) OpenAI API credentials Slack workspace with API access n8n installed (self-hosted or cloud) How It Works & How To Set Up 1. Google Drive Trigger Setup Connect your Google Drive credentials. Choose the folder dedicated to APK uploads. Event type: fileCreated (fires whenever a new APK is added). 2. Downloading the APK The workflow uses the Google Drive node to download the uploaded file. No manual configuration required beyond credential setup. 3. Configure MobSF Upload Replace the provided local URL with your MobSF instance URL. Ensure MobSF is reachable (via Docker or local network). Use multipart/form-data to upload the binary file. 4. Trigger MobSF Static Scan The next HTTP Request node triggers a static scan using the returned hash. No further configuration needed. 5. Code Nodes (Package Processing) These three nodes: extract used/detected packages, identify unused libraries, classify them as safe, maybe-required or risky. You can customize logic if needed. 6. AI-Based Summary Generation Connect OpenAI credentials. The node generates a clean, non-markdown summary for Slack. 7. Slack Notification Connect your Slack account. Select any desired channel. Summary is pushed instantly on every APK upload. 8. Activate the Workflow Once all credentials are added, enable the workflow and test by uploading an APK. How To Customize Nodes Google Drive Trigger Modify polling interval (e.g., every 5 minutes). Change folder for different build pipelines. MobSF Request Nodes Replace URL to support remote servers or Kubernetes deployments. Add additional headers if needed. Code Nodes Adjust package detection rules. Add tagging, filtering or extra metadata extraction. OpenAI Summary Node Customize the prompt for different reporting styles (e.g., shorter, more technical). Slack Node Add formatting, mentions or route to multiple channels. Add-Ons (Optional Extensions) Email Notifications** – Send the same report to email via Gmail or SMTP. Jira Ticket Auto-Creation** – Open issues when risky dependencies are detected. Save Reports to Database** – Store unused package data for long-term trends. CI/CD Integration** – Trigger analysis via GitHub Actions or Jenkins. VirusTotal Scan** – Add an extra malware check layer. Use Case Examples Automated Dependency Cleanup Quickly identify unused libraries after each build upload. Security Monitoring for Android Releases Ensure risky system packages aren’t unintentionally included. Team Collaboration Enhancement Send automated insights to Slack for faster decision-making. QA Validation Before Deployment Confirm that declared dependencies match actual usage. Build Optimization Remove unnecessary packages to reduce APK size and performance overhead. > There are many more possible uses depending on team needs and environment. Troubleshooting Guide | Issue | Possible Cause | Solution | | ------------------------------ | --------------------------------------- | ------------------------------------------------------ | | Workflow not triggering | Wrong Google Drive folder | Re-select the correct APK folder in the trigger node | | MobSF upload failing | Wrong URL or server not running | Check MobSF Docker container and update the URL | | MobSF scan shows empty results | APK not parsed successfully | Verify the APK is valid and not corrupted | | Slack message not delivered | Channel permissions or wrong channel ID | Reconnect Slack credentials and select a valid channel | | AI summary node fails | Missing OpenAI credentials | Add OpenAI API key in the credentials section | Need Help? If you need assistance setting up, extending or customizing this workflow, our n8n automation experts at WeblineIndia are available to help. Whether you want to add new features, integrate more systems or build similar automation workflows, feel free to reach out to us for professional support.

Overview This n8n template automates finding roofing contractors in any city using Google Maps. It deep-scrapes listings via ScrapeOps Proxy, deduplicates results against Google Sheets, saves fresh leads, and sends alerts via Gmail and Slack - all triggered from a simple web form. Who is this for? Roofing companies building local lead lists without manual research Sales teams prospecting contractors in new cities or regions Agencies running lead generation campaigns for home services clients Anyone who needs structured local business data from Google Maps What problem does it solve? Manually searching Google Maps, copying business details, and checking for duplicates is slow and error-prone. This workflow automates the entire process - from search to deduplication to saved leads - so you get fresh, structured contractor data with zero manual effort. How it works A web form captures the target city. ScrapeOps Proxy scrapes Google Maps for roofing contractors in that city. Each listing is deep-scraped for full details: phone, website, rating, reviews, and address. Results are compared against existing Google Sheet entries to remove duplicates. Only new leads are saved to the sheet. Gmail and Slack alerts notify you of new leads instantly. Set up steps (~10–15 minutes) Register for a free ScrapeOps API key: https://scrapeops.io/app/register/n8n Add ScrapeOps credentials in n8n. Docs: https://scrapeops.io/docs/n8n/overview/ Duplicate the Google Sheet template and connect it to the Read Previous Entries and Save New Leads nodes. Configure Gmail credentials in the Send Gmail Alert node and set your recipient. Configure Slack credentials in the Send Slack Alert node and set your channel. Open the form URL, enter a city, and run. Pre-conditions Active ScrapeOps account (free tier available): https://scrapeops.io/app/register/n8n ScrapeOps community node installed in n8n: https://scrapeops.io/docs/n8n/overview/ Google Sheets credentials configured in n8n Duplicated Google Sheet template with correct column headers Gmail credentials for alert emails Slack credentials for channel notifications Disclaimer This template uses ScrapeOps n8n integration as a community node. You are responsible for complying with Google's Terms of Use, robots.txt directives, and applicable laws in your jurisdiction. Scraping targets may change at any time; adjust render, scroll, and wait settings and parsers as needed. Use responsibly and only for legitimate business purposes.

This workflow automates the assignment of household chores. It reads tasks and a list of people from Google Sheets, pairs each task with someone, updates the spreadsheet with the assignments and emails each person their chores. Each run makes a random assignment so you don’t have to decide who does what. By running on a schedule, it keeps your chore rotation automated. Who is it for? Designed for families, roommates, flat‑shares or property managers who want to keep track of recurring chores without endless group chats or arguments. It’s also helpful for anyone coordinating a team of cleaners or volunteers and wishing to automate a fair distribution of tasks. How it works A Schedule Trigger starts the workflow at a regular interval (default every seven days). Google Sheets node reads the “Tasks” sheet from your spreadsheet. Each row contains a chore with a task. Another Google Sheets node reads the “Persons” sheet to obtain the list of people available to do chores. Next a Code node filters out any people without an email address and any tasks without a task name, then selects a random person for each task. A Gmail node sends each person an email summarising the chore they’ve been assigned. The last Google Sheets node updates the “Tasks” sheet, writing the assigned person’s name into the assigned_to column. Setup steps Spreadsheet – Create a Google Sheets document with two sheets. The first sheet “Tasks” should have columns for task, description, assigned_to and a “hidden row_number”. The second sheet “Persons” should have columns for name and email and “hidden row_number”. Fill them with your current chores and household members. Connect your Google account – In the Get Tasks and Get People nodes, select the credential for your Google account and search for your sheets. Configure the Schedule Trigger – Set the trigger interval (for example, every seven days on a Sunday evening). Edit the assignment logic (optional) – The Code node is preconfigured to filter data and assign tasks randomly. You can modify this script if you prefer a round‑robin approach, weighting by difficulty, or any other logic. Configure Gmail – In the Send a message node, select your Gmail credential. If you want you can customise the subject and body of the email. Update sheet mapping – In the Update assign_to node, ensure the assigned_to column mapping writes the assigned person’s name back to the correct row. The workflow uses the row_number to match the row being updated. Test and activate – Run the workflow manually to verify it reads your sheets, assigns tasks and sends emails. Once satisfied, activate the schedule so it runs automatically. Requirements · A Google account with access to Google Sheets and Gmail. · A spreadsheet containing two sheets as described above (see images), with headers matching the field names used in the workflow. How to customise it Change the schedule interval to suit your rotation, edit the email template to include due dates or motivational messages, or modify the assignment script to weight tasks by difficulty. You could also send notifications via Slack or Telegram.

This workflow classifies incoming support messages from email or Slack, drafts AI-generated replies for routine queries, and automatically pauses to notify a human agent for sensitive topics such as complaints, emotional distress, billing disputes, legal concerns, or escalation requests. Who's it for • Customer support teams handling 50+ messages per day • SaaS companies needing compliant, empathetic AI responses • E-commerce brands managing returns, refunds, and complaints • Any team that wants AI speed with human oversight on sensitive issues How it works / What it does Captures incoming messages from Email (webhook) or Slack Normalizes message context (sender, channel, body, urgency signals) AI classifies the message into a category and sensitivity tier Routine queries → AI drafts reply → sent automatically Sensitive queries → AI drafts reply → paused for human review Human approves, edits, or rejects the draft via webhook resume Final reply sent to customer via email or Slack All interactions logged to Google Sheet with category, tier, and resolution How to set up Import this workflow Configure credentials (Gmail/IMAP, Slack, OpenAI/Anthropic, Google Sheets) Update your support tone, escalation keywords, and team Slack channel Activate workflow Requirements • Gmail or IMAP webhook / Slack Events API • OpenAI / Anthropic / Grok API • Slack Bot Token (for human notifications) • Google Sheets for audit logging • HTTP endpoint for human approval webhook How to customize the workflow • Edit sensitivity tiers in the Python classification node • Change escalation keywords list • Update Slack notification channel and message template • Modify AI tone and persona in the AI draft node • Adjust wait timeout for human review window

This n8n template demonstrates how to automatically analyze all your accumulated notes from the past week and generate actionable insights, task lists, and priorities using AI. Use cases are many: Try automating weekly planning sessions, extracting action items from meeting notes, identifying recurring themes in your thoughts, or creating data-driven weekly reports for personal productivity tracking! Good to know ChatGPT analysis costs approximately $0.01-0.05 per week depending on the volume of notes The workflow uses advanced date filtering to process exactly 7 days of content Email sending requires SMTP configuration (Gmail, Outlook, etc.) Perfect companion:* Works seamlessly with the "Audio Notes to Google Docs*" workflow - it reads and analyzes all notes created by that system! How it works A schedule trigger runs every Sunday at your preferred time (default: 11 PM) The workflow reads your complete Google Doc containing all accumulated notes A smart filter function extracts only entries from the past 7 days using date stamp recognition The filtered content gets sent to ChatGPT which analyzes patterns and extracts: Actionable tasks for next week Important deadlines and appointments Key insights and learnings Top 3 priorities Category distribution (Work, Private, Health, etc.) A second AI call creates a personalized email summary with context and recommendations The structured analysis gets appended to your Google Doc as a weekly summary You receive a Telegram notification when the review is complete A detailed email report lands in your inbox with the full analysis and action items How to use The workflow runs automatically every Sunday - no manual intervention needed Adjust the schedule trigger to your preferred day/time for weekly planning Review the email summary and use the extracted tasks for your upcoming week planning The Google Doc serves as your permanent archive of weekly insights Requirements Google Docs API access to read your notes document OpenAI API account for ChatGPT analysis (GPT-4 recommended for best results) SMTP email configuration for sending summary reports Telegram Bot Token for notifications Prerequisite:* The *"Audio Notes to Google Docs**" workflow or similar system that creates timestamped entries Customising this workflow Modify the AI analysis prompt to focus on specific areas (business metrics, health tracking, learning goals) Add multiple analysis modes (daily, bi-weekly, monthly reviews) Include additional outputs like calendar event creation, task manager integration, or team sharing Connect to project management tools like Notion, Asana, or Monday.com for automatic task creation

Monitor a company watchlist for new Seed and Series A funding rounds and deliver a formatted weekly scouting report via email and Slack. This workflow reads company domains from a Google Sheets watchlist, checks each one for recent financing events via the PredictLeads Financing Events API, filters for Seed and Series A rounds from the past 7 days, then uses OpenAI to generate a professional weekly scouting report with a summary table and trend analysis. The report is delivered via Gmail and Slack. How it works: Weekly schedule trigger runs every Monday. Reads company domains from the Google Sheets watchlist. Loops through each company and fetches financing events from PredictLeads. Filters for Seed and Series A rounds that occurred in the last 7 days. Aggregates all filtered funding events into a single dataset. Sends the aggregated data to OpenAI to generate a formatted scouting report. The report includes a markdown table (Company, Round Type, Amount, Date, Key Investors) and trend analysis. Sends the full report via Gmail. Posts a summary notification to Slack. Setup: Create a Google Sheet with a "Watchlist" tab containing a column: domain. Configure the Gmail recipient address in the Send Report Email node (default: team@yourcompany.com). Set up a Slack incoming webhook URL in the Slack Summary node. Add your OpenAI API key in the Generate Scouting Report HTTP Request node. Add your PredictLeads API credentials (X-Api-Key and X-Api-Token headers). Requirements: Google Sheets OAuth2 credentials. Gmail OAuth2 credentials. Slack incoming webhook URL. OpenAI API account (uses gpt-4o-mini, ~$0.003-0.008 per call). PredictLeads API account (https://docs.predictleads.com). Notes: The 7-day lookback window is configured in the Filter Seed & Series A code node. Funding categories include "seed", "series_a", and "series a" variations. If no funding rounds are found, the report states that clearly rather than failing. PredictLeads Financing Events API docs: https://docs.predictleads.com

This n8n template allows you to automatically monitor your company's budget by comparing live Bexio accounting data against targets defined in Google Sheets, sending automated weekly email reports. It also exports your financial data from Bexio into a flexible spreadsheet environment. Financial overspending often goes unnoticed until it's too late. This workflow transforms reactive accounting into proactive management by automatically calculating monthly actuals and flagging budget overages in real-time, eliminating the need for manual spreadsheet updates. Who’s it for This workflow is built for Founders and CFOs who want to replace reactive accounting with proactive financial management. It is the ideal solution for leadership teams needing to eliminate manual data entry, synchronize live Bexio actuals against Google Sheet targets, and receive automated weekly email reports that proactively flag budget overages before they become critical issues. How it works The workflow automates the extraction and analysis of your Bexio accounting journal through several stages: Data Extraction: It uses a recursive pagination loop to fetch journal entries from the Bexio API in batches of 1,000 records. Data Synchronization: It utilizes the "Append or Update" operation in Google Sheets to ensure records stay current without creating duplicates. Financial Analysis: The system reads target thresholds from a "Budgets" sheet and aggregates costs per account by calculating the delta between Debits and Credits. Automated Reporting: A logic engine compares monthly actuals against budgets and generates a summary report sent via Gmail if thresholds are exceeded. How to set up Credentials: Connect your Bexio (Bearer Token), Google Sheets (OAuth2), and Gmail accounts in their respective nodes. Target Sheet: In the "Update Records" node, select your specific Google Spreadsheet and target tab for the journal entries. Use this template to create your database - Google Sheet Template Budget Configuration: Clone the template spreadsheet and define your specific metrics and monthly budget limits in the "Budgets" sheet. Date Filtering: Open the "Get Records" node and adjust the from and to query parameters (currently set for the 2025 fiscal year) to match your reporting period. Gmail: Enter the recipient email address in the "To" field of the Gmail node. Requirements Bexio Account: Must have API access enabled. Google Workspace: Access to Google Sheets for data storage and Gmail for sending reports. How to customize the workflow Budget: You can set budgets for as many metrics as you want for every accounting period. Sync Frequency: The "Schedule Trigger" can be adjusted from its weekly default to daily or hourly for more frequent updates. Notification Channels: Swap the Gmail node for Slack or Microsoft Teams to receive report via different channels. Rate Limiting: If processing a very large journal, increase the "Delay" node duration to remain within Bexio’s API rate limits. Pagination Reuse: The pagination logic can be adapted to retrieve any other Bexio data limited by API batch sizes.

📊 Description IPL fans expect more than a scoreboard. They want to know what the score means — is the batting team ahead of the game, is the chase getting away from them, who has the pressure right now. This workflow answers all of that automatically by fetching live IPL match data every 6 minutes, computing key cricket indicators, and sending everything to GPT-4o which generates a punchy 2-sentence analyst-style narrative ready to embed in any fan app, widget, or dashboard without a single line of custom backend code. Built for fantasy cricket platforms, sports media companies, IPL fan apps, and broadcast technology teams who want to add intelligent real-time commentary to their products without hiring a commentary team or training machine learning models. What This Workflow Does ⏰ Fires automatically every 6 minutes between 2PM and 11PM covering all IPL match windows 🌐 Accepts manual triggers via webhook for on-demand narrative generation at any time 🏏 Fetches all current cricket matches from CricAPI in real time on every execution 🔍 Dynamically identifies the live IPL match from the API response — no hardcoded match IDs 🧮 Detects which innings is active and computes all key match indicators automatically 🤖 Sends structured match context to GPT-4o which generates a 2-sentence human-sounding narrative 📝 Logs every narrative to Google Sheets with full match context for audit and analytics 📤 Returns a clean JSON response via webhook that any app or widget can poll in real time ⚠️ Fires an email alert if any node fails so you always know when the workflow needs attention Key Benefits ✅ Fully dynamic — no hardcoded match IDs, works across the entire IPL season ✅ Handles both 1st and 2nd innings with different logic and prompts per scenario ✅ GPT-4o sounds like a human analyst not a notification system ✅ Webhook response makes it embeddable in any fan app or widget instantly ✅ Complete match log in Google Sheets — every narrative timestamped and stored ✅ Falls back to any live T20 match when IPL is off-season so testing never breaks ✅ Error trigger ensures failures never go unnoticed How It Works Trigger Layer Two triggers run this workflow. The Schedule Trigger fires every 6 minutes between 2PM and 11PM IST covering both day games starting around 3:30PM and evening games starting around 7:30PM. The Webhook Trigger provides a manual entry point so developers can fire the workflow on demand for testing or to power a real-time polling architecture where a frontend app hits the webhook URL every few minutes to get the latest narrative. Both triggers feed into the same API call so the logic is completely identical regardless of how the workflow was triggered. Data Fetch & Match Detection A single HTTP Request node fetches all current cricket matches from CricAPI's /v1/currentMatches endpoint. The Code node then scans the response and dynamically finds the live IPL match by checking that the match name contains "IPL" or "Indian Premier League", the match type is T20, and the match has started but not ended. No match IDs are hardcoded anywhere — the workflow finds the right match on every execution. When IPL is not in season the workflow falls back to any live T20 match so development and testing are never blocked. Indicator Computation Once the match is identified the Code node detects which innings is active based on how many score entries the API returns. For the 1st innings it computes the current run rate, overs remaining, wickets in hand, projected total, match phase (Powerplay / Middle / Death), and pressure level. For the 2nd innings it additionally computes the required run rate, runs needed, run rate gap between RRR and CRR, and a pressure index based on how difficult the chase is becoming. Both scenarios produce a structured flat object that gets assembled into a context-rich GPT-4o prompt tailored to the specific innings situation. AI Narrative Generation The prompt is sent to GPT-4o via HTTP Request with a system prompt that instructs the model to write exactly 2 sentences, use the specific numbers provided, sound like a human cricket analyst, use cricket language fans understand, and never use percentages. The result is a narrative like "Mumbai Indians need 45 off 24 balls with 7 wickets in hand — the muscle is there but one collapse changes everything. Jasprit Bumrah has to be kept for the final two overs or this chase gets away from Kolkata." The narrative is then parsed from the API response and passed to both output nodes. Output & Logging Every narrative is appended to a Google Sheets log with the full match context — timestamp, match name, innings, current over, score, target, RRR, CRR, phase, pressure level, and the narrative text. This creates a complete over-by-over record of every narrative generated across the entire match. Simultaneously the Respond to Webhook node returns a clean JSON payload containing the match name, innings, score, over, phase, pressure, narrative, and timestamp — ready for any frontend app or dashboard to consume directly. Features Cron-based schedule trigger covering all IPL match hours Manual webhook trigger for on-demand generation and frontend polling Single API call architecture — one HTTP node, no unnecessary API calls Dynamic live IPL match detection — no hardcoded IDs 1st innings mode — CRR, projected total, wickets in hand, phase, pressure 2nd innings mode — RRR, CRR, run rate gap, runs needed, overs remaining, pressure Three-tier match phase detection — Powerplay, Middle overs, Death overs Pressure index computation based on RRR and wickets GPT-4o via HTTP Request — stable across all n8n versions Structured system prompt enforcing 2-sentence format and cricket language Google Sheets append logging with full match context per narrative Webhook JSON response for real-time frontend integration No Operation node on false branch for clean workflow termination Workflow-level Error Trigger with Gmail alert on any failure Requirements CricAPI account and API key — free tier at cricapi.com OpenAI API key (GPT-4o access) Google Sheets OAuth2 connection Gmail OAuth2 connection (for error alerts) Setup Steps Sign up at cricapi.com and get your free API key Create a Google Sheet called "IPL Win Probability Log" with the columns listed above Paste your Sheet ID into the Google Sheets node Connect your Google Sheets OAuth2 credentials Add your OpenAI API key to the Authorization header of the GPT-4o HTTP Request node in the format Bearer YOUR_KEY Connect your Gmail OAuth2 credentials to the error alert node Activate the workflow Target Audience 🏏 Fantasy cricket platforms who want to add real-time match intelligence to their user experience 📱 IPL fan apps and cricket portals looking for AI-generated commentary without a commentary team 📺 Broadcast technology teams building real-time graphics and insight widgets 🤖 Automation agencies building sports intelligence products for IPL franchise and media clients