HumationHuman + Automation
Back to Catalog

Predictive health monitoring & alert system with GPT-4o-mini

Cheng Siong ChinCheng Siong Chin
391 views
2/3/2026
Monday.comSynchronizationWebhookHubSpotCRM
Official Page

How It Works

The system collects real-time wearable health data, normalizes it, and uses AI to analyze trends and risk scores. It detects anomalies by comparing with historical patterns and automatically triggers alerts and follow-up actions when thresholds are exceeded.

Setup Steps

  1. Configure Webhook Endpoint - Set up webhook to receive data from wearable devices
  2. Connect Database - Initialize storage for health metrics and historical data
  3. Set Normalization Rules - Define data standardization parameters for different devices
  4. Configure AI Model - Set up health score calculation and risk prediction algorithms
  5. Define Thresholds - Establish alert triggers for critical health metrics
  6. Connect Notification Channels - Configure email and Slack integrations
  7. Set Up Reporting - Create automated report templates and schedules
  8. Test Workflow - Run end-to-end tests with sample health data

Workflow Template

Webhook → Store Database → Normalize Data → Calculate Health Score → Analyze Metrics → Compare Previous → Check Threshold → Generate Reports/Alerts → Email/Slack → Schedule Follow-up

Workflow Steps

Ingest real-time wearable data via webhook, store and standardize it, and use GPT-4 for trend analysis and risk scoring. Monitor metrics against thresholds, trigger SMS, email, or Slack alerts, generate reports, and schedule follow-ups.

Setup Instructions

Configure webhook, database, GPT-4 API, notifications, calendar integration, and customize alert thresholds.

Prerequisites

Wearable API, patient database, GPT-4 key, email SMTP, optional Slack/Twilio, calendar integration.

Use Cases

Monitor glucose for diabetics, track elderly vitals/fall risk, assess corporate wellness, and post-surgery recovery alerts.

Customization

Adjust risk algorithms, add metrics, integrate telemedicine.

Benefits

Early intervention reduces readmissions and automates 80% of monitoring tasks.

Predictive Health Monitoring & Alert System with GPT-4o Mini

This n8n workflow creates a robust, AI-powered system for predictive health monitoring and alerts. It leverages a combination of database interactions, AI analysis (using an OpenAI Chat Model), and various communication channels to detect potential health issues and notify relevant parties.

What it does

This workflow automates the following steps:

  1. Ingests Data: It's designed to receive health-related data, likely from a webhook, which could be triggered by an external monitoring system or an application.
  2. Stores Data: The incoming data can be stored in various databases like PostgreSQL, MongoDB, or Redis for historical tracking and further analysis.
  3. Analyzes Health Data with AI: The core of the system uses an OpenAI Chat Model (specifically GPT-4o Mini, as hinted by the directory name) via an AI Agent to analyze the health data. This AI can identify patterns, anomalies, or potential risks based on the input.
  4. Conditional Alerting: Based on the AI's analysis, an "If" node evaluates conditions to determine if an alert is necessary.
  5. Notifies via Multiple Channels: If an alert condition is met, the system can send notifications through various channels:
    • Email: For detailed reports or formal notifications.
    • Slack: For team alerts and quick communication.
    • Twilio (SMS/Voice): For critical alerts requiring immediate attention.
  6. Logs Activity: A "No Operation" node might be used for logging or as a placeholder for future extensions, ensuring the workflow completes gracefully even when no specific action is taken.
  7. Schedules Actions (Optional): The Google Calendar node suggests the possibility of scheduling follow-up actions or appointments based on health insights.
  8. Custom Logic: A "Code" node allows for custom JavaScript logic to be executed, providing flexibility for complex data manipulation or rule-based processing.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • OpenAI API Key: For the OpenAI Chat Model to analyze health data.
  • Database Credentials: Access to at least one of the following databases if you plan to use them:
    • PostgreSQL
    • MongoDB
    • Redis
  • Email SMTP Credentials: For sending email alerts.
  • Slack Account & API Token: For sending Slack notifications.
  • Twilio Account & API Credentials: For sending SMS or voice alerts.
  • Google Calendar Account (Optional): If you intend to schedule events or actions.

Setup/Usage

  1. Import the Workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Webhook: Set up the "Webhook" node to listen for incoming health data. You will get a unique URL that external systems can post data to.
  3. Set up Credentials:
    • Configure your OpenAI credentials for the "OpenAI Chat Model" node.
    • Set up credentials for Postgres, MongoDB, or Redis if you plan to store data.
    • Configure Send Email credentials.
    • Set up Slack credentials.
    • Configure Twilio credentials.
    • (Optional) Configure Google Calendar credentials.
  4. Customize AI Agent: Adjust the "AI Agent" and "OpenAI Chat Model" nodes to define how the AI should interpret and analyze the incoming health data. You might need to provide specific prompts or instructions to guide its analysis for predictive health monitoring.
  5. Define Alert Logic: Modify the "If" node to set the conditions under which an alert should be triggered based on the AI's output.
  6. Customize Notifications: Configure the "Send Email", "Slack", and "Twilio" nodes with the appropriate recipient details and message templates for your alerts.
  7. Activate the Workflow: Once configured, activate the workflow to start monitoring and alerting.

This workflow provides a powerful foundation for a proactive health monitoring system, leveraging AI to go beyond simple threshold-based alerts.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Synchronizing WooCommerce inventory and creating products with Google Gemini AI and BrowserAct

Synchronize WooCommerce Inventory & Create Products with Gemini AI & BrowserAct This sophisticated n8n template automates WooCommerce inventory management by scraping supplier data, updating existing products, and intelligently creating new ones with AI-formatted descriptions. This workflow is essential for e-commerce operators, dropshippers, and inventory managers who need to ensure their product pricing and stock levels are synchronized with multiple third-party suppliers, minimizing overselling and maximizing profit. --- Self-Hosted Only This Workflow uses a community contribution and is designed and tested for self-hosted n8n instances only. --- How it works The workflow is typically run by a Schedule Trigger (though a Manual Trigger is also shown) to check stock automatically. It reads a list of suppliers and their inventory page URLs from a central Google Sheet. The workflow loops through each supplier: A BrowserAct node scrapes the current stock and price data from the supplier's inventory page. A Code node parses this bulk data into individual product items. It then loops through each individual product found. The workflow checks WooCommerce to see if the product already exists based on its name. If the product exists: It proceeds to update the existing product's price and stock quantity. If the product DOES NOT exist: An If node checks if the missing product's category matches a predefined type (optional filtering). If it passes the filter, a second BrowserAct workflow scrapes detailed product attributes from a dedicated product page (e.g., DigiKey). An AI Agent (Gemini) transforms these attributes into a specific, styled HTML table for the product description. Finally, the product is created in WooCommerce with all scraped details and the AI-generated description. Error Handling: Multiple Slack nodes are configured to alert your team immediately if any scraping task fails or if the product update/creation process encounters an issue. Note: This workflow does not support image uploads for new products. To enable this functionality, you must modify both the n8n and BrowserAct workflows. --- Requirements BrowserAct API account for web scraping BrowserAct n8n Community Node -> (n8n Nodes BrowserAct) BrowserAct templates named “WooCommerce Inventory & Stock Synchronization” and “WooCommerce Product Data Reconciliation” Google Sheets credentials for the supplier list WooCommerce credentials for product management Google Gemini account for the AI Agent Slack credentials for error alerts --- Need Help? How to Find Your BrowseAct API Key & Workflow ID How to Connect n8n to Browseract How to Use & Customize BrowserAct Templates How to Use the BrowserAct N8N Community Node --- Workflow Guidance and Showcase STOP Overselling! Auto-Sync WooCommerce Inventory from ANY Supplier

Madame AI Team | KaiBy Madame AI Team | Kai
600