Workflow Templates

This workflow utilizes Philips IntelliVue Device details to automatically track patient vitals, such as heart rate and oxygen levels. It quickly spots critical health issues and sends alerts to healthcare staff for fast action. The system saves data for records and helps improve patient care with real-time updates. It’s simple to set up and adjust for different needs. Essential Information Processes data from Philips IntelliVue Devices to monitor vitals instantly. Filters and categorizes conditions as critical or non-critical based on thresholds. Sends clinical alerts for critical conditions and logs data for review. Runs every 30 seconds to ensure timely updates. System Architecture Data Collection Pipeline: Poll Device Data Every 30s**: Continuously retrieves vitals from Philips IntelliVue Devices. Fetch from IntelliVue Gateway**: Retrieves data via HTTP GET requests. Processing Pipeline: Process Device Data**: Analyzes and validates the data stream. Alert Generation Flow: Validate & Enrich Data**: Ensures accuracy and adds patient context. Save to Patient Database**: Stores data for records. Check Alert Status**: Applies rules to trigger alerts. Send Clinical Alert**: Notifies staff for critical conditions. Implementation Guide Import workflow JSON into n8n. Configure the Philips IntelliVue Devices gateway URL and test with sample data. Set up alert credentials (e.g., email). Test and adjust rule thresholds. Technical Dependencies Philips IntelliVue Devices for vitals data. n8n for automation. Email or messaging API for alerts. Database for data storage. Customization Possibilities Adjust Switch node rules for critical thresholds. Customize alert messages. Modify database schema. Add logging for analysis.

Description This workflow acts as a CI/CD-style test harness for validating other n8n workflows. It executes a target workflow (here: Archive Payment Receipts), evaluates pass/fail outcomes, and generates structured reports. Results are automatically archived to Google Drive, logged in Google Sheets, and synced with ClickUp for visibility. Both success and failure scenarios are handled with standardized formatting. What This Template Does (Step-by-Step) ⚡ Manual Trigger – Start the test run manually. ▶️ Execute Target Workflow Under Test – Calls the specified workflow (Archive Payment Receipts) and captures its output, even if it errors. ✅ Test Result Evaluation (If Node) – Checks if the output contains errors. Pass Path → success formatting + archival. Fail Path → failure formatting + logging. 📄 Format Success Test Result (Set Node) – Creates a structured result object with: Status: ✅ Passed Workflow Name Timestamp 📄 Format Failed Test Result (Set Node) – Same as above, but with ❌ Failed status. 📝 Generate Success/Failure Report Text (Code Node) – Converts structured data into a human-readable report string. 📦 Convert Report to Text File – Transforms the text into a .txt file for archiving. ☁️ Archive Reports to Google Drive – Saves .txt files (success/failure) into the resume store folder with timestamped filenames. ✏️ Update ClickUp Task (Success/Failure) – Posts results directly into a ClickUp task for visibility. 📊 Log Error Details to Error Tracking Sheet (Google Sheets) – Appends raw error objects to an error log sheet for debugging and trend analysis. Prerequisites Target workflow to test (e.g., Archive Payment Receipts) Google Drive folder for report storage Google Sheets (Error Log tab) ClickUp API credentials n8n instance Key Benefits ✅ Automates workflow regression testing ✅ Captures pass/fail outcomes with full audit trail ✅ Maintains error logs for debugging and reliability improvements ✅ Keeps stakeholders updated via ClickUp integration ✅ Supports compliance with archived test reports Perfect For Teams running workflow QA & testing Organizations needing audit-ready test reports DevOps pipelines with continuous validation of automations Stakeholders requiring real-time visibility into workflow health

Automated Trade Report from Interactive Brokers This workflow is aimed at traders who use Interactive Brokers. It automatically retrieves the trades made in IBKR on a daily basis and writes them to a Google Sheet, so that anyone can easily perform further analyses and statistics using the on-board tools. This creates an automatic, continuous trade journal. Typical Usecaes Monitoring your trades in one journal Analyze your Profit & Losses Basis for any kind of statistics • Log trades (entry, exit, setup, reason) • Analyze performance (win rate, R/R, expectancy) • Evaluate strategies & setups • Detect mistakes & patterns • Track emotions & discipline • Support coaching, reviews & improvement How it works A daily schedule triggers a FlexStatement request to Interactive Brokers to start generating a trade report. The workflow extracts the reference code from IBKR's response, waits for the report to be ready, then downloads the Flex report XML. The XML is parsed and split into individual Trade records. Key fields (tradeDate, symbol, quantity, buySell, tradeID, price, money, currency, fxRateToBase) are normalized.\n5. Each trade is appended or updated in the configured Google Sheet, matching on tradeID to avoid duplicates and keep the journal current. Prerequisites Trading Account on IBKR Google Sheets OAuth2 A Google Sheet containing your trading journal Setup [ ] Set schedule to run at your desired time (default: 08:00) [ ] Add or verify IBKR request token/reference parameters. 1. Create Flex Query Token: Go to IBKR Account Management Reports → Flex Queries → Flex Web Service → Generate Current Token → Make a note of the token (e.g.: 123456789012345678901234) 2. Enter Flex Token: In node '1. Request Flex Report' and in node '2. Extract Reference Code' Replace YOUR_FLEX_TOKEN with your token ID 3. Create Flex Query in IBKR (if not already done): Go to IBKR Account Management Reports → Flex Queries → Activity Flex Query → Create Select: Trade Confirmation ✓ Period: Last 365 Days Format: XML Save and note down the query ID 4. Enter Flex Query ID: In node '1. Request Flex Report' Replace YOUR_QUERY_ID with your query ID [ ] Adjust wait time if IBKR needs longer to generate reports [ ] Select the Google Sheet and target sheet/tab [ ] Connect Google Sheets OAuth2 account [ ] Confirm column mapping and that tradeID is the matching column [ ] Run a manual test to validate parsing and row updates

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 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.

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/

Short Description: Automatically collect and analyze your competitor’s YouTube performance. This workflow extracts video titles, views, likes, and descriptions from any YouTube channel and saves the data to Google Sheets — helping creators spot viral trends and plan content that performs. Who’s it for For content creators, YouTubers, and marketing teams who want to track what’s working for their competitors — without manually checking their channels every day. How it works This workflow automatically collects data from any YouTube channel you enter. You just write the channel name in the form — n8n fetches the channel ID, gets all recent video IDs, and extracts each video’s title, views, likes, and description. Finally, all the information is saved neatly into a connected Google Sheet for analysis. How to set up Create a Google Sheet with columns for Title, Views, Likes, Description, and URL. Connect your Google account to n8n. Add your YouTube Data API key inside the HTTP Request nodes (use n8n credentials, not hardcoded keys). Update your form submission or trigger node to match your input method. Execute the workflow once to test and verify that data is flowing into your sheet. Requirements YouTube Data API key Google Sheets account n8n cloud or self-hosted instance How to customize You can modify the JavaScript code node to include more metrics (like comments or publish date), filter by keywords, or change the output destination (e.g., Airtable or Notion).

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.

This weekly workflow automatically identifies new ranked keywords for your domain within Google’s top 10 results without manual SERP monitoring. On each run, the workflow fetches the latest ranking and search volume data using the DataForSEO Labs API and stores a fresh results snapshot in Airtable. It then compares this data with the previous set to identify any new keywords your domain started ranking for, focusing on queries that rank in the top 10. All newly ranked top-10 keywords are logged in Airtable, along with their ranking position and search volume. Once new terms and rankings are identified, the workflow sends you a Slack summary highlighting the latest changes. Who’s it for SEO experts and marketers who want an automated way to track new top-ranking keywords on Google for their domain(s). What it does This workflow automatically detects when your domain enters top-10 results for new keywords on Google, records them in Airtable, and sends a weekly summary via Slack. How it works Runs on a predefined schedule (default: weekly). Reads your keywords and target domains from Airtable. Fetches the latest Google rankings and keyword metrics via DataForSEO API. Compares the latest data with the previous run. Logs newly ranked top-10 keywords to Airtable. Sends a Slack summary with key changes. Requirements DataForSEO account and API credentials Airtable table with your keywords, following the required column structure. Airtable table with your target domains, following the required column structure. Slack account Customization You can easily customize this workflow by adjusting the run schedule, changing the minimum ranking threshold (e.g., top 5 or top 20), exporting results to other tools, and tailoring the Slack message content to your team’s workflow.

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.

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.