Workflow Templates

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

AWS IAM Access Key Rotation Reminder Automation Workflow Watch the demo video below: Who’s it for DevOps/SRE teams responsible for AWS account security. Security/compliance officers ensuring key rotation policies are followed. Any AWS account owner who wants automatic detection of stale access keys. How it works / What it does Weekly Scheduler — triggers the workflow on a recurring basis. Get Many Users — fetches all IAM users in the AWS account. Get User Access Key(s) — retrieves the access keys associated with each user. Filter Out Inactive Keys — removes keys that are not active (e.g., status Inactive). Access Key Older Than 365 Days — checks the key creation date and flags keys older than one year. Send Slack Message — notifies a Slack channel with details of the outdated key(s) for review and action. No Operation — safely ends the workflow if no keys match the condition. How to set up Configure the Weekly Scheduler to run at your desired cadence (e.g., every Monday). Use Get Many Users to list all IAM users. For each user, call ListAccessKeys (Get User Access Key(s)) to fetch their key metadata. Apply a filter to keep only keys with status Active. Add a condition to compare CreateDate against today - 365 days. Send results to Slack using the Slack Post Message node. Requirements n8n (latest version). AWS credential in n8n configured for us-east-1 (IAM requires signing with this region). IAM permissions: iam:ListUsers iam:ListAccessKeys Slack bot credentials with permission to post messages in the desired channel. How to customize the workflow Change threshold** — adjust the 365 days condition to 90, 180, or any other rotation policy. Escalation** — mention @security or create a Jira/Ticket when old keys are found. Logging** — push flagged results into a Google Sheet, database, or log management system for audit. Automation** — instead of only notifying, add a step to automatically deactivate keys older than the threshold (after approval). Multi-account support** — duplicate or loop across multiple AWS credentials if you manage several AWS accounts.

This workflow integrates Google Analytics 4 (GA4) with Slack, enabling users to query their website data using natural language inside a dedicated Slack channel. An AI Agent interprets user queries, fetches relevant reports from GA4, and responds in Slack as a reply. How it works When a user sends a message in a specified Slack channel, the workflow is triggered. The message is filtered to remove @bot mentions, and then passed to an AI Agent. The AI Agent, powered by a Google Gemini Chat Model and utilizing conversational memory (to have back-and-forth with user on follow up questions, limit of 10), determines if the user's query requires data from Google Analytics 4. If so, it leverages a pre-configured GA4 tool to fetch the necessary report (e.g., page views, users, conversions for a specific date range). Finally, the AI Agent's response, containing the requested data, is sent back to the original Slack channel as a reply. Setup Steps Slack Trigger: Configure the Slack API credential and specify the channel n8n should monitor for new messages. Credentials: Create and configure the following credentials in n8n: Slack API: For sending and receiving messages. Google Analytics 4: For accessing GA4 reports. Requires a Google Cloud Project with the Analytics Data API enabled and a Service Account Key (JSON). Google Gemini Chat Model: For the AI Agent's intelligence. Requires an API key from Google AI Studio. AI Agent System Prompt: Craft a robust system prompt for the AI agent. This prompt should define the agent's role, constraints (e.g., "do not estimate or lie on data, if GA4 is unavailable, inform so"), and guidance on mapping natural language metrics/dimensions to GA4 equivalents (e.g., "when the user mentions 'leads', they mean 'conversions' in GA4"). Slack Reply: Ensure the final Slack "Send a message" node is configured to reply to the original channel, providing the data in a clear, concise format.

What Is This? This workflow monitors your Elastic Email subaccounts daily and sends a Slack alert whenever an account's email credit balance drops below a configurable threshold. It's a simple but essential guard against unexpected sending failures caused by depleted credits. Who Is It For? Any team or agency managing multiple Elastic Email subaccounts — marketing departments, email service providers, or developers running automated email campaigns — who want proactive warnings before credits run out. How Does It Work? The workflow runs once a day on a schedule. It calls the Elastic Email REST API to retrieve all subaccount data, then filters out any accounts with a credit balance below the minimum you define in the Config node. If any low-credit accounts are found, a Slack message with all accounts their email address and current credit balance will be sent. API errors are caught separately and also reported to Slack. How To Set It Up? Prerequisites: An Elastic Email account with API access A Slack workspace with bot permissions Step 1: Set the credit threshold In the Config node, set Minimum amount of Email Credits to the value below which you want to be notified (default: 100). Step 2: Configure Elastic Email credentials In the Load EE Subaccounts HTTP Request node, create a new Custom Auth credential with the following JSON: { "headers": { "X-ElasticEmail-ApiKey": "<Your EE Auth Token>" } } You can generate an API token directly in your Elastic Email account settings. Step 3: Configure Slack credentials Connect your Slack workspace using OAuth2 in both Slack nodes, and update the channel ID to your desired notification channel. Need help? Reach out at developers@sailingbyte.com or visit sailingbyte.com. Happy hacking!

This workflow provides a powerful way to automatically document and maintain an inventory of all your n8n workflows in a Google Sheet. By running on a schedule or manually, it fetches details about every workflow on your instance, processes the key information, and then populates a spreadsheet. This creates a centralized, up-to-date dashboard for auditing, monitoring, and understanding your automation landscape. Who is this for? This workflow is ideal for n8n administrators, developers, and teams who manage multiple workflows. If you need a clear and simple way to track all your automations, their components, and their statuses without manually checking each one, this template is for you. It's particularly useful for maintaining technical documentation, auditing node usage across your instance, and quickly finding specific workflows. What problem is this workflow solving? As the number of workflows on an n8n instance grows, it becomes challenging to keep track of them all. Questions like "Which workflows use the HubSpot node?", "Which workflows are inactive?", or "When was this workflow last updated?" become difficult to answer. This workflow solves that problem by creating a single source of truth in a Google Sheet. It automates the process of cataloging your workflows, saving you time and ensuring your documentation is always current. What this workflow does Triggers Execution: The workflow can be initiated either on a set schedule (via the Scheduled Start node) or manually (via the Manual Start node). Fetches All Workflows: The Get All Workflows node connects to your n8n instance via the API to retrieve a complete list of your workflows and their associated data. Processes Workflows Individually: The Loop Through Each Workflow node iterates through each retrieved workflow one by one so they can be processed individually. Extracts Key Information: The Extract Workflow Details node uses custom code to process the data for each workflow, extracting essential details like its name, ID, tags, and a unique list of all node types it contains. Updates Google Sheet: The Add/Update Row in Google Sheet node then takes this information and appends or updates a row in your designated spreadsheet, using the workflow ID as a unique key to prevent duplicates. Waits and Repeats: The Pause to Avoid Rate Limits node adds a short delay to prevent issues with API limits before the loop continues to the next workflow. Setup Configure Get All Workflows Node: Select the Get All Workflows node. In the 'Credentials' section, provide your n8n API credentials to allow the workflow to access your instance's data. Prepare Your Google Sheet: Create a new Google Sheet. Set up the following headers in the first row: id, title, link, tags, nodes, CreatedAt, UpdatedAt, Active, Archived. Configure Add/Update Row in Google Sheet Node: Select the Add/Update Row in Google Sheet node. Authenticate your Google account in the 'Credentials' section. In the 'Document ID' field, enter the ID of your Google Sheet. You can find this in the sheet's URL (e.g., .../spreadsheets/d/THIS_IS_THE_ID/edit). Select your sheet from the 'Sheet Name' dropdown. Under 'Columns', ensure the id field is set as the 'Matching Columns' value. This is crucial for updating existing rows correctly. Activate the Workflow: Choose your preferred trigger. You can enable the Schedule Trigger to run the sync automatically at regular intervals. Save and activate the workflow. How to customize this workflow to your needs Track Different Data**: You can modify the Extract Workflow Details node to extract other pieces of information from the workflow JSON. For example, you could parse the settings object or count the total number of nodes. Remember to add a corresponding column in your Google Sheet and map it in the Google Sheets node. Add Notifications**: Add a notification node (like Slack, Discord, or Email) after the Loop Through Each Workflow node (in the second output) to be alerted when the sync is complete or if an error occurs. Filter Workflows**: You can add an IF node after the Loop Through Each Workflow node to filter which workflows get added to the sheet. For instance, you could choose to only log active workflows ({{ $('Loop Through Each Workflow').item.json.active }} is true) or workflows containing a specific tag. Adjust Wait Time**: The Pause to Avoid Rate Limits node is set to pause between each entry. You can adjust this time or remove it entirely if you have a small number of workflows and are not concerned about hitting API rate limits.

This n8n template turns raw call transcripts into clean HubSpot call logs and a single, actionable follow-up task—automatically. Paste a transcript and the contact’s email; the workflow finds the contact, summarizes the conversation in 120–160 words, proposes the next best action, and (optionally) updates missing contact fields. Perfect for reps and founders who want accurate CRM hygiene without the manual busywork. How it works A form trigger collects two inputs: Contact email Plain-text call transcript The workflow looks up the HubSpot contact by email to pull known properties. An AI agent reads the transcript (plus known fields) to: Extract participants, role, problem/opportunity, requirements, blockers, timeline, and metrics. Write a 120–160 word recap a teammate can skim. Generate one concrete follow-up task (title + body). Suggest updates for missing contact properties (city, country, job title, job function). The recap is logged to HubSpot as a completed Call engagement. The follow-up is created in HubSpot as a Task with subject and body. (Optional) The contact record is updated using AI-suggested values if the transcript clearly mentions them. How to use Connect HubSpot (OAuth2) on all HubSpot nodes. Connect OpenAI on the AI nodes. Open Form: Capture Transcript, submit the email + transcript. (Optional) In AI: Summarize Call & Draft Task, tweak prompt rules (word count, date normalization). (Optional) In Update Contact from Transcript, review the mapped fields before enabling in production. Activate the workflow and paste transcripts after each call. Requirements HubSpot** (OAuth2) for contact search, call logging, and tasks OpenAI** for summarization and task drafting Notes & customization ideas Swap the form for a Google Drive or S3 watcher to ingest saved transcripts. Add a speech-to-text step if you store audio recordings. Extend Update Contact to include additional fields (timezone, department, seniority). Post the summary to Slack or email the AE for quick handoffs. Gate updates with a confidence check, or route low-confidence changes for manual approval.

Automatically track domain expiry dates from Google Sheets, fetch real-time DNS expiry data via WHOIS API, and update expiry details back to your sheet with zero manual effort. Automated Domain Expiry Date Tracker with Google Sheets & WHOIS API Automate the entire process of monitoring domain expiry dates for all your websites directly from Google Sheets. This workflow reads domain names, fetches DNS SOA expiry information using the WHOIS API, converts timestamps into readable dates, and updates expiry details back into your tracking sheet—fully automated and rate-limit safe. Perfect for SEO teams, agencies, hosting managers, and businesses managing large domain portfolios. What this workflow does This automation handles four key tasks: Reads domain data Pulls all website domains directly from a Google Sheet Fetches expiry details Uses WHOIS API to retrieve DNS SOA records for each domain Processes expiry dates Converts expiry timestamps into human-readable DD-MM-YYYY format Extracts expiry month and year automatically Updates tracking sheet Writes expiry date, month name, and year back to Google Sheets Processes domains one by one with a controlled delay to avoid API limits How it works The workflow starts manually and loads configuration values such as Google Sheet ID and sheet name. It reads all domains listed in the Websites column and processes them in a loop. For each domain, the workflow calls the WHOIS API to fetch DNS SOA records. The expiry timestamp is extracted, converted into a readable date format, and enriched with expiry month and year values. Once processed, the workflow updates the same Google Sheet row with the new expiry information. A 30-second pause is applied before moving to the next domain to ensure API safety and stability. Setup requirements Accounts needed: n8n instance (self-hosted or cloud) Google account with Google Sheets access RapidAPI account with WHOIS API access Estimated setup time: 10 minutes Setup steps 1. Import workflow Copy the workflow JSON Open n8n → Workflows → Import from JSON Paste and import Verify all nodes are connected correctly 2. Configure Google Sheets Create a Google Sheet with a Websites column Add Google Sheets OAuth2 credential in n8n Paste your Sheet ID and sheet name inside Set Sheet Configuration node 3. Configure WHOIS API Get your RapidAPI WHOIS API key Add it to the Fetch DNS Records via WHOIS API HTTP Request node Test the API request 4. Verify data mapping Ensure expiry values map correctly to: Domain Expiry Expiry Month Expiry Year 5. Run and monitor Run the workflow manually Check execution logs Verify expiry data updates correctly in Google Sheets What data gets updated Domain data: Domain name Expiry date (DD-MM-YYYY) Expiry month (January–December) Expiry year Sheet updates: Existing rows are matched using the Websites column No duplicate rows are created Use cases SEO management:** Prevent domain expiries that can hurt rankings Agency operations:** Track client domains in one central sheet Hosting monitoring:** Stay ahead of renewal deadlines Portfolio management:** Manage hundreds of domains automatically Important notes Replace the WHOIS API key before activating Google Sheets column names must match exactly Workflow runs sequentially to avoid rate limits One domain is processed at a time Expiry accuracy depends on DNS SOA availability Support Need help or custom development? 📧 Email: info@isawow.com 🌐 Website: https://isawow.com/

Real-Time Uptime Alerts to Jira with Smart Slack On-Call Routing This workflow automatically converts uptime monitoring alerts received via webhook into Jira incident tasks and intelligently notifies an available on-call team member on Slack based on their real-time presence status. It ensures critical service outages never go unnoticed by selecting an active responder and sending a detailed direct message immediately. ⚡ Quick Implementation Steps Import the workflow JSON into n8n. Configure your Webhook, Slack, and Jira credentials. Update the IF node to filter for status = down (already configured). Set the Jira project and issue type as required. Connect your Slack on-call channel. Activate the workflow and send a test alert using Postman or your monitoring tool. What It Does This automation listens for incoming alerts from any uptime monitoring service. When a system or service goes down, the workflow instantly validates whether the alert is critical (status = down). Once validated, it automatically creates a detailed Jira Task containing all relevant service details such as timestamp, downtime duration, error code, customer impact and priority. After the Jira incident is created, the workflow retrieves a list of all members from a dedicated Slack on-call rotation channel. It checks each member’s Slack presence (active, away, offline) and uses smart selection logic to choose the best person to notify. The selected team member then receives a richly formatted direct Slack message containing all incident details and a link to the Jira ticket. This ensures the alert is not only logged properly but also reaches the right responder at the right time. Who’s It For This workflow is perfect for: DevOps teams managing uptime & system reliability. Support teams responsible for incident response. SRE teams using Jira and Slack. Organizations with an on-call rotation setup. Teams wanting automated escalation for downtime alerts. Requirements to Use This Workflow n8n installed** (self-hosted or cloud) Slack API credentials** with permission to read user presence and send direct messages Jira Software Cloud** credentials allowing issue creation A monitoring system** capable of sending webhook alerts (e.g., UptimeRobot, Uptime Kuma, StatusCake, custom system, etc.) Access to a Slack channel that includes your on-call rotation members How It Works & How to Set Up Step 1: Receive Alert from Uptime Monitoring Tool The workflow starts with the Webhook node (Receive Uptime Alert). Your monitoring tool must send a POST request with JSON payload including fields like: serviceName status timestamp customerImpact errorCode priority etc. Step 2: Filter for Critical Status The IF node (Filter for Critical Status) checks: Only when the service is down does the workflow continue to create a Jira incident. Step 3: Create Jira Incident Task The Create New Jira Incident node generates a Jira Task with: Summary: serviceName + timestamp Description: dynamic fields based on the alert payload Set your Jira Project and Issue Type as needed. Step 4: Fetch Slack On-Call Channel Members The workflow calls Slack API to retrieve all user IDs in a designated channel (e.g., #on-call-team). Step 5: Loop Through Each Member Split In Batches Node** loops each Slack member individually. For each user, their Slack presence is fetched using: Step 6: Build Final Data for Each User The Set node (Collect & Set Final Data) stores: presence member ID service details Jira ticket ID downtime info and more Step 7: Select the Best On-Call User A custom Code node uses presence-based logic: Selection Logic If one or more users are active → randomly pick one active user. If only one user is active → pick that user. If no users are active → default to the first member from the channel. This ensures you always get a responder. Step 8: Notify Selected User The Slack Notify Node sends a formatted direct message with: service status downtime duration error code customer impact Jira ticket link priority The selected on-call responder receives everything they need to act immediately. How to Customize Nodes Webhook Node Change the path to something meaningful (e.g., /uptime-alerts). Customize expected fields based on your monitoring tool's payload. IF Node Modify status condition for: "critical" "error" or multiple conditions Jira Node You can customize: Issue type (Incident, Bug, Task) Priority field mapping Project ID Custom fields or labels Slack Retrieval Node Change the channel to your team's actual on-call rotation channel. Slack Message Node Modify message formatting, tone, emojis, or add links. Add @mentions or tags. Include escalation instructions. Add-Ons (Optional Extensions) Enhance the workflow by adding: 1. Escalation Logic If the selected user doesn’t respond within X minutes, notify next user. 2. PagerDuty / OpsGenie Integration Trigger paging systems for SEV-1 incidents. 3. Status Page Updates Automatically update public status pages. 4. Auto-Resolution When service status returns to up, automatically: Update Jira ticket Notify the team Close the incident 5. Logging & Analytics Store incidents in Google Sheets, Notion, or a database. Use Case Examples This workflow can support multiple real-world scenarios: Website Uptime Monitoring If your main website goes down, instantly create a Jira incident and notify your on-call engineer. API Downtime Alerting When an API endpoint fails health checks, alert active developers only. Microservices Monitoring Each microservice alert triggers a consistent, automated incident creation and notification. Infrastructure Failure Detection When servers, containers, or VMs become unreachable, escalate to your infrastructure team. Database Performance Degradation If DB uptime drops or error rate spikes, create a Jira ticket and ping the database admin. And many more variations of outage, error, and performance monitoring events. Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|----------------|----------| | Workflow not triggering | Webhook URL not updated in monitoring tool | Copy n8n webhook URL and update in monitoring source | | No Jira ticket created | Invalid Jira credentials or missing project permissions | Reauthorize Jira credentials and verify permissions | | Slack users not found | Wrong channel ID or bot not added to channel | Ensure bot is invited to the Slack channel | | Slack presence not returning | Slack app lacks presence permission (users:read.presence) | Update Slack API scopes and reinstall | | No user receives notification | Presence logic always returns empty list | Test Slack presence API and verify real-time presence | | Wrong user selected | Intended selection logic differs | Update the JS logic in the code node | | Jira fields not populated | Alert payload fields missing | Verify webhook payload structure and match expected fields | Need Help? If you need assistance setting up this workflow, customizing integrations, building escalations or extending the logic with add-ons — WeblineIndia is here to help. We can assist with: Custom Slack/Jira/Monitoring automation On-call rotation logic enhancements Cloud deployment & workflow optimization Any custom n8n automation Production-grade monitoring workflows 👉 Contact WeblineIndia for professional support, implementation and custom workflow development.

##📘 Description This workflow acts as a real-time emergency alert system designed for personal safety scenarios. It receives distress signals via webhook, enriches the data with a live Google Maps link and timestamp, generates a clear AI-formatted alert message, instantly notifies a Telegram group, and logs the incident in Google Sheets for tracking and audit. ⚙️ Step-by-Step Flow 1) Emergency Webhook (Trigger) 2) Receives a POST request containing: Name Phone number Latitude & Longitude Acts as the entry point for emergency alerts. 3) Generate Maps Link (Function Node) Converts latitude & longitude into a Google Maps URL Ensures responders can access live location instantly 4) Create Emergency Message (Function Node) Adds timestamp (IST) Structures raw alert data Prepares base emergency message context 5) AI Agent (OpenAI GPT-4o-mini) Formats the alert into a clean, urgent, human-readable message Ensures clarity, visibility, and consistency Adds emojis and structured layout for quick comprehension 6) Telegram Group Alert (Telegram Node) Sends real-time emergency notification to a predefined group Ensures immediate visibility for responders 7) Log to Google Sheets (Google Sheets Node) Stores alert data for records Fields logged: name, phone, maps link, message, timestamp Creates audit trail for safety tracking 🧩 Prerequisites • Telegram Bot credentials + chat ID • OpenAI API (GPT-4o-mini) • Google Sheets OAuth connection • Webhook endpoint exposed publicly 💡 Key Benefits ✔ Instant emergency alert delivery ✔ Live location sharing via Google Maps ✔ AI-enhanced message clarity (no ambiguity) ✔ Real-time group notification for faster response ✔ Persistent logging for audit and follow-up 👥 Perfect For Women safety applications SOS mobile apps or panic button systems Security teams and emergency response workflows Community safety networks and alert systems

Stop sending sensitive agency drafts as permanent email attachments. This workflow creates a "self-destructing" delivery system that hosts files via UploadToURL, sends branded previews via SendGrid, and automatically expires access after a set duration while logging the entire lifecycle in Google Sheets. 🎯 What This Workflow Does Turns any sensitive file into a professional, time-limited client preview: 📝 Captures Delivery Request - Receives the file (binary or URL), recipient info, and desired expiry duration (e.g., 24 hours) via Webhook. ☁️ Instant CDN Hosting - UploadToURL hosts the asset and returns a high-speed public link. 🔑 Secure Token Generation - Generates a unique hex token and calculates the exact UTC expiry timestamp. 📊 Real-time Logging - Records the link in Google Sheets as active with all metadata before the email is sent. 📧 Branded Delivery - Sends a professional HTML email via SendGrid featuring your branding, a secure "View File" button, and a clear expiry notice. ⏳ Automated Expiration - Pauses execution for the specified duration using the Wait node, then updates the sheet to expired and notifies both the client and the agency. ✨ Key Features UploadToURL Integration**: Native community node hosting ensures your files are web-ready instantly without manual cloud storage setup. Dynamic "Burner" Logic**: The link stays active only as long as you specify (from 1 to 168 hours). Dual-Phase Notifications**: Clients get a polite notice when the link is active and a second one when it has officially expired. Lifecycle Tracking**: A centralized Google Sheet acts as your "Delivery Command Center," tracking tokens, sent times, and expiry statuses. Agency Audit Trail**: The agency receives a final summary email once a link's lifecycle is complete, providing a full record for project management. 💼 Perfect For Creative Agencies**: Sharing draft designs, videos, or proposals that shouldn't live in a client's inbox forever. Legal & Finance**: Providing temporary access to sensitive documents or statements. Freelancers**: Delivering final assets that require a "preview-only" window before final payment. HR Teams**: Sending temporary access to employee handbooks or internal policy drafts. 🔧 What You'll Need Required Integrations UploadToURL** - To host assets and provide secure CDN links. n8n Community Node** - n8n-nodes-uploadtourl must be installed. SendGrid** - To send the branded preview and expiry emails. Google Sheets** - To act as the database for link tracking. Configuration Variables GSHEET_SPREADSHEET_ID: The ID of your tracking sheet. DEFAULT_EXPIRY_HOURS: Default time (e.g., 24) if not specified in the webhook. AGENCY_NAME & AGENCY_EMAIL: For branding the automated emails. 🚀 Quick Start Import Template - Copy the JSON and import it into your n8n canvas. Install Node - Ensure the UploadToURL community node is installed. Set Credentials - Link your UploadToURL, SendGrid, and Google Sheets accounts. Prepare Sheet - Create a sheet named BurnerLinks with columns: Token, Recipient Email, Status, Sent At, Expires At, and CDN URL. Define Variables - Update the n8n variables with your Sheet ID and Agency details. Deploy - Activate the workflow and start sending secure, timed previews. 🎨 Customization Options Branding**: Edit the Generate Link Record code node to update the HTML/CSS for the email templates to match your brand colors. Extended Wait**: For links lasting weeks, ensure your n8n instance is configured to persist executions across restarts. Slack Alerts**: Add a Slack node to notify your team the moment a client clicks the link (requires a redirect/tracking layer). Password Protection**: Integrate an additional layer that requires a password (sent via a separate channel) to view the UploadToURL link. 📈 Expected Results Enhanced Security**: Sensitive files no longer float around indefinitely in client inboxes. Professional Impression**: Clients receive branded, structured previews that emphasize security and professionalism. Zero Manual Cleanup**: No need to manually delete files or remember to "turn off" links. Complete Transparency**: Always know exactly which links are active and when they were accessed. 🏆 Use Cases Pitch Deck Delivery Send your high-stakes pitch deck with a 48-hour window. The urgency encourages the client to review it promptly while protecting your IP. Contract Previews Share a draft agreement for a quick 24-hour review. Once the window closes, the client is prompted to contact you for the final version. Limited-Time Portfolio Share a custom portfolio or "lookbook" with a lead, giving them 7 days of access to create a "limited time" feel to your availability. 💡 Pro Tips Wait Node Execution**: Each link runs as a separate execution. If you send 100 links, you will see 100 "Waiting" executions in your history. File Types**: The workflow includes validation for PDF, JPG, PNG, DOCX, and MP4. You can expand this in the Validate Payload code node. BCC Records**: The workflow automatically BCCs the agency on the first email so you have a copy in your own sent folder. Ready to secure your deliveries? Import this template and connect UploadToURL to start sending professional "burner" links today. Questions about the Google Sheet setup? The workflow includes a detailed sticky note explaining the exact column headers needed for the database sync.

Description: Transform your Jira project management workflow with this intelligent n8n automation template that continuously tracks, scores, and reports the health of Jira Epics. The automation runs every 6 hours, fetches all active Epics, analyzes linked issues for performance, quality, and stability metrics, and automatically flags at-risk Epics. It updates Jira fields, sends alerts to Slack, logs trends in Google Sheets, and syncs visibility with Monday.com—ensuring teams stay proactive, not reactive. Ideal for agile teams, project managers, and product owners looking to monitor delivery health, detect risks early, and maintain transparent reporting across tools. ✅ What This Template Does (Step-by-Step) ⏱ Trigger Every 6 Hours: Automatically executes every six hours to keep health data updated in near real-time. 📥 Fetch All Epics from Jira: Retrieves all Epics, their keys, and fields via the Jira API to establish a full analysis scope. 🔀 Split Epics for Processing: Converts the batch of Epics into individual items, enabling sequential metric analysis. 🔗 Fetch Linked Issues: Collects all issues linked to each Epic, capturing their types, statuses, cycle times, and labels for deeper health analysis. 📈 Calculate Health Score: Computes a weighted score (0–1 scale) based on: • 40% Average Cycle Time • 30% Bug Ratio • 20% Churn (Reopened issues) • 10% Blocker Ratio Scores above 0.6 indicate at-risk Epics. ⚖️ Decision Gate: At-Risk or Healthy: If the health score exceeds 0.6, the workflow automatically initiates corrective actions. 🔧 Update Jira Epic: Updates Jira with the computed health score and adds an “At Risk” label for visibility in dashboards and filters. 🚨 Send Slack Alerts: Notifies the #project-alerts channel with Epic details, health score, and direct Jira links for immediate attention. 📋 Update Monday.com Pulse: Syncs health metrics and risk status back to your Monday board, maintaining cross-platform transparency. 📊 Log to Google Sheets: Appends health score logs with timestamps and Epic keys for trend analysis, audits, and dashboard creation. 🧠 Key Features ✔️ Automated Jira Epic health scoring (cycle time, churn, bugs, blockers) ✔️ Real-time risk flagging with Slack alerts ✔️ Integrated cross-tool visibility (Jira + Monday + Sheets) ✔️ Continuous trend tracking for performance improvement ✔️ Secure API-based automation 💼 Use Cases 💡 Track project delivery health and spot risks early 📈 Build executive dashboards showing team velocity and quality 🤝 Align product and engineering with shared visibility 🧾 Maintain a compliance audit trail of Epic health trends 📦 Required Integrations • Jira Software Cloud API – for Epic and issue data • Slack API – for real-time team alerts • Monday.com API – for visual board updates • Google Sheets API – for historical tracking and analytics 🎯 Why Use This Template? ✅ Prevents project delays by flagging risks early ✅ Provides automated, data-driven Epic health insights ✅ Connects your reporting ecosystem across platforms ✅ Perfect for Agile and DevOps teams driving continuous improvement

Description Keep your internal knowledge base fresh and reliable with this automated FAQ freshness monitoring system. 🧠📅 This workflow tracks FAQ update dates in Notion, calculates SLA compliance, logs results in Google Sheets, and sends Slack alerts for outdated items. Perfect for documentation teams ensuring content accuracy and operational visibility across platforms. 🚀💬 What This Template Does 1️⃣ Triggers every Monday at 10:00 AM to start freshness checks. ⏰ 2️⃣ Fetches FAQ entries from your Notion database. 📚 3️⃣ Computes SLA status based on the last edited date (30-day threshold). 📆 4️⃣ Updates a Google Sheet with current FAQ details and freshness status. 📊 5️⃣ Filters out overdue FAQs that need review. 🔍 6️⃣ Aggregates all overdue items into one report. 🧾 7️⃣ Sends a consolidated Slack alert with direct Notion links and priority tags. 💬 Key Benefits ✅ Maintains documentation freshness across systems. ✅ Reduces support friction from outdated FAQs. ✅ Centralizes visibility with Google Sheets reporting. ✅ Notifies your team in real time via Slack. ✅ Enables SLA-based documentation governance. Features Weekly automated schedule (every Monday at 10 AM). Notion database integration for FAQ retrieval. SLA computation and overdue filtering logic. Google Sheets sync for audit logging. Slack notification for overdue FAQ alerts. Fully configurable thresholds and alerting logic. Requirements Notion API credentials with database read access. Google Sheets OAuth2 credentials with edit access. Slack Bot Token with chat:write permission. Environment variables : NOTION_FAQ_DATABASE_ID GOOGLE_SHEET_FAQ_ID SLACK_FAQ_ALERT_CHANNEL_ID Target Audience Knowledge management and documentation teams 🧾 SaaS product teams maintaining FAQ accuracy 💡 Support operations and customer success teams 💬 QA and compliance teams monitoring SLA adherence 📅 Step-by-Step Setup Instructions 1️⃣ Connect Notion credentials and set your FAQ database ID. 2️⃣ Create a Google Sheet with required headers (Title, lastEdited, slaStatus, etc.). 3️⃣ Add your Slack credentials and specify the alert channel ID. 4️⃣ Configure the cron schedule (0 10 * * 1) for Monday 10:00 AM checks. 5️⃣ Run once manually to verify credentials and mappings. 6️⃣ Activate for ongoing weekly freshness monitoring. ✅